ralfyishere/rules-with-receipts
Skill Claude CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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…
ralfyishere/rules-with-receipts
Skill Claude CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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…
ralfyishere/rules-with-receipts
Instructions file CodexOpenCode
Instructions for ralfyishere/rules-with-receipts, covering agents.md — for ai agents that land in this repo, what this is, if you are installing the pack into a project, if you are working in a project that already has the pack and if you are evaluating claims about this pack.
ralfyishere/rules-with-receipts
Instructions file
Instructions for ralfyishere/rules-with-receipts: This directory IS the quality pack's source. Sessions here are usually maintaining the pack. Maintainer rules.