728 件 ・ 関連度順
概要と使いどころ
Debug systematically with root-cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, CI failures, or system investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Set up systematic review monitoring across e-commerce platforms. Track new reviews, detect negative review spikes, monitor competitor reviews, and automate review response workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic code review for bugs, security, style, and performance
日本語の概要は準備中です。原文の説明を表示しています。
Systematic exploration of unknown environments before starting work
日本語の概要は準備中です。原文の説明を表示しています。
Best practices for systematic research, source evaluation, and evidence gathering
日本語の概要は準備中です。原文の説明を表示しています。
Build the actual product — from landing page to deployed MVP with payment integration, QA testing, and post-deploy canary monitoring. Handles code generation, deployment, database setup, authentication, Stripe/payment integration, systematic QA protocol, and production health scoring. Use when the user needs to build something, deploy a product, set up payments, create a landing page, or says 'build this', 'deploy', 'create MVP', 'set up payments', or 'ship it'.
日本語の概要は準備中です。原文の説明を表示しています。
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Iterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix web performance issues including Core Web Vitals (LCP, INP, CLS), bundle size, asset optimization, render performance, and runtime efficiency. Use this skill whenever the user wants to improve page speed, fix Core Web Vitals, optimize assets, reduce bundle size, debug slow renders, or systematically improve a site's performance. Triggers on performance, page speed, Core Web Vitals, LCP, INP, CLS, FID, TTFB, bundle size, code splitting, image optimization, lazy loading, render blocking, slow page, performance audit, Lighthouse score. Also triggers when traffic or conversion is dropping due to perceived slowness.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a creative brief grounded in live reference sites and deliberately distinct from existing demos, for any new brand build. Composes with brand-archetype-system and creative-direction. Use this skill at the start of any brand or microsite build when the result needs to land in a specific aesthetic position and not drift into a default house style. Triggers on creative brief, design brief, build brief, brand direction, where should this brand sit, what should this site look like, reference sites for, archetype for, distinct from our other brands, divergence from prior, not the same as. Also triggers when prior builds have come out as siblings and a systematic divergence approach is needed.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic literature review with search, screening, and synthesis
日本語の概要は準備中です。原文の説明を表示しています。
Systematic scientific hypothesis formulation and evaluation
日本語の概要は準備中です。原文の説明を表示しています。
Systematic root-cause debugging. Iron Law: no fixes without root cause investigation first. Four phases: Root Cause Investigation, Pattern Analysis (6 known patterns), Hypothesis Testing (3-strike rule), Implementation. Structured debug report output.
日本語の概要は準備中です。原文の説明を表示しています。
Parses error messages, traces execution flow through stack traces, correlates log entries, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Literature review for academic and R&D research: search strategy, source assessment, synthesis, and citation management. Use when conducting a systematic literature review, building a bibliography, or preparing a research-grounded report.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic copy editing through focused passes (the Seven Sweeps Framework) covering clarity, voice, proof, specificity, and friction removal. Use when editing marketing copy, reviewing drafts, polishing content, or proofreading.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic PR review with blast-radius analysis, security scanning, and breaking-change and test-coverage deltas. Use when reviewing PRs that touch shared libraries, APIs, database schemas, auth, or security-sensitive code.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic competitor tracking that feeds positioning, battlecards, and roadmap decisions. Use when analyzing competitors, building battlecards, tracking market moves, conducting win/loss analysis, or updating positioning.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action plans with stakeholder presentation templates.
日本語の概要は準備中です。原文の説明を表示しています。
Run fable-mode execution discipline on Claude Sonnet. When invoked by slash command or by name, spawns a Sonnet subagent that follows the staged loop — stage plan, parallel delegation, a failable verification check at each stage, and a skeptical self-review before delivery; a wording-only request runs the loop inline on the current model. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on Sonnet.
日本語の概要は準備中です。原文の説明を表示しています。
Run fable-mode execution discipline on Claude Haiku. Routes the task to the @fable-worker-haiku agent, whose definition carries the staged loop with tightened verification (no bare "unverified" allowed) and an escalate-don't-improvise rule. Trigger when the user explicitly asks for thorough/systematic handling run cheaply or fast ("fable on haiku", "deep work mode but cheap", "stage this on haiku"). For bulk mechanical work. Do NOT use for tasks needing synthesis — benchmark note: at n=1 the skill's effect on Haiku swung both directions (+25 / −17); route quality-critical work to fable-sonnet instead.
日本語の概要は準備中です。原文の説明を表示しています。
Run fable-mode execution discipline on Claude Fable 5.1 — the top of the escalation ladder and the strongest staged run available. Routes the task to the @fable-orchestrator agent with its model overridden to Fable (`model: "fable"`), which stages the work, delegates artifact production to @fable-worker-sonnet / @fable-worker-haiku, and cold-checks deliverables with @fable-verifier. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on the strongest model ("fable on fable", "stage this on fable", "deep work mode, fable", "run this on 5.1"), or when a fable-opus run reports the task exceeds Opus's ceiling. Benchmarked 2026-09-02: zero correctness delta on Fable 5.1 at ~1.1× tokens, ~2× wall — a provenance runner, not an accuracy runner. Do NOT use for ordinary single-pass tasks — prefer fable-opus, fable-sonnet, or fable-haiku when the task doesn't need peak reasoning. Fable is plan-included; bulk work still routes down-tier.
日本語の概要は準備中です。原文の説明を表示しています。
Run fable-mode execution discipline on Claude Opus — the top of the escalation ladder. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on Opus ("fable on opus", "stage this on opus", "deep work mode, opus"). When a task exceeds Opus's ceiling, report that to the user rather than escalating further.
日本語の概要は準備中です。原文の説明を表示しています。