|

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Orchestrate comprehensive codebase research focusing on identifying and explaining relevant code with precise file and line references.

>

Core software engineering principles for code style, documentation, and development workflow. Applies when editing code, working in software repositories, or performing software development tasks.

A Claude by Anthropic skill to transform AI-generated markdown from "close enough" to "perfect." It provides comprehensive guidance for creating GitHub Flavored Markdown (GFM) that passes...

Write formal laws and covenants for codebases using proper legal-style structure. Use when establishing inviolable standards, architectural constraints, or domain-specific rules that must be...

Personalized tutoring, study strategies, lesson planning, and educational support across subjects and learning styles

|

|

Mutation must be controlled and localized. Use when reviewing code with scattered mutations or shared mutable state.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Expert in bridging the gap between business needs and technical solutions. Specializes in Requirements Engineering, BPMN, and Agile User Stories. Use when gathering requirements, creating user...

>

AI as TDD pair programmer with role-based collaboration. Use when you want to collaborate on TDD with the AI taking a specific role (driver, navigator, or alternating).

Digital equity and trauma-informed design for marginalized populations. Activate on "accessibility", "offline-first", "trauma-informed", "reentry", "recovery population", "shared device",...

>

>