Browse skills

Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.

The English summary is being prepared. Showing the original description.

Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.

The English summary is being prepared. Showing the original description.

Use for complex coding requests that need a structured implementation plan with dependencies, checkpoints, and verification criteria.

The English summary is being prepared. Showing the original description.

Use when work needs deeper thinking, less generic output, repo evidence, tradeoffs, monitoring signals, or stronger quality discipline.

The English summary is being prepared. Showing the original description.

Use when an approved plan has independent tasks ready for delegated execution with fresh subagents and two-stage review.

The English summary is being prepared. Showing the original description.

Use after UI implementation for mechanical source checks and a rendered or fresh-eyes review.

The English summary is being prepared. Showing the original description.

Use for security review, audit, hardening, compliance, DevSecOps, network, infrastructure, or application security with focused references.

The English summary is being prepared. Showing the original description.

Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.

The English summary is being prepared. Showing the original description.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup

The English summary is being prepared. Showing the original description.

Use when asking project status, next priority, sprint health, blockers, deadlines, risk register, or daily brief generation.

The English summary is being prepared. Showing the original description.

Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.

The English summary is being prepared. Showing the original description.

Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.

The English summary is being prepared. Showing the original description.

Use when frontend, backend, mobile, data, DevOps, or security work needs domain routing and at most four focused references.

The English summary is being prepared. Showing the original description.

Use when designing, auditing, or redesigning a web UI; select fast, prototype, or studio from the requested scope.

The English summary is being prepared. Showing the original description.

Use when implementing web UI in React, Next.js, Tailwind, CSS, or GSAP against an approved design, fast-path brief, or prototype UX contract.

The English summary is being prepared. Showing the original description.

Use before build, fix, debug, review, or docs implementation; converts prompts into structured intent JSON with goal, constraints, and routing.

The English summary is being prepared. Showing the original description.

Use when work is ambiguous or has multiple viable paths; compares options, assumptions, evidence, tradeoffs, and the best next action.

The English summary is being prepared. Showing the original description.

Use when starting any CodexAI task; load this baseline before routing, editing, or claiming work is done.

The English summary is being prepared. Showing the original description.

Use for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.

The English summary is being prepared. Showing the original description.

Use at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.

The English summary is being prepared. Showing the original description.

Use when work needs Scrum roles, ceremonies, backlog refinement, sprint planning, story delivery, release readiness, or role handoffs.

The English summary is being prepared. Showing the original description.

Use for bugs, test failures, broken behavior, or unexpected results; enforces 4-phase root-cause debugging before fixes.

The English summary is being prepared. Showing the original description.

Use before feature, bugfix, or refactor implementation when behavior can be tested; enforces Red-Green-Refactor discipline.

The English summary is being prepared. Showing the original description.

Use when about to claim work is complete, fixed, or passing; run verification and read the output before any success claim.

The English summary is being prepared. Showing the original description.