← ClaudeAtlas

pristine-shippinglisted

Use when doing non-trivial software work — implementing features, fixing bugs, rewriting calculation or data pipelines, changing code that reads or writes a database, or deciding whether a change is ready to ship. Also use before "fixing" existing behavior, testing a risky change, or claiming work is done.
swarnimodi/vibecoding-skills · ★ 0 · Code & Development · score 70
Install: claude install-skill swarnimodi/vibecoding-skills
# Pristine Shipping The bar for calling work done is "proven, with evidence someone else can check", not "tests pass". This skill does not make code error-free. It makes the verification thorough and the claims about it honest. Apply these methods on any project without being asked. The user's and the project's own instructions take precedence over this file. ## First: index the project's context Before changing anything, read whatever instruction and memory sources exist. Assume no particular agent, memory service or earlier conversation. Check `CLAUDE.md`, `CLAUDE.local.md` and `AGENTS.md` (root and subfolders), `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, `.cursor/rules`, `.cursorrules`, `.github/copilot-instructions.md`, `GEMINI.md`, `.windsurfrules`, and any memory tool or memory MCP you have (for example Supermemory or mem0): not required, but if present always check and use it. Then learn from the repo itself: README, docs, manifests, CI config, scripts and git log. Note the project's conventions, its test commands, and how it builds and runs. If something is not written down, infer it from the code and say it was inferred. ## Permission gates: never on your own - **Never commit, push, merge, deploy, release, run migrations, change shared infrastructure or configuration, or touch production without the user's explicit go for that specific step.** Approval for one step does not extend to the next. - **Never copy production data or secrets** into test environm