🎯Skills25
A code exploration skill that turns the "question → read code → conclusion" process into a searchable, evidence-based document, supporting three exploration types: question (code investigation around a specific issue), module-overview (structure/boundary mapping), and spike (lightweight multi-directional technical probe).
A CodeStable skill that routes bug-fix workflows through a structured three-stage process — problem report, root cause analysis, and fix verification — ensuring every bug fix leaves behind traceable documentation.
A knowledge-capture skill in the codestable workflow that distills engineering lessons into searchable learning documents — pitfall track records bugs, traps, and failed attempts while knowledge track records best practices and reusable patterns, so teams avoid repeating the same mistakes.
A CodeStable skill that routes new feature development through a four-stage workflow — brainstorm, design, implementation, and acceptance — inserting a design document between requirements and code to prevent scope drift and leave behind a traceable record.
Stage 2 of the codestable feature workflow that translates an approved design document into code by following the checklist step-by-step, enforcing three core disciplines: write the minimum necessary code, only modify intended files, and never make decisions not covered by the design document.
Stage 1 of the codestable feature workflow that drafts a comprehensive design document (covering architecture, interface contracts, implementation hints, and test design) plus an action checklist, which serve as the single source of truth for the subsequent implementation and acceptance stages.
A CodeStable skill that generates reference documentation for each public-facing entry of a library (components, functions, CLI commands, etc.) by reading directly from source code, with a manifest-tracked batch or single-entry workflow.
A CodeStable skill that serves as the entry point for exploratory discussions — it diagnoses vague ideas through one or two rounds of dialogue and routes them to the right downstream: directly to feature design, into a feature brainstorm note, or to roadmap decomposition for large requirements.
The final acceptance stage of the CodeStable feature workflow that verifies implementation against the design document, updates architecture and requirement docs, closes roadmap items, and produces an acceptance report as the closure record.
Stage 3 of the codestable issue workflow that implements targeted bug fixes according to a confirmed root-cause analysis, validates the fix, and writes a fix-note document — enforcing strict scope discipline to prevent unrelated refactoring from contaminating the fix.
The root cause analysis stage of the CodeStable issue workflow — it reads the problem report and actual source code to identify the true root cause, assesses impact, and presents 2-3 fix options for the user to choose before any code is changed.
A skill that onboards a repository into the CodeStable workflow system, either scaffolding a fresh directory structure from scratch or auditing and migrating existing scattered documents into the standard codestable/ layout.
A CodeStable skill that serves as a one-stop architecture center — draft new architecture documents, refresh existing ones, or run architecture health checks with three modes: new, update, and check.
A CodeStable skill for behavior-equivalent code improvements — it routes refactoring work through a scan-design-apply pipeline with human checkpoints at each stage, ensuring AI only touches what it can do reliably without changing external behavior.
A CodeStable skill for recording finalized technical decisions — technology selections, architecture choices, constraints, and coding conventions — as searchable permanent documentation with full context on rationale and alternatives considered.
A CodeStable skill for drafting and updating requirements documents using user stories and plain language to describe capabilities — why they exist, how they work, and where the boundaries are.
A CodeStable skill for writing and updating project documentation — developer guides for contributors and integration partners, and user guides for end users, stored in the project's docs directory.
The first stage of the CodeStable issue workflow that captures a bug report through dialogue, producing a structured, reproducible {slug}-report.md while also determining whether to route the issue through a fast-track or standard fix path.
A CodeStable skill that organizes reusable programming patterns, library usage tips, and technical techniques into a prescriptive reference library, searchable during feature design and issue analysis stages.
A CodeStable skill that breaks down large requirements into a dependency-tracked sub-feature list with status management, serving as the seed and scheduling basis for subsequent feature development cycles.
A CodeStable skill providing a lightweight fast-forward channel for feature development — lets AI code directly while leveraging the project's accumulated CodeStable knowledge base to avoid known pitfalls and follow established conventions.
A CodeStable skill providing a lightweight fast-forward channel for small refactors — AI directly identifies 1-3 low-risk optimization points, applies classic refactoring methods, and self-verifies with tests, without the full scan-design-apply workflow.
The unified entry point for the CodeStable workflow family — it scans the repository state and routes open-ended user requests to the appropriate cs-* sub-skill (feature, bug, refactor, roadmap, etc.).
Skill
Skill