cursorrules
01Cursor rule Cursor
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
2 2mo ago A 297 tokens
original MIT
Instructions file CodexOpenCode
Instructions for HumanDealer/vibeproof, covering agents.md — operating contract for ai coding agents, the non-negotiables (memorize these), the standard workflow (every change), before you say "done" and when something breaks.
2 2mo ago A 893 tokens
original MIT
Instructions file
Instructions for HumanDealer/vibeproof, covering claude.md — claude code operating contract, the non-negotiables, claude code specifics and the standard workflow.
2 2mo ago A 483 tokens
original MIT
code-review
04Skill Claude CodeCodex
Use before merging a diff. A structured review pass for correctness bugs, safety issues, and needless complexity.
2 2mo ago A 24 tokens
original MIT
Skill Claude CodeCodex
Use when something is broken — a bug, a test failure, unexpected behavior. Enforces the no-fix-without-root-cause loop.
2 2mo ago A 34 tokens
original MIT
plan
06Skill Claude CodeCodex
Turn docs/PRD.md into docs/PLAN.md — an ordered, checkbox build plan with architecture, risk gates, and a test list. Use after /spec, before any code. The plan survives session compaction; conversation context does not.
2 2mo ago A 52 tokens
original MIT
Skill Claude CodeCodex
Use when you learned something durable — a decision, a hard-won lesson, a useful reference. Captures it into the memory wiki so it compounds.
2 2mo ago A 34 tokens
original MIT
ship
08Skill Claude CodeCodex
Use when a change is ready to land. Runs the full sequence — branch, quality gate, commit, push, PR — so nothing gets skipped.
2 2mo ago A 32 tokens
original MIT
spec
09Skill Claude CodeCodex
Turn a plain-language product idea into a PRD.md. Use when a non-technical expert describes what they want to build ("I want an app that...", "build me a tool for..."). Interviews to extract the non-obvious requirements, then writes docs/PRD.md.
2 2mo ago A 59 tokens
original MIT
tdd
10Skill Claude CodeCodex
Write failing tests BEFORE implementation, from the test list in docs/PLAN.md. Use when starting to build a step. The test is the contract — "tests pass" only means something when the test exercises the change. Closes the "0 tests passes trivially" loophole.
2 2mo ago A 60 tokens
original MIT