团队用 Claude Code 六周写了 2752 条提示词，把重复纠错整理成 14 个 Skill

Our team went back through every session. A lot of those prompts were the same correction typed again. "Don't mock it." "Did you actually run it?" "I didn't ask you to change that."

So we turned the ones we repeated most into skills.

The ones that cost us the most before we wrote them down:

• Mock data where an API didn't exist yet. Looked finished, passed review, didn't work.
• "It's centred now", twice, from reading the CSS. One screenshot said otherwise.
• A cleanup step that ran after a failed migration and took live billing rows with it.
• About 50 real emails to fake addresses from a local test run. All bounced.
• Asked for one nav link, got a redesigned nav.

There are 14 now. 7 that Claude applies on its own (build it for real or say it's missing, prove it on the running app, check current docs, stay in scope, ask before anything that sends or spends, no comments, no AI-sounding copy), 2 for APIs and auth, and 5 commands like /prod-runbook, which wraps everything in set -euo pipefail and puts the destructive step last.

About 900 tokens total until one fires.

/plugin marketplace add duvi-ai/skills /plugin install duvi-skills@duvi 

Or npx skills add duvi-ai/skills for Codex, Cursor and the rest.

https://github.com/duvi-ai/skills

The prompt we typed most, which became scope-discipline:

discuss first, don't change anything. propose the full plan, don't give me a menu 

Which of these would you throw out? And what do you keep typing to yours?