Loading...
Loading...
Found 44 Skills
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
This skill should be used when the user says "update CLAUDE.md", "refresh CLAUDE.md", "sync CLAUDE.md with the codebase", "reorganize CLAUDE.md", "optimize project instructions", or when CLAUDE.md is stale, verbose, or out of sync.
This skill should be used when the user asks to "create a skill", "build a skill", "write a skill", "improve skill structure", "understand skill creation", or mentions SKILL.md files, skill development, progressive disclosure, XML structure, or bundled resources (scripts, references, assets). Comprehensive guide for creating effective Claude Code skills.
Creates well-structured Agent Skills following best practices. Use when building new skills for Claude Code, designing skill directory structures, writing SKILL.md files, or improving existing skills with progressive disclosure patterns.
Comprehensive knowledge of all 23 Gang of Four design patterns with progressive disclosure (Quick/Practical/Deep), pattern recognition for problem-solving, and philosophy-aligned guidance to prevent over-engineering.
Navigation and user flow patterns including routing, state management, progressive disclosure, and game progression. Use when designing multi-step flows, game phases, or navigation structures. (project)
The foundational context engineering skill — start here when exploring the discipline. This skill should be used when the user asks to "understand context", "explain context windows", "design agent architecture", "debug context issues", "optimize context usage", or discusses context components, attention mechanics, progressive disclosure, or context budgeting. Also activates when the user mentions "context engineering" or "context-engineering" for foundational understanding of AI agent context systems.
Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates are low, when users skip onboarding and never return, when onboarding flows are being scoped for the first time, or when audience research shows users not finding key features.