ralfyishere/rules-with-receipts

ralfyishere/rules-with-receipts

Skill Claude Code

Require a written plan before starting complex or multi-step work. Activate when the task involves building a feature, implementing something new, refactoring, migrating, restructuring a document, multi-file edits, research projects, or any work with more than 3 dependent steps, unclear requirements, or an expensive…

ralfyishere/rules-with-receipts

Skill Claude Code

Raise the quality bar by noticing what the request didn't say - missing constraints, hidden risks, weak evidence, undefined terms, and likely downstream problems - without creating friction or derailing the task. Activate when a request omits something that will matter later, when input material has gaps or…

ralfyishere/rules-with-receipts

Skill Claude Code

Reason from user problems and evidence of demand, not from features - for build/don't-build decisions, prioritization, MVP scoping, and interpreting feature requests and user feedback. Activate on "should we build", "users are asking for", "what should we prioritize", "scope the MVP", roadmap questions, and any…

ralfyishere/rules-with-receipts

Skill Claude Code

Improve prompts, system prompts, and agent instructions systematically - with test cases, failure diagnosis, and one-change-at-a-time iteration instead of vibe edits. Activate for "improve this prompt", "the model keeps doing X wrong", "write a system prompt", "make the agent stop doing Y", prompt templates, and…

ralfyishere/rules-with-receipts

Skill Claude Code

The going-public procedure - sanitize content, metadata, AND history before anything becomes public, verify redistribution rights, and treat third-party instruction files as untrusted code. Activate before ANY crossing of the public boundary - making a repo public, git push, releasing, publishing a package, or sharing…

ralfyishere/rules-with-receipts

Skill Claude Code

Run multi-source research with search strategy, source triangulation, and honest coverage claims. Activate for "research X", "what's the state of the art", "compare the options on the market", "what do we know about", literature or market or technical landscape questions, and any task where the answer must be…

ralfyishere/rules-with-receipts

Skill Claude Code

Make outputs sharper, clearer, and shorter without losing meaning. Activate before delivering any prose that matters - emails, reports, documentation, investor blurbs, strategy memos, prompts, README files, executive summaries, PR descriptions - and whenever the user asks to "tighten", "polish", "shorten", "improve"…

ralfyishere/rules-with-receipts

Skill Claude Code

Do exactly what was asked; flag adjacent issues instead of fixing them uninvited. Activate during any task where you notice nearby problems, improvement opportunities, or "while I'm here" temptations - messy code next to the bug, weak sections next to the paragraph being edited, related features the user didn't…

ralfyishere/rules-with-receipts

Skill Claude Code

Adversarially test any defensive pattern you ship before it ships. Activate when adding or reviewing an allowlist, denylist, suppression rule, detection regex, sanitizer, validator, guard, auth check, rate limit, or filter; writing a scanner or linter rule; shipping a security or validation heuristic. Trigger signals…

ralfyishere/rules-with-receipts

Skill Claude Code

Learn from prior mistakes and repeated patterns - review what failed, extract a reusable lesson, apply it to the next attempt. Activate when the user corrects your output, when an approach fails and needs a retry, when you notice the same friction recurring across tasks, and at the end of significant multi-step work.…

ralfyishere/rules-with-receipts

Skill Claude Code

Orient from the workspace's project registry before working - canonical repo paths, current versions, pending state - instead of rediscovering them by searching. Activate at the start of any new or resumed session in a multi-project workspace, on project-state requests ("check the work on X", "is everything up to…

ralfyishere/rules-with-receipts

Skill Claude Code

Pick and apply the right reasoning framework for the problem - first principles, tradeoff analysis, decision matrix, root-cause analysis, steelman, evidence grading, risk/reward, sequencing. Activate for decisions between options, evaluations of ideas or arguments, strategy questions, prioritization, "should we X or…

ralfyishere/rules-with-receipts

Skill Claude Code

Separate facts, assumptions, inferences, and guesses — and never present one as another. Activate whenever producing claims someone might act on - technical explanations, factual summaries, numbers and calculations, API/library behavior, legal or financial context, product comparisons, research findings. Trigger…