Opus 5.5 Claude Code Workflow Best Practices
From Wikiprompt, the free prompt encyclopedia
Opus 5.5 Claude Code Workflow Best Practices A practical workflow for maximizing Opus 5.5 in Claude Code, covering context management, subagent usage, and project mapping.
Prompt ContentSave
π
- set effort to medium at all times, more effort never gave me better outputs
- keep your context window under 400k tokens
- only use a global claude.md, let the code and your knowledge base do the rest
- use git worktrees and keep one main chat as the router
- prompt the router to spawn each project's thread in its own worktree, versioning gets easy
- use subagents a lot, they keep your main context window clean
- you share the vision and the end goal, the workers do the research and coding
- skip plan mode, use /grill-me or the Compound engineering plugins instead
- kick off new projects with heavy research and a pile of inspirations
- then trust Opus overnight, with the right references it can build literally anything
- disable 90% of your skills, you probably don't need them anymore
- have Opus build an artifact that maps the full scope of each project
- it updates the map at every milestone, so you always see what's done and what's left
Sign in to see the full prompt
Continue with:
By logging in, you agree to our Terms of Use and Privacy Policy
Usage
This prompt is designed for use with productivity. Copy the prompt content above and paste it into your preferred AI tool.
For best results, you may customize the placeholders (indicated by square brackets or capital letters) with your specific requirements.
References
- Category: productivity Prompts
- Source: https://x.com/EXM7777/status/2107108825761558799
Talk
0 comments