Skill Claude CodeCodex
Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.
Skill Claude CodeCodex
Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.
Skill Claude CodeCodex
Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.
Skill Claude CodeCodex
Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.
Skill Claude CodeCodex
Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.
Skill Claude CodeCodex
Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.
Skill Claude CodeCodex
Surface and resolve ambiguity before the spec is written: ask targeted questions about underspecified behaviour, edge cases and decisions, and record the answers. Use between proposal and spec whenever the proposal leaves choices open.
Skill Claude CodeCodex
Decide HOW the spec is met: the technical approach, the key architecture decisions and their trade-offs, with Mermaid diagrams where they clarify. Use after the spec is stable, before breaking work into tasks.
Skill Claude CodeCodex
Investigate a feature or bug before committing to an approach: frame the problem, survey the relevant code, and lay out options with trade-offs. Use at the very start of a non-trivial change, when the problem or solution space is still unclear.
Skill Claude CodeCodex
Turn an explored idea into a reviewable proposal: state the why, the scope (in and out), the approach, and the risks. Use once exploration converges and before writing the spec — it is the decision artifact a reviewer signs off.
Skill Claude CodeCodex
Specify WHAT must be true as a delta against the current specs — testable requirements and acceptance scenarios in the OpenSpec delta format. Use after clarify; the spec, not the code, is the source of truth for behaviour. Avoid HOW (that is design).
Skill Claude CodeCodex
Break the spec and design into an ordered, checkable task list — small, verifiable steps that map back to requirements. Use once spec and design are agreed, to drive (and track) implementation.
Skill Claude CodeCodex
Validate the implementation against the spec: walk every requirement and acceptance scenario, run the checks, and report any gaps. Use after apply, before archiving — it is the evidence the change is actually done.
Skill Claude CodeCodex
Create commits per policy (no co-author, with approval, conventional). Trigger: when committing changes.
Skill Claude CodeCodex
Set up VS Code (recommended extensions and profiles) to work well with this workspace. Trigger: when the user asks about extensions, VS Code profiles, or preparing the editor.
Skill Claude CodeCodex
Teaches how to use this AI workspace (SDD, skills, MCP), for people new to AI. Trigger: when the user asks how to use the workspace, how to start, or what SDD is.
Skill Claude CodeCodex
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Skill Claude CodeCodex
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Skill Claude CodeCodex
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Skill Claude CodeCodex
Audit the project layout/architecture against the canonical layouts (LAYOUTS + CONV-STRUCT). Trigger: architecture review.
Skill Claude CodeCodex
Audit a REASONS spec/app against a catalogue of security controls (SEC-). Trigger: security review or before approving a spec for deployment.
Skill Claude CodeCodex
Audit the tech stack against the profile's catalogue (TECH-A- / TECH-B-). Trigger: stack review.
Skill Claude CodeCodex
Audit code style/conventions against a catalogue of engineering conventions (CONV-). Trigger: style review.
Skill Claude CodeCodex
Generate application code from a user-reviewed REASONS spec — Profile A (layered FastAPI/SQLAlchemy) or B (ES modules + SRI CDN). Trigger: materialising a signed-off spec as code.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: