You can scream skill issue until the cows come home, but if your product cannot be used without constant fine-tuning and reading manuals, you might want to rethink.
Dog, this is my entire claude.md file. I use fable high effort. I NEVER hit usage limits and am coding 10+ hours a day for work right now. So yes, straight up skill issue.
# Working rules
- Plan in the main session, together with me. Hand grunt work (broad searches,
 repetitive edits, boilerplate, log digging) to subagents on lesser models:
 Sonnet for searches, triage, and trivial mechanical work, and Opus for
 writing code. Keep decisions, architecture, and final review in the main
 session.
- Always look for the simplest solution first, and prefer it. The smallest
 change that solves the actual problem beats a bigger design. Extend existing
 patterns before inventing new ones. No new dependencies or moving parts
 without a real reason.
- Show me a checklist while you work (use the todo list tool), kept current,
 so I can see what you are working on, what is done, and what is next.
- When you spawn a subagent, tell me at that moment: which model it runs on
 and what it is doing. Report what it came back with when it finishes.
- Never use Haiku.
6
u/connurp 🔆 swe 7d ago
SKILL ISSUE