Reddit power-user workflow
Claude Code Power User Playbook (from Reddit post)
If you're looking to up-level your Claude Code workflow, this distills a top-rated Reddit post where a power user shares their skills, hooks, subagents, and full setup – plus a GitHub repo with working examples.
Reddit post
Claude Code is a Beast – Tips from 6 Months of Hardcore Use
r/ClaudeAI • by JokeGold5455
Long-form writeup covering skills, hooks, subagents, and real-world workflows used daily in a production codebase.
📁Linked repo:github.com/diet103/claude-code-infrastructure-showcase
💡 What is it?
This is a power-user playbook for Claude Code, distilled from a highly-upvoted Reddit post by someone who's used Claude Code intensively for 6 months in production. It covers advanced patterns like skills (reusable instruction files), hooks (automated triggers), and subagents (specialized Claude instances for different tasks). If you want to go beyond basic prompting and build a structured, scalable workflow with Claude Code, this is your starting point.
Key insights
- Plan everything — use planning mode and/or a specialized strategy-plan-architect subagent to help you plan and document tasks.
- Skills + hooks — use hooks to make sure your agent activates skills. This will ensure that the skills actually get called by your agent.
- Dev docs system — create a system to document codebase and tasks, and update as the agent performs its tasks.
- Code reviews — always have Claude review its work
- Pm2 for backend — use this tool to accelerate debugging
What the linked repo contains:
Skills, modular skill pattern, specialized agents, dev docs system, comprehensive examples
About planning (strategic-plan architect subagent)
The strategic-plan architect runs before deep coding. It gathers context, analyzes project structure, and designs the plan.
- Gathers context and analyzes project structure.
- Creates a comprehensive plan with exec summary, phases, tasks, risks, success metrics, and timelines.
- Use /dev-docs custom command to generate the three files: plan, context, and tasks-checklist.
- Uses a clarifying-questions loop until Claude is confident in the architecture and implementation.
About skills
Skills are activated by the agent, but often it won't call them on its own. Add a hook that forces Claude to think through which skills are relevant and explicitly trigger them.
Example skills
| Skill name | Purpose |
|---|---|
| backend-dev-guidelines | Routes → Controllers → Services → Repositories |
| frontend-dev-guidelines | React 19, MUI v7, TanStack Query/Router patterns |
| workflow-developer | Complex workflow engine patterns |
| notification-developer | Email / notification system |
| database-verification | Prevent column name errors (guardrail that can block edits) |
claude.md vs Skills
| What stays in claude.md | What becomes skills |
|---|---|
| Global conventions and coding style | Deep, stack-specific guidelines |
| High-level repo structure and naming rules | Multi-step workflows (e.g. "ship a feature") |
| Top-level workflow expectations | Large playbooks that deserve their own files |
Other useful tips
| Tip | Details |
|---|---|
| pm2 logs | Use pm2 to run and debug backend services so Claude can read individual service logs more easily. |
| Utility scripts | Attach small utility scripts to skills, such as a Node command to test an authenticated route. Claude can run it, inspect the output, then iterate. |
| Working repo | The linked repo includes working examples of these skills, hooks, and subagents – clone it and gradually swap in your own conventions. |
Example hooks
| Hook | What it does | Notes |
|---|---|---|
| file-edit tracker | Logs which files were edited, which repo they belong to, and timestamps. | Great for reconstructing the story of a session or writing a summary later. |
| build checker | Reads and edits logs, runs build scripts, checks TypeScript errors. | Either fixes issues directly in Claude or delegates to a subagent, and logs everything. |
| prettier formatter | Automatically formats code using Prettier. | Deprecated – used too much context for the value it provided. |
Example subagents
Quality control
Testing + debugging
Planning + strategy
Specialized