diagram-gen
Generate architecture, sequence, state, and ERD diagrams for code understanding. Use when user wants to visualize code structure or document systems.
Discover business sales marketing skills, compare source repositories and read the instructions for each workflow.
Generate architecture, sequence, state, and ERD diagrams for code understanding. Use when user wants to visualize code structure or document systems.
Capture task outcomes and patterns after completing work. Use after /verify or when a task succeeds/fails to enable adaptive skill evolution.
Break down tickets or requirements into actionable task checklists. Use when user wants to plan a feature, start a new task, or decompose work before coding.
Maintain a lightweight backlog of high-value tasks discovered during work.
Document architectural decisions with context and consequences.
Ask clarifying questions and get approval before implementation.
Analyze and document the impact of planned changes.
Expert in statistical analysis for blind A/B and ABX audio testing. Validates randomization, calculates statistical significance, and ensures proper experimental design. Use when implementing A/B test features...
Handle customer inquiries and provide support assistance
機能設計書を作成するための詳細ガイドとテンプレート。機能設計書作成時にのみ使用。
プロダクト要求定義書(PRD)を作成するための詳細ガイドとテンプレート。PRD作成時にのみ使用。
Quick revenue overview and sales metrics. Shows today/week/month sales, recent orders, top products, and revenue trends. Use for daily business checks, launch tracking, or financial reporting. Triggers on "sale...
Guide for spec-based agent-driven development using structured requirements (EARS notation), technical design documentation, and implementation planning. Use when users want to build features using a specificat...
Transform ideas into validated, dependency-mapped Linear stories. Activates when user wants to develop a new feature idea, create Linear stories from a concept, brainstorm and plan implementation, or mentions "...
Deterministic team development workflow for Claude Code. Enforces a mandatory sequence of phases (Setup → Brainstorm → Plan → Execute → Quality Check → Ship) with Linear integration, TDD requirements, and quali...
Act as Bob Moesta, innovation expert and co-creator of Jobs to Be Done theory. Use when users want advice on innovation, product development, customer research, sales strategy, understanding why customers buy,...
When the user asks about roadmap planning, sprint planning, milestone estimation, or capacity planning
Rewrites marketing copy, formats policy snippets, and summarizes metrics using a consistent brand and reporting style. Use when tone guidance, policy formatting, or reporting voice is required.
Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not...
Defines the overall project purpose, operating model, and roles for Hackathon II – Todo Spec-Driven Development. Always load for any project-related task.
ディーラー向け車両提案書を自動生成するスキル。 顧客の予算・家族構成・用途から最適な車両を選定し、提案書を作成する。 「提案書」「車両提案」「レコメンド」「おすすめの車」「proposal」などのキーワードで発動。 Use w...
Create or update project specifications interactively through an interview process. Use when starting a new project, adding major features, or when the user asks to create a spec, plan a project, or define requ...
Knowledge engineering pipeline that transforms messy human intent and repository analysis into living operational domain profiles
This skill should be used when the user asks to "reflect on patterns", "generate rules from sessions", "consolidate memory", "analyze session patterns", "learn procedures and workflows", "create procedural know...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.