Loading...
Loading...
Found 100 Skills
Use after brainstorming/design phase to create detailed implementation plans. Creates step-by-step plans clear enough for execution by any developer.
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Claude Code Advanced Development Guide - A comprehensive tutorial covering tool usage, REPL environment, development workflows, MCP integration, advanced patterns, and best practices. Ideal for learning Claude Code's advanced features and development techniques.
Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
Use this when you need to start feature development isolated from the current workspace, or before executing implementation plans — ensure an isolated workspace exists via native tools or the git worktree fallback mechanism
Development workflow and quality gates for the Bun + TypeScript stack. **ALWAYS use before commits** to ensure quality gates are met. Also use when starting development or when user asks about workflow process. Examples - "before commit", "quality gates", "workflow checklist", "bun commands", "pre-commit checks".
Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation. Use when user wants to start a new project, improve project structure, add development tooling, or establish professional workflows.
Compound Engineering workflow for AI-assisted development. Use when planning features, executing work, reviewing code, or codifying learnings. Follows the Plan → Work → Review → Compound loop where each unit of engineering makes subsequent work easier. Triggers on: plan this feature, implement this, review this code, compound learnings, create implementation plan, systematic development.
Use when implementing features from a spec or requirements document, doing multi-phase work, or when you need structured Analyze-Plan-Ask-Execute-Review cycles to prevent ad-hoc coding and ensure spec-aligned, pattern-consistent implementations
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
Apply a Content Driven Development process to AEM Edge Delivery Services development. Use for ALL code changes - new blocks, block modifications, CSS styling, bug fixes, core functionality (scripts.js, styles, etc.), or any JavaScript/CSS work that needs validation.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always