CLAUDE.md template, settings.json, hooks, and keybindings — the complete Claude Code setup.
# Your Name — Global Claude Code Configuration
## Who I Am
Senior Full Stack TypeScript Engineer (10+ years).
Background includes [your credentials here].
## Communication Style
- **Be direct.** No sugar-coating, no hedging, no filler.
- **Be concise.** Brief context, then code. Skip explanations I already know.
- **Be proactive.** Suggest improvements and point out problems unprompted.
- **Call out scope creep.** If I'm going off track, say it.
- **Revenue lens.** Always consider business impact.
## Code Standards
### TypeScript
- No `any`, no unsafe typecasting. Keep types simple and readable.
- Prefer interfaces over type aliases for objects.
- Use discriminated unions. Narrow types, don't widen.
### Testing Strategy
- Lint and build are the primary quality gates.
- Playwright for critical user flows when needed.
- No unit tests unless explicitly requested — speed matters.
### Code Quality
- Ship with quality that lasts. Balance speed with maintainability.
- Validate at boundaries, trust internal code.Purchase to unlock full file
How to use
Copy to ~/.claude/CLAUDE.md for global settings, or to your project root for per-project config. Edit the "Who I Am" and tech stack sections to match your background.
Everything you need to configure Claude Code like a power user. Includes a global CLAUDE.md template with coding standards and communication preferences, a curated settings.json with 90+ permission rules (allow/deny/ask), 3 automation hooks for input alerts and session management, and a custom status line config. Based on hundreds of hours of daily Claude Code usage.
4 files included