backend-guidance
Overlay for server-side networked code — HTTP handlers, gRPC services, message consumers. Use alongside the repo's implementation skill when implementing or reviewing backend logic.
coding-guidance-cpp
C++ implementation and review skill. Use when writing, modifying, or reviewing C++ code — feature work, bug fixes, refactors, or code review. Portable across C++ repos and build systems.
development-contract-core
Portable workflow for repos that require tracked change contracts, verifier evidence, and smallest-proof validation. Use when a repo has a contract policy file or enforced feature-plan checker.
documenter
Documentation skill for README, API docs, code comments, release docs, and AI-friendly project documentation.
frame-development-contract
Repo-local overlay for the development contract system in this frame. Use when work may trigger a tracked change contract and you need the repo's concrete policy, plan directory, or validation profiles.
project-config-and-tests
Generic overlay for config contracts, defaults, path helpers, and deterministic test coverage.
project-core-dev
Overlay for day-to-day feature work and bug fixes in repo-owned code. Provides a validation checklist for build, test, format, and analysis. Use alongside the repo's principle skill.
project-platform-diagnose
Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, and runtime smoke checks. Portable across C++ projects.
project-release-maintainer
Overlay for release-facing docs, install layout, workflows, licenses, and hygiene scripts. Portable across repos with a release/packaging pipeline. Use for publication-facing changes.
project-vendor-boundary
Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.
recursive-thinking
Recursive self-questioning heuristic for stress-testing a plan, diagnosis, design, review, or recommendation before acting. Use when the user asks to use recursive thinking, go deeper, interrogate assumptions, pressure-test an approach, ask why/how questions, or find what would change the conclusion. Avoid for simple factual lookups or low-ambiguity tasks.
security
Security skill for threat modeling, secure defaults, and security-focused code review in generic software projects.
thinking
Planning and design skill. Merges convergent planning, focused inquiry, and kaizen-style incremental improvement. Use for quick-to-medium planning tasks where structured thinking improves the outcome. Lighter than a full plan document — heavier than just asking the LLM to think.
ui-guidance
Overlay for graphical UI and web frontend code. Use alongside the repo's implementation skill when implementing or reviewing UI changes.