The universal base layer of standards for everything a project authors, code and prose alike, derived from the ASD-STE100 controlled-language specification: a controlled naming vocabulary with a per-project glossary, small imperative units with guard…
Converts an internal artifact — a design spec, a shipped branch or feature, an API or data contract — into a self-contained handoff document an external team can read fast and act on without any internal context. Use when handing a contract, integration…
Distributes uncommitted working-tree changes back to their originating commits on a multi-commit branch using git commit --fixup and a non-interactive autosquash rebase. Use when the user wants to "distribute" fixes into existing commits, clean up a branch…
Reviews code changes for correctness, security, test coverage, and design quality, producing severity-tagged findings. Supports local changes, specific commits, or GitLab merge requests. Use when user requests a code review, asks to review a diff, branch,…
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill, or to update, audit, or modernize an existing skill's structure, frontmatter, or description.
Functional programming principles for structuring code as Data, Calculations, and Actions — immutability disciplines, stratified design (layers, abstraction barriers, minimal interfaces), duplication-removing refactorings and functional tools, timeline rules…
Drives a whole feature from a short prompt to merge-ready with minimal supervision — derives a machine-checkable done-contract, plans and executes tasks in a build→test→verify cycle, and persists all state to files on disk so the work survives context…
Produces a self-contained handoff prompt capturing the current session's state — goal, decisions, progress, key files, next steps — to paste into a fresh session and continue seamlessly. Use when the context is getting long, before compacting, or when the…