Skill Claude CodeCodex
An acceptance-contract guide for large, multi-stage coding tasks. It turns the meaning of “done” into observable checkpoints that can change when requirements or facts change.
253 2d ago A 59 tokens
original MIT
Skill Claude CodeCodex
A recurring process for improving code maintainability in controlled batches. It requires a clear goal, allowed scope, stopping rules, notes, and machine-readable state so work can continue safely over multiple iterations.
253 2d ago A 54 tokens
original MIT
Skill Claude CodeCodex
A method for finding and testing possible user problems when a product brief is incomplete. It uses product direction, user information, feedback, issues, and usage signals as evidence.
253 2d ago A 77 tokens
original MIT
Skill Claude CodeCodex
A workflow for handling Linear issues delegated to an agent. Linear is a tool for tracking work; this workflow covers finding eligible issues, claiming them, developing in isolation, delivering the result, and recording the final state.
253 2d ago A 58 tokens
original MIT
Skill Claude CodeCodex
A workflow guide for handing finished software to users through commits, releases, or deployments. A deployment puts software into its target environment, while a release makes a version available to others.
253 2d ago A 59 tokens
original MIT
Skill Claude CodeCodex
A development-stage guide for deciding how a software change should be designed before it is built. It examines the problem, evidence, ownership, alternatives, state changes, compatibility, failure handling, and the need for a lasting design document or implementation plan.
253 2d ago A 56 tokens
original MIT
Skill Claude CodeCodex
A workflow guide for the coding stage of a software task, used after the goal and design are settled. It keeps implementation focused on one clear path and leaves final checking and release to other stages.
253 2d ago A 58 tokens
original MIT
Skill Claude CodeCodex
A default workflow for managing software work from understanding the task through design, implementation, testing, review, delivery, and retrospective. It chooses the current stage, risk level, owner, and evidence needed to decide when the work is complete.
253 2d ago A 51 tokens
original MIT
Skill Claude CodeCodex
A lightweight end-of-task review that checks whether the work produced a reusable lesson for future development. It records an improvement only when the evidence supports a lasting change.
253 2d ago A 57 tokens
original MIT
Skill Claude CodeCodex
A code-review process for deciding whether completed and tested changes are safe to accept. It examines behavior, risks, contracts, tests, and maintainability, where maintainability means how easy the code is to understand and change.
253 2d ago A 58 tokens
original MIT
Skill Claude CodeCodex
Use when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard from Codex rollout logs.
253 2d ago A 44 tokens
original MIT
Skill Claude CodeCodex
A method for understanding what a development task actually requires by tracing the user's entry point through the software.
253 2d ago A 65 tokens
original MIT
Skill Claude CodeCodex
A guide for choosing tests and other checks that prove a software change works.
253 2d ago A 57 tokens
original MIT
Skill Claude CodeCodex
A set of rules for keeping project files, names, and folders organised as the codebase grows.
253 2d ago A 70 tokens
original MIT
Skill Claude CodeCodex
A focused review method for improving the structure of frontend code when a system has grown difficult to maintain.
253 2d ago A 66 tokens
original MIT
Skill Claude CodeCodex
Guidelines for building clear and accessible interactions in front-end software. They describe how links, buttons, menus, focus states, tooltips, overlays, and hover feedback should behave.
253 2d ago A 57 tokens
original MIT
Skill Claude CodeCodex
A guide for deciding where frontend styles, responsive layouts, focus states, colours, and reusable UI behaviour should live.
253 2d ago A 54 tokens
original MIT
goal-mode
18Skill Claude CodeCodex
A goal-tracking mode that keeps work moving until a clearly defined objective is complete, paused, redirected, or genuinely blocked.
253 2d ago A 45 tokens
original MIT
Skill Claude CodeCodex
Use when a complex task will span turns or sessions and needs structured working notes to survive context compression or handoff; short single-turn work does not trigger it.
253 2d ago A 37 tokens
original MIT
Skill Claude CodeCodex
A method for repeatedly observing a real product, identifying its biggest quality gap, making a focused improvement, and checking the result again.
253 2d ago A 79 tokens
original MIT
Skill Claude CodeCodex
A guide for separating user-interface code from application logic in frontend apps. It explains where shared state, business actions, and display-only components should live.
253 2d ago A 57 tokens
original MIT
Skill Claude CodeCodex
A governance guide for maintaining the instructions that AI agents use in a project, including AGENTS.md files, commands, skills, references, and checking scripts.
253 2d ago A 58 tokens
original MIT
Skill Claude CodeCodex
A process for finding and safely removing dead code in the NextClaw repository. Dead code is code that is no longer used, such as obsolete files, exports, or dependencies.
253 2d ago A 71 tokens
original MIT
Skill Claude CodeCodex
A release guide for building, publishing, recovering, and smoke-testing the NextClaw Desktop application, which is a desktop version of NextClaw.
253 2d ago A 25 tokens
original MIT