roadmap-planning
Use when generating project roadmap - creates ROADMAP.md with milestones and timeline
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Use when generating project roadmap - creates ROADMAP.md with milestones and timeline
Use when generating product vision documents - creates PRODUCT_VISION, MVP_DEFINITION, TARGET_PERSONAS, VALUE_PROPOSITION
Use when creating epic structure - generates Epic INDEX.md with Kanban folders
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Create distinctive, production-grade frontend interfaces. Use in bootstrap pipeline for design docs, or as specialist for UI task implementation.
Use when starting a new project or setting up documentation structure - bootstraps docs/ folder with lifecycle documents and planning hierarchy
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when generating full planning hierarchy - orchestrates roadmap, stories, epics, and tasks creation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when generating project inception documents - creates PROJECT_CHARTER, STAKEHOLDER_MAP, TECH_RADAR, KICKOFF_CHECKLIST
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when executing implementation plans with independent tasks in the current session
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when generating architecture documents - creates SYSTEM_OVERVIEW, API_DESIGN, DATA_MODEL, SECURITY, and ADRs
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
Enforce a precise, minimal design system inspired by Linear, Notion, and Stripe. Use this skill when building dashboards, admin interfaces, or any UI that needs Jony Ive-level precision - clean, modern, minimal...
Advise on technology choices for new full-stack projects using the user's preferred stack (FastAPI + React + PostgreSQL). Use when starting a new project, discussing architecture decisions, choosing frameworks,...
Use this skill when the user asks to find, search for, or identify Nix packages. Handles searches across nixpkgs channels, finds correct attribute paths, checks versions, and can locate specific versions via ni...
Use this skill when applying home-manager or darwin configurations that require long-running builds. Automatically runs builds in background, monitors progress with appropriate polling intervals, and reports st...
Use this skill when VSCode extensions fail to build in nix configuration, when adding new VSCode extensions, or when debugging extension-related build errors. Handles systematic search across nixpkgs, vscode-ma...
Use whenever working on a python project. Manage Python projects using uv package manager with modern Python project structure.
Install Claude skills from .skill files. Use when installing a new skill provided by the user as a .skill file (which is a zip archive containing the skill directory structure).
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.