Skill Claude CodeCodex
Use when the user wonders how hard it is to implement a software requirement. How much is already implemented, what could be re-used, what is missing entirely and needs to be added from scratch.
Skill Claude CodeCodex
Resolves every detailed decision needed to implement a chosen approach to a software requirement, producing a plan an agent can execute without further questions. Walks through the future implementation, surfaces every decision, edge case and blocker, and settles each one with the user before any code is written. The…
Skill Claude CodeCodex
Decide what kind of test to write for a change in a Ruby on Rails app so you get solid coverage without redundant or needlessly slow tests. Assumes RSpec/Capybara conventions (feature specs, request specs, unit specs). Use whenever you're about to add or change tests in a Rails project and neither the repo nor your…
Skill Claude CodeCodex
Get an independent second opinion on the code you just wrote — an outside pass for correctness, simplicity, regressions, and missing tests that you're too close to the work to catch — and fold the valid feedback back in. Use after implementing a change and before handing it to the user, or whenever you want to…
Skill Claude CodeCodex
Make sure your work lands on a private feature branch and avoid breaking a protected branch like main or master. Use before you start making changes for a non-trivial task, or whenever you notice you're about to commit unreviewed work directly onto a protected branch.
Skill Claude CodeCodex
Explores different approaches to a software requirement and compares their trade-offs, so the user knows which approaches are workable and at what cost. Scans the codebase for what exists and what will get in the way, generates genuinely different solution approaches, compares them from a bird's-eye view, and tracks…
Skill Claude CodeCodex
Carry a set of requirements all the way to a tested, self-reviewed implementation that's ready to hand back, deciding open questions on your own and only interrupting for true showstoppers. Use when the user asks you to implement a feature, task, or ticket autonomously, end-to-end, or with minimal supervision — e.g.…
Skill Claude CodeCodex
Confirm a change hasn't broken any current or past feature by running every check the repo has, which means enumerating its test runners and linters first (from CI config and project docs, so no linter is forgotten), then running the whole suite by the fastest route (CI, parallel, or local) and fixing failures…
Skill Claude CodeCodex
Make a working change simpler and smaller, with fewer concepts for a reader to understand. Find missing structure (the same thing built twice, steps repeated with one difference, mechanisms more general than their uses, existing code that could serve the change) and local waste (checks nothing can trigger, wrappers…
Skill Claude CodeCodex
Slows down a conversation where the agent raised more open questions, decisions or findings than the user can take in at once. Goes through them one item at a time, each explained in plain language with plenty of context, a few clear options and a recommendation, and waits for the user's choice before moving on. Use…
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: