Loading...
Loading...
Found 1,947 Skills
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Use when the user wants to bootstrap a target codebase for AI-driven development with Claude Code. Generates a concise CLAUDE.md grounded in the actual stack (build tools, test runner, code style), creates a docs/ folder skeleton (designs/, prd/, plans/), and seeds conventions (conventional commits, plan-checkbox format, where designs and PRDs live). Triggers on "init Claude in this repo", "set up CLAUDE.md", "bootstrap docs folder", "prepare this project for Claude Code", "scaffold AI dev workflow", "/init this project".
Creates an Architecture Decision Record (ADR) documenting a significant technical decision. Follows the standard ADR format with context, decision, and consequences. Invoked when the user says "write an ADR", "document this decision", or "create an architecture record".
Use when the user wants to brainstorm an idea or design a feature/spec. Explores intent and requirements through dialogue, then writes a spec document to docs/spark/ and STOPS. Does not auto-chain to implementation planning or any other skill.
This skill should be used when the user asks to "update my README", "refresh the README", "README is outdated", "sync README with the codebase", "improve my README", "keep README up to date", "fix the README", "my README is stale", "update the readme file", "README needs updating", "update readme from git history", or "readme is out of date".
Initialize IDD structure in a project. Checks existing state, creates directory structure, and generates templates. Use /intent-init to set up Intent-driven development in current project.
AI-Driven Specification-Driven Development (SDD) workflow orchestrator - guides skill selection and general SDD methodology
Technical writing skills specialized in drafting, structuring, and visualizing technical notes. Understand the essence from source code and official documents, and create explanatory articles in an engineer-friendly format.
Use when an approved Spec Kit `plan.md` + `spec.md` must be decomposed into dependency-ordered `tasks.md`, or when `tasks.md` is missing/stale after planning or reconciliation changes.
Generate Product Requirements Documents through structured discovery. 3 phases: Discovery interview, Analysis & Scoping, Technical Drafting. Use when: defining new products, planning features, documenting requirements. Triggers on "create PRD", "define product", "product requirements", "write PRD".
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
Documentation pipeline automation and docs-as-code workflows