728 件 ・ 関連度順
概要と使いどころ
Systematic process for analyzing and modernizing legacy applications to comply with the 12-Factor App methodology. Covers code analysis, configuration externalization, dependency management, and container/Kubernetes best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a plugin and produce an executable refactoring design, task plan, and context manifest. Use when preparing systematic plugin refactoring.
日本語の概要は準備中です。原文の説明を表示しています。
Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
日本語の概要は準備中です。原文の説明を表示しています。
Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.
日本語の概要は準備中です。原文の説明を表示しています。
Builds or audits a literature review, producing an evidence map, the closest prior work, source clusters, a gap verdict, and a synthesis plan for the introduction. Use when the user asks whether a contribution is novel, who has studied a question, what the literature establishes, or how to organize a review, or wants a reading list, Zotero export, or pile of papers turned into one. For systematic reviews or meta-analyses it produces the protocol scaffold and routes registration (PROSPERO or OSF) and screening to dedicated tools.
日本語の概要は準備中です。原文の説明を表示しています。
Builds or audits a literature review: evidence map, closest prior work, gap verdict, and synthesis plan. Use to check whether a contribution is novel, map what a literature establishes, or organize a review; systematic reviews get a protocol scaffold.
日本語の概要は準備中です。原文の説明を表示しています。
Track and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically deconstruct written content into verifiable claims, validate each using search/documentation, and facilitate informed discussion through structured interviewing.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging specialist focused on root cause analysis
日本語の概要は準備中です。原文の説明を表示しています。
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and batch-produce social media content across platforms (Instagram, X/Twitter, TikTok, LinkedIn, YouTube). Generates a week or month of posts with platform-specific formatting, hashtags, hooks, and posting schedule. Use when "social media posts", "social calendar", "plan social content", "Instagram posts", "tweets", "LinkedIn posts", "TikTok ideas", "social media strategy", "batch social", or any request to systematically produce social media content.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and batch-produce an entire email system for a product. Maps every lifecycle touchpoint (onboarding, activation, conversion, retention, transactional, win-back), generates all emails with quality gates, outputs Loops-ready copy. Use when "create all emails", "email system", "build email sequences", "lifecycle emails", "onboarding sequence", "set up transactional emails", "plan all the emails for [product]", or any request to systematically produce a complete set of emails for a platform.
日本語の概要は準備中です。原文の説明を表示しています。
Build a complete cold email outreach system — ICP definition, sequence architecture, personalization strategy, and batch-produced email sequences with CAN-SPAM/deliverability compliance. Use when "cold outreach", "cold email sequence", "outbound campaign", "prospecting emails", "sales outreach", "build outreach sequence", or any request to create systematic cold email campaigns for lead generation.
日本語の概要は準備中です。原文の説明を表示しています。
用于遇到缺陷、测试失败或异常行为，且必须在提出修复方案前调查根因的场景。未经根因分析不得只修复表象。
日本語の概要は準備中です。原文の説明を表示しています。
Systematic root-cause isolation and minimal fix proposal for software bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Code quality assurance strategies. Parent skill for quality-related skills: security (security review) and debug (systematic debugging).
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging methods, log analysis, and performance diagnostics. Use when debugging issues, analyzing errors, or troubleshooting incidents.
日本語の概要は準備中です。原文の説明を表示しています。
Research-before-coding workflow: systematically search existing solutions before custom implementation. Use when introducing new libraries, tools, or solving unfamiliar problems.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use for debugging, fixing bugs, and investigating errors.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use when asked to "fix this bug", "debug this", "why is this failing", "this is broken", "investigate this error", "track down this issue", or any debugging situation. Supports --deep flag to force full investigation.
日本語の概要は準備中です。原文の説明を表示しています。