Hook Claude Code
Runs when you submit a prompt, before the agent sees it, running an inline shell check. From 0xBeycan/genesis.
Hook Claude Code
Runs when you submit a prompt, before the agent sees it, running an inline shell check. From 0xBeycan/genesis.
Settings file Claude Code
Agent settings declaring 1 hook event (UserPromptSubmit).
Cursor rule Cursor
Genesis workshop entry — read AGENTS.md and the memory bank; the product lives in templates/.
Instructions file CodexOpenCode
Instructions for 0xBeycan/genesis, covering agents.md — genesis development, session protocol, rules and never.
Instructions file
Instructions for 0xBeycan/genesis: Forked Genesis to start your own project? Read GENESIS.md first — everything below is for developing Genesis itself.
Skill Claude CodeCodex
Skill "[object Object]" from 0xBeycan/genesis, covering when to use, steps and notes.
Skill 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.
Skill 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…
Skill 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…
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.
Skill 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.
Skill 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.
Skill 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.