Skill Claude CodeCodex
Skill "[object Object]" from 0xBeycan/genesis, covering when to use, steps and notes.
11 1mo ago A 8 tokens
original MIT
11Stars on the repository
13Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
clean-code
02Skill Claude CodeCodex
General, language-agnostic code-quality rules. Use while writing or refactoring any code in this repo to keep files small, names clear, errors handled, and boundaries respected — the baseline that keeps the vibe lane from rotting.
11 1mo ago A 50 tokens
original MIT
ideate
03Skill Claude CodeCodex
Open the option space before committing to a decision with real design freedom — a product/feature angle, a name, a design-language direction, an architecture fork with several viable shapes, or a debugging dead-end. Generate genuinely different options, score them against fixed constraints, converge to one, record…
11 1mo ago A 100 tokens
original MIT
ponytail
04Skill Claude CodeCodex
Force the laziest solution that actually works — the simplest, shortest, most minimal. Use on ANY coding task (writing, adding, refactoring, fixing, reviewing, designing code, choosing libraries or dependencies). Question whether the code needs to exist at all (YAGNI), reuse before writing, stdlib and native platform…
11 1mo ago A 126 tokens
original MIT
Skill Claude CodeCodex
Self-review a change before declaring it done. Use after finishing an edit and before wrap-session — checks the diff against the Definition of Done and the golden rules, catching boundary breaks, secrets, and missing specs/ADRs.
11 1mo ago A 50 tokens
original MIT
wrap-session
06Skill Claude CodeCodex
Close out a work session cleanly. Use at the end of ANY session in either lane (vibe or spec) to update the memory bank, rotate an overgrown progress log, re-sync thin wrappers if rules changed, and run the Definition of Done so the next agent inherits an accurate, un-rotted state.
11 1mo ago A 67 tokens
original MIT
write-adr
07Skill Claude CodeCodex
Record an architecture or tech decision as a numbered ADR. Use whenever a live alternative is rejected, or a locked choice would tempt a future undo — a stack/library pick, a boundary, a vendor swap, a job/event model, or superseding a past decision.
11 1mo ago A 57 tokens
original MIT
write-tests
08Skill Claude CodeCodex
Drive a change with tests. Use whenever you add or change behavior — turn the acceptance criteria (spec lane) or the intended behavior (vibe lane) into a failing test before the code. The how-to companion to the test-first golden rule.
11 1mo ago A 53 tokens
original MIT