Design, create, revise, audit, validate, or optimize reusable agent skills and SKILL.md packages across platforms. Use for trigger precision, structure, progressive disclosure, token efficiency, prompt evals, or converting repeated workflows into portable skills. Do not use for AGENTS.md, skill fusion, or host…
Create, draft, audit, revise, or migrate root and nested repository AGENTS.md files from repo evidence. Use when the user asks to create or review an AGENTS.md, improve repository coding-agent instructions, convert CLAUDE.md-style guidance into AGENTS.md, or decide instruction scope in a monorepo. Primary for…
Baseline overlay for routine thin HTTP, gRPC, or message-consumer implementation and review; use backend-systems-guidance for multi-layer, data-access, transaction, reliability, or trust-boundary work. Compose with matching implementation guidance. Not for outbound-client-only or security-audit tasks.
Canonical overlay for non-trivial server-side networked implementation and review involving multi-layer architecture, data access, reliability, trust boundaries, or deeper testing; use backend-guidance for thin routine handlers. Compose with matching implementation guidance for APIs, queues, repositories…
Bash implementation and review guidance for automation and repository scripts; not for one-off command execution, POSIX sh, or release-workflow design where project-release-maintainer is primary. Covers safe quoting, explicit failure handling, process ownership, and maintainable shell boundaries.
C++ implementation and review guidance for modern ownership, type safety, API design, and tests; use coding-guidance-qt when QObject lifetime, signals and slots, QWidget/model-view behavior, Qt threading, or Qt build tooling is the main concern. Portable across C++17/20/23 repositories and build systems.
Go terminal UI implementation and review guidance for interactive Bubble Tea state machines. Includes Huh only when embedded in Bubble Tea; use coding-guidance-go for standalone or one-shot Huh prompts and other non-TUI Go work. Covers Bubbles, Lip Gloss, key bindings, focus, and supported Charmbracelet major versions.
Go implementation and review guidance for non-interactive CLIs, libraries, workers, and services; use coding-guidance-go-tui for interactive Bubble Tea and go-testing-with-testify for testify-focused test work. Covers errors, contexts, concurrency, package boundaries, standard tests, and measured performance.
Python implementation and review skill. Use when writing, modifying, refactoring, or reviewing Python code, especially production Python that needs clear contracts, type safety, testability, and maintainable module boundaries. Portable across Python repos and tooling stacks.
Qt C++ implementation and review guidance for QObject, QWidget/model-view, signals and slots, thread affinity, .ui forms, and Qt build tooling; use coding-guidance-cpp for non-Qt C++ design. Portable across Qt5/Qt6 repositories with a QWidget desktop focus.
Workflow for context packets, context audits, compaction, handoffs, session memory, and deciding what AI-agent context to load, retrieve, trim, summarize, refresh, or omit. Use for context rot, context flooding, stale or missing context, task switching, and long-running agent sessions. Do not use when prompt wording…
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.
Template for authoring or revising the thin repo-local overlay generated by the development contract system. Use when writing overlay guidance that names a target repo's policy path, plan directory, checker command, lifecycle helper, or validation profiles; use development-contract-process for ordinary work in a repo…
Build a portable change-contract system for any repository. Use when creating or porting a repository workflow based on tracked feature records, lifecycle directories, a policy file, a checker, a lifecycle transition helper, and aligned docs/tests.
Companion overlay to documenter for user-directed, multi-round coauthoring of specs, PRDs, proposals, ADRs, decision docs, and similar technical documents. Use when the user wants to shape or approve structure, set checkpoints, iterate section by section, or preserve decisions across rounds. Document size neither…
Evidence-backed review, writing, revision, or restructuring of durable READMEs, specs/ADRs, agent guides, and public API/release docs when claims or structure need judgment. Route AGENTS.md to agents-md-generator; add documenter-coauthoring for staged work. Let matching domain skills lead when code, packaging, or…
Creative retrospective workflow that uses simulated dream imagery and metaphor to defamiliarize recent experience, then turns it into grounded hypotheses and next observations or actions. Use only when the user explicitly asks to dream, sleep on something, use a dream or nightmare lens, or reflect through metaphor. Do…
Fuse two or more bounded agent skills into one new or explicitly named existing package without accidental capability loss. Use when asked to merge, fuse, consolidate, deduplicate, fold, or unify local, remote (including skills.sh), or inline sources into one package. Do not use for runtime composition, single-skill…
Use when writing, reviewing, or hardening Go tests that rely on stretchr/testify — assert, require, mock, and suite — including table-driven tests, subtests, parallel tests, mocks versus hand-written fakes, error-wrap assertions, and flaky test triage with -race and -count.
Use for live browser investigation with playwright-cli, or for writing, debugging, reviewing, or hardening Playwright tests in an existing working harness across Node, Python, .NET, or Java. Covers flake triage, locator refinement, visual and responsive checks, test structure, fixtures, auth-state use, and mock…
Project overlay for config precedence, defaults, parsing, normalization, path helpers, and deterministic tests at those seams. Not for general test strategy or unrelated test implementation.
Project overlay for discovering and reporting repository-specific completion checks for routine repo-owned changes. Use when the validation path is unclear; prefer specialized project overlays for config, platform, release, or vendor concerns.
Diagnostic project overlay for environment-dependent build, install, startup, CI, container, headless, terminal, or runtime failures. Not for ordinary logic bugs or known release packaging changes.
Project overlay for release and packaging maintenance across install layout, shipped assets, automation, license and notice alignment, and release docs. Not for content-only documentation or publishing without explicit authorization.