- codex skills - copied from
~/.codex/skills/
The skills below were generated into ~/.codex/skills so they are globally available in any project.
| Name | When to use it / what problem it solves | Domain | Basic usage examples |
|---|---|---|---|
agentic-execution-context-discovery-ai-assisted-workflows |
Start here when work needs repo discovery, phased execution, or a disciplined plan before coding. Prevents guessing and premature implementation. | general | "Inspect the repo first"; "Break this feature into phases"; "Verify the call graph before editing" |
behavioral-verification-e2e-assurance |
Use for behavior-first test planning, especially when unit, integration, and Playwright coverage need to stay user-visible. | general | "Write RTL tests by role"; "Add Playwright coverage for login"; "Check error-state behavior" |
capability-driven-auth-frontend-state-ui-access-integrity |
Use when UI permissions, auth gates, or explicit client-state lifecycles risk leaking backend policy into the frontend. | full stack web dev | "Model forbidden state"; "Preserve intent through login"; "Replace role checks with capabilities" |
design-first-transformation-engineering |
Use when a change is really a data-flow transformation and needs clear inputs, outputs, invariants, and boundary normalization. | general | "Define the transform pipeline"; "Normalize input at the edge"; "Keep domain logic free of HTTP types" |
fault-tolerant-distributed-integration |
Use for Go clients, cross-service calls, direct-to-storage uploads, and any network boundary that needs deadlines and observability. | general | "Add context deadlines"; "Test with httpbin"; "Design a direct S3 upload flow" |
full-stack-web-slice-design-generator |
Use when a roadmap row needs to become a concrete full-stack slice from database truth to UI feedback. | full stack web dev | "Turn this milestone into a slice plan"; "Map server/client boundaries"; "Draft the What to Study list" |
full-stack-web-implementation-slices-table-and-repo-structure |
Use when turning a web roadmap into an implementation-slices table and repository structure with clear frontend, server, data, and shared-package boundaries. | full stack web dev | "Generate the slices table"; "Show the repo structure"; "Map feature boundaries" |
go-systems-slice-design-generator |
Use when a Go milestone needs a small sequential slice with explicit control flow, invariants, and failure paths. | go | "Plan a parser slice"; "Write the sequential baseline"; "Document error exits" |
go-implementation-slices-table-and-repo-structure |
Use when turning a Go systems roadmap into an implementation-slices table and cmd//internal/ repository structure with explicit sequential and concurrency boundaries. |
go | "Generate the Go slices table"; "Show cmd/ and internal/"; "Plan package boundaries" |
production-capacity-lifecycle-operations |
Use when adding rate limits, concurrency controls, telemetry, feature flags, or rollout safety to a service. | general | "Add a token bucket"; "Instrument logs and metrics"; "Design a safe rollout" |
resilient-client-state-query-architecture |
Use when client state needs TanStack Query, Zustand, XState, or URL-synced filters without effect spaghetti. | full stack web dev | "Model query lifecycles"; "Store filter state in the URL"; "Use XState for a branching checkout" |
resilient-concurrent-distributed-systems-design |
Use when Go concurrency or distributed retries need bounded workers, dedupe, and explicit failure-mode choices. | general | "Bound the queue"; "Add circuit breaking"; "Design idempotent retries" |
slice-implementer |
Use when implementing a bounded docs/slices/*.md design. Reconciles the document with repository rules, builds a tracer path, implements in checkpoints, and verifies behavior. |
general | "Implement slice 05"; "Reconcile this slice before coding"; "Verify the slice end to end" |
tracer-code-continuous-refactoring |
Use when a later slice must replace an earlier internal representation while preserving stable boundaries and observable behavior. | general | "Refactor in-memory storage behind an interface"; "Keep tests stable during a CRDT migration"; "Build a tracer for this boundary change" |
type-safe-boundary-validation-mutation |
Use when schemas, forms, and mutations need a single authoritative validation boundary and type-safe contracts. | full stack web dev | "Wire Zod to the form"; "Use tRPC for commands"; "Move permissions into the policy layer" |