メニュー
Use for any coding task: fix bug, implement feature, update file, refactor, debug, investigate failure, add tests, run validators, review changes, or verify a repo. Enforces clarify → explore → route → TDD → verify → review for a non-programmer user.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Enforce distinctive, non-AI-looking design for any UI task across ALL stacks. Auto-triggers on: build UI, page, component, layout, web app, design, style, CSS, animation, theme, landing page, dashboard, form, navigation, frontend, website, interface, responsive, mobile, header, footer, sidebar, hero, card, button, modal, Tauri, Electron, React Native, Flutter, SwiftUI, desktop app, mobile app, native app.
Conducts enterprise-grade research with multi-source synthesis, citation tracking, and verification. Produces citation-backed reports through a structured pipeline with source credibility scoring. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends", or "state of the art". Not for simple lookups, debugging, or questions answerable with 1-2 searches.
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to 7 specialists, generates health score. Use when user says "audit", "full SEO check", "analyze my site", or "website health check".
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", or "X vs Y".
| name | execution-guard |
| description | Use for any coding task: fix bug, implement feature, update file, refactor, debug, investigate failure, add tests, run validators, review changes, or verify a repo. Enforces clarify → explore → route → TDD → verify → review for a non-programmer user. |
Apply this workflow on coding tasks.
repo-scout (haiku): search, inventory, conventions, validator discoveryplanner (sonnet): multi-file planning, risks, open questionscode-reviewer (sonnet): post-edit reviewvalidator (sonnet): build, typecheck, lint, tests, coveragesecurity-reviewer (opus): before commits or security-sensitive changescode-reviewer after validators passsecurity-reviewer