Claude Skills by godshiba

Configure the GENESIS usage sensor interactively - set the trigger cap (5h/7d), choose advise/enforce/off, toggle desktop notifications, and optionally wire the statusline readout. Persists to settings.json. Use after installing genesis-usage, or when the user asks to set up / change the usage cap, threshold, sensor mode, notifications, or the usage statusline.

The G7 session-close ritual for GENESIS projects. Runs a gate audit, appends the SESSION_LOG entry (what changed, repo state, next concrete step), and leaves the tree in a resumable state. Use when the user says close the session, wrap up, stopping here, done for today, when about to hit a usage limit, or when ending substantial work in a project with docs/registry/.

Interactively turn GENESIS gates on, warn, or off and write the choice to settings.json - no hand-editing JSON or memorizing env vars. Walks each gate (G7 session, G1 registration, G3 TODO, G2 config guard, G2 commit, pre-compaction snapshot, session resume) plus the GitHub-mirroring toggle, shows its current value, writes the change globally or per-project, and offers to record why (G6). Use when the user types /genesis:config, or asks to turn a gate on/off/warn, soften/disable/loosen a gate...

Record a non-obvious technical choice in docs/registry/DECISIONS.md with the alternatives that were rejected and why. Use when the user types /genesis:decision, says "log this decision", or right after choosing between real alternatives (library, pattern, schema, process model) in a GENESIS project.

Reorganize a repository's documentation into a clean, comprehensible structure. Inventories every doc, absorbs registry-shaped knowledge (decisions, gotchas, TODOs) into GENESIS registries, moves and merges files, flags stale content, writes missing docs from code evidence - all behind an approval gate, all reversible. Use when the user asks to organize/clean up/restructure docs, when a repo's documentation is scattered or duplicated, or when /genesis:init retrofits a repo with more than a ha...

Audit current work against all seven GENESIS gates before a commit or at the end of a task. Runs the project check command, finds unregistered files, orphan TODOs, doc-sync drift, and missing registry entries. Use when the user asks to gate-check, audit gates, verify gates, or before committing in a GENESIS project (one with docs/registry/).

Run the GENESIS prep protocol before building any project, or retrofit it onto an existing repo. Interviews for purpose/constraints/out-of-scope, investigates risks, produces an architecture contract and phase roadmap, then generates a tailored CLAUDE.md plus docs/registry/ (FILES, ISSUES, DECISIONS, LANDMINES, SESSION_LOG, ROADMAP). Use when starting a new project, when a repo has no CLAUDE.md, or when the user asks to genesis, prep, init, or bootstrap a project.

Register a bug, deferral, or known limitation as the next ISS-NNN in docs/registry/ISSUES.md with severity and an investigation path. Use when the user types /genesis:issue, says "log this bug/issue", "defer this", or when work uncovers a problem that will not be fixed in the current task in a GENESIS project.

Five-second capture of a gotcha into docs/registry/LANDMINES.md while the pain is fresh. Use when the user types /genesis:landmine (optionally with the gotcha as argument), says "that's a landmine", "log this gotcha", or immediately after a debugging detour caused by surprising behavior in a GENESIS project.

The GENESIS feedback loop. Review the session or shipped project for lessons worth promoting - recurring landmines, gate friction, missing template slots - and fold them into the project CLAUDE.md or propose upstream changes to the GENESIS plugin templates. Use when the user types /genesis:learn, asks for a project autopsy/retro, or after shipping a phase or release.

One-screen health dashboard for a GENESIS project - current roadmap phase, open issues by severity, registry sizes, last handoff age, and repo state. Read-only and fast. Use when the user asks for project status, "where are we", what's open, or wants a quick orientation in a project with docs/registry/.