Skill Claude CodeCodex
Explain why or how an existing consequential behavior, design choice, regression, threshold, or tradeoff exists from current evidence and relevant history. Use for why, how, rationale, or postmortem questions and to explain an established root cause or regression finding; do not use to reproduce, diagnose, or…
Skill Claude CodeCodex
Map affected consumers and verification obligations before implementing or reviewing a change that crosses interfaces, persistence or schemas, permissions, deployment or release boundaries, or three or more downstream branches. Use for blast-radius and what-could-break questions. Do not use for ordinary local edits…
Skill Claude CodeCodex
Find architecture deepening, terminology, and semantic-symmetry opportunities in a codebase. Use for architecture or refactoring audits, tightly coupled or shallow modules, weak test seams, scattered domain concepts, overloaded names, or sibling workflows whose ownership and transitions drift unexpectedly. Do not use…
Skill Claude CodeCodex
Design, inspect, adopt, repair, resume, or hand off multi-session project continuity. Use for continuity setup or audit, stale or conflicting startup docs, recursive checkpoints or queues, handoffs, context drift, or adjacent-repository topology. Separate durable intent, repo rules, volatile state, and history. Do not…
Skill Claude CodeCodex
Audit or govern Codex skills, external skill intake, prompt packets, or skill-like guidance for routing, placement, prompt economy, validation, distribution, provenance, or collision safety. Use alongside the platform's skill-creation guidance when creating or revising a skill. Do not use for product-specific skill…
Skill Claude CodeCodex
Use as an evidence-design overlay to create, revise, or critique charts, dashboards, analytical figures, visual tables, maps, KPI displays, evidence-rich diagrams, and decision-grade reports. Governs truthful comparison, uncertainty, documentation, restraint, accessibility, and rendered QA while medium-specific skills…
Skill Claude CodeCodex
Commit, publish or integrate, prove, and retire a completed registered Git task when the operator explicitly says yeet. Use only for that exact terminal instruction after working-thread validation exists. Do not use for ordinary commits, tests, deployments, read-only or no-diff work, or selecting integration refs.