スキルを探す

Structured bug diagnosis and fixing workflow — reproduce, diagnose root cause, apply minimal fix, write regression test, and scan for similar patterns

日本語の概要は準備中です。原文の説明を表示しています。

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/

日本語の概要は準備中です。原文の説明を表示しています。

Automated CLI-based parallel agent execution — spawn subagents via Gemini CLI, coordinate through MCP Memory, monitor progress, and run verification

日本語の概要は準備中です。原文の説明を表示しています。

Convert PDF to Markdown using opendataloader-pdf — extracts text, tables, headings, and images with correct reading order

日本語の概要は準備中です。原文の説明を表示しています。

PM planning workflow — analyze requirements, select tech stack, decompose into prioritized tasks with dependencies, and define API contracts

日本語の概要は準備中です。原文の説明を表示しています。

Full QA review pipeline — security audit (OWASP Top 10), performance analysis, accessibility check (WCAG 2.1 AA), and code quality review

日本語の概要は準備中です。原文の説明を表示しています。

Auto-detect project tech stack and generate stack-specific references for domain skills

日本語の概要は準備中です。原文の説明を表示しています。

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

日本語の概要は準備中です。原文の説明を表示しています。

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category.

日本語の概要は準備中です。原文の説明を表示しています。

Implement server APIs, authentication, and application data access. Schema modeling and query tuning use oma-db.

日本語の概要は準備中です。原文の説明を表示しています。

Design schemas and migrations, tune queries, or plan vector retrieval and database operations. Application API implementation uses oma-backend.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.

日本語の概要は準備中です。原文の説明を表示しています。

Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Research customer pain points, trends, and competitors through the OMA market engine. Use for market discovery or voice-of-customer analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Implement Flutter, React Native, or native Swift apps. Use for mobile screens, widgets, platform integrations, and application data flows.

日本語の概要は準備中です。原文の説明を表示しています。

Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.

日本語の概要は準備中です。原文の説明を表示しています。

Review changes for correctness, security, accessibility, and performance. Use for scoped quality reviews or verification plans; bug fixes use oma-debug.

日本語の概要は準備中です。原文の説明を表示しています。

Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.

日本語の概要は準備中です。原文の説明を表示しています。

Design-first ideation workflow — explore user intent, clarify constraints, propose approaches, and produce an approved design document before planning

日本語の概要は準備中です。原文の説明を表示しています。