Skill Claude CodeCodex
Create and update a readable HTML progress report for a project, migration or multi-agent delivery. Use when the user needs every slice, completed/total scores, evidence and concrete next actions. Uses authoritative JSON data and a bundled Python renderer with a compact human-facing layout.
Skill Claude CodeCodex
Apply a strict Clippy lint policy to a Rust codebase and drive it to zero warnings. Use when asked to tighten lints, enable pedantic/nursery/restriction lint groups, enforce unwrap/cast/indexing discipline, or replicate a strict lint setup in a Rust project.
Skill Claude CodeCodex
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.
Skill Claude CodeCodex
Start new work by checking existing decisions and implementation, investigating the important unknowns, and holding a focused owner Q&A before expensive implementation or verification. Use at the beginning of every new task or materially changed objective. Scale the process to the task; fully specified small work…
Skill Claude CodeCodex
Coordinate ownership, dependencies and shared resources for work that needs several contributors. Use after scope and slices are defined; skip for work one owner can complete without coordination.
Skill Claude CodeCodex
Deliver one approved, complete user journey through implementation, review, fixes, verification and publication. Use for bounded team work and behaviour-preserving migrations; retain one accountable owner and follow delegated work to completion.
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: