ralfyishere/rules-with-receipts

ralfyishere/rules-with-receipts

Skill Claude Code

Actively try to disprove or break your own answer before presenting it. Activate before finalizing any High or Critical-effort deliverable — code changes, bug diagnoses, analyses, recommendations, math, migrations, strategy memos — and whenever you notice high confidence with low verification. Trigger signals: you're…

ralfyishere/rules-with-receipts

Skill Claude Code

Keep edits controlled, reversible, and easy to review. Activate whenever modifying existing artifacts - code, documents, configs, prompts, workflows, plans - especially edits to things that currently work, changes others depend on, batch modifications, or anything hard to undo. Trigger signals: "update", "refactor"…

ralfyishere/rules-with-receipts

Skill Claude Code

Understand the relevant code, conventions, and blast radius before writing or changing code in an existing project. Activate before implementing any feature, fix, or refactor in a codebase you didn't write this session - especially "add X to the app", "where should this go", "integrate with", or any multi-file change.…

ralfyishere/rules-with-receipts

Skill Claude Code

When a published claim is corrected, retracted, downgraded, superseded, or reversed, sweep EVERY surface that restates it - sibling docs, other repos, mirrors, READMEs, indexes, memory files - and banner or supersede each in the SAME closeout before it's done. Activate on "I corrected/retracted/updated X", a metric…

ralfyishere/rules-with-receipts

Skill Claude Code

Debug systematically instead of guessing - symptom, reproduction, hypotheses, discriminating tests, evidence, root cause, fix, regression test. Activate whenever something is broken, failing, wrong, or behaving unexpectedly - error messages, failing tests, crashes, wrong output, performance regressions, "it worked…

ralfyishere/rules-with-receipts

Skill Claude Code

Break hard tasks into smaller solvable units with explicit dependencies and unknowns. Activate when a task feels too big to plan in one pass — large features, migrations, research questions with many sub-questions, multi-part documents, business analyses, gnarly debugging with several possible fault lines, or anything…

ralfyishere/rules-with-receipts

Skill Claude Code

Delegate work to subagents, background tasks, or parallel workers effectively - and verify their outputs before relying on them. Activate when spawning agents, fanning out searches or reviews, orchestrating multi-agent workflows, running background tasks, or incorporating any output produced outside your own context.…

ralfyishere/rules-with-receipts

Skill Claude Code

Writing down a known defect does not resolve it. Activate when about to ship something with a "known limitation", "known issue", "caveat", "disclosed", "we're aware", "for now", "not yet handled", or "advisory" note; a TODO/FIXME left in shipped code; a review that found a defect you are documenting instead of fixing…

ralfyishere/rules-with-receipts

Skill Claude Code

Keep generating and testing NEW hypotheses against a live domain instead of stopping at a closed verdict - observe what is actually succeeding, log a belief-state with credence, attack every confirmation streak. Activate in any standing investigation (an edge, a root cause, a market, a growth lever, a performance…

ralfyishere/rules-with-receipts

Skill Claude Code

Generate different options before choosing - for brainstorms, naming, design alternatives, and any open problem where the first workable idea becomes the only idea. Activate on "brainstorm", "give me ideas/options/names", "what could we build", "how else could we do this", first attempts on open-ended problems, and…

ralfyishere/rules-with-receipts

Skill Claude Code

Pick how much rigor a task deserves - the Low/Medium/High/Critical tier that other skills key off. Use when torn between answering quickly and investigating, when deciding whether to verify or trust knowledge, and whenever stakes signals appear: "production", "customer-facing", "important", money, legal, deletion…

ralfyishere/rules-with-receipts

Skill Claude Code

Test a load-bearing efficacy claim by running the cheapest experiment that could falsify it - with real data and confidence intervals - instead of reasoning about whether it works. Activate before relying on or shipping any efficacy claim: an inherited system's supposed edge, a prompt/rule/config change you believe…

ralfyishere/rules-with-receipts

Skill Claude Code

Recover cleanly when work goes sideways mid-task - failed fixes, broken state, cascading patches, a working tree worse than where you started. Activate when a second consecutive attempt at the same problem fails, when tests that were green are now red after your changes, when you notice patch-on-patch layering, or…

ralfyishere/rules-with-receipts

Skill Claude Code

After solving a non-trivial problem, capture the reusable approach as a short learning note in .claude/learnings/ before calling the work complete. Activate after: a hard bug is solved, a tricky architecture or strategy decision lands, a difficult prompt is fixed, a mistake occurs that must not repeat, an eval failure…

ralfyishere/rules-with-receipts

Skill Claude Code

Identify what could go wrong before it goes wrong. Activate when designing anything new, before committing to a plan or recommendation, before shipping changes with real blast radius, and when evaluating ideas, strategies, or proposals. Trigger signals: "will this work?", "review this plan", "any risks?", designing an…

ralfyishere/rules-with-receipts

Skill Claude Code

Project the trajectory before committing - pre-register dated, credenced predictions about what breaks, what becomes necessary, and what pays off 5/10/20 steps ahead, then resolve them when the future arrives and score your calibration. Activate when starting any build, plan, or strategy; making architecture, roadmap…

ralfyishere/rules-with-receipts

Skill Claude Code

The high-rigor operating mode that orchestrates the full skill pack in order for complex, high-stakes, ambiguous, multi-step, strategic, technical, or quality-sensitive work. Activate when a task is important enough that a rushed answer would be a disservice - major features, migrations, hard bugs, strategy documents…

ralfyishere/rules-with-receipts

Skill Claude Code

Design the human's part of a task when a step needs their hands - browser logins, account creation, approvals, physical-world actions, anything outside your tool reach. Activate whenever you're about to ask the user to do something you cannot do, especially multi-step flows you can't observe (OAuth/device flows…

ralfyishere/rules-with-receipts

Skill Claude Code

Decode what the user actually needs before optimizing the wrong thing. Use when a request has vague referents ("fix it", "make it better", "clean this up", "improve this"), looks like a symptom-fix ("increase the timeout", "make this function faster"), is oddly specific with missing context, or would be strange taken…

ralfyishere/rules-with-receipts

Skill Claude Code

Before committing real effort to a chosen approach, spend a cheap cycle to find the higher-leverage path - an existing solution/tool/dataset, a more efficient method, or a smarter composition - instead of grinding the first workable idea on one track. Activate when about to build a tool, collect data the slow way, or…

ralfyishere/rules-with-receipts

Skill Claude Code

Trust current observed state over memory, docs, or assumptions. Activate before making any claim about the current state of files, code, configs, data, tools, UI, or provided documents - and before editing anything. Trigger signals: about to say "the file contains", "the test passes", "this function does", "the config…

ralfyishere/rules-with-receipts

Skill Claude Code

Handle context carefully across long sessions - distinguish durable facts, temporary context, stale assumptions, and user preferences; re-verify before relying on old context. Activate in long or resumed sessions, after context compaction or summarization, when recalling something established "earlier" in the…

ralfyishere/rules-with-receipts

Skill Claude Code

Handle explicitly delegated judgment - "do whatever you think is needed", "you decide what's next", "keep going", standing autonomous sessions. Activate when the user hands you the prioritization itself rather than a task: no deliverable is named, and choosing what to work on IS the work. Trigger signals: "do what you…

ralfyishere/rules-with-receipts

Skill Claude Code

Present answers in the most usable format for the reader's next action - direct answer, table, checklist, numbered plan, executive summary, decision memo, email draft, prompt block, implementation plan, or critique. Activate when composing any substantial response, when a deliverable's format is unspecified, or when a…