A couple of suggestions for Claude Code productivity, from someone in the profitable SaaS trenches:

For ANY non-trivial feature: shift-tab into planning mode, and mention “do deep research on best practices and known issues, using web search” to the prompt. READ the plan, adjust, and have it execute. Plans survive compaction MUCH better than vibe-prompted features, particularly if they’re bigger.

/plugin marketplace add mksglu/claude-context-mode (significantly bigger context window, uses an MCP to load files into context via reference instead of parking the whole file there)

/plugin install claude-warden@claude-warden (much better protection against destructive actions)

Create a /documents/ folder with these files:

• platform-docs.md (describes EVERY feature of your product in detail, generated by a skill that goes through each file/screen and sums up functionality)
• ICPs.md (a document that defines each of your ideal customers, what they need, what theywant to and can do. A dossier for each kind, like what a private detective would produce) -styleguide.md (contains a description of the visual feel of your application. certain colors, hierarchies. you can have CC generat that from an existing codebase using the —chrome flag to “see it”)
• also great: roadmap.md/vision.md (gives exploratory runs some guidance), data-reference.md (explains the kind of connection between your domaindata that is not expressed in the models and their relationships)

Maintain a CLAUDE.md that references all these /documents/*.md files in the system prompt (and forces code to be compliant).

Any of these docs can be inferred from an existing codebase. Ask CC to use the AskUserQuestion skill to get your feedback on anything unclear. Ask it to persist plans and complex ideas in markdown form in your /documents folder.

That will make the experience MUCH more enjoyable and manageable than a vanilla CC.