Professional configuration guide for Claude Code.

Complete .claude folder with production-ready skills, hooks, and commands.

+400 developers use this setup every day 😁

/home/.claude
1## Git Workflow
2- Do not include "Claude Code" in commit messages
3- Use conventional commits (be brief and descriptive)
4
5## Important Concepts
6Focus on these principles in all code:
7- e2e type-safety
8- error monitoring/observability
9- ████████████████████████████████████████████████
10
11All detailed coding guidelines are in the skills:
12- Use `software-engineering` skill for core principles
13- Use `typescript` skill for TypeScript/JavaScript
14- Use `react` skill for React/Next.js
15- ████████████████████████████████████████████████

Without

  • Repeat instructions every conversation
  • Figure out best practices yourself
  • Different configs per project
  • Manual branch → code → test → PR
  • No task completion alerts

With

  • Write once, use everywhere
  • Production-tested practices included
  • Same standards across projects
  • One command does all four
  • Get notified when done

What's in the folder?

Complete configurations, automations and explicit guidelines for software engineering, testing, writing standards, naming conventions, TypeScript and React.

CLAUDE.md

Define your rules once. All projects follow.

  • Git Workflow
  • Software Engineering Concepts
  • TypeScript / JavaScript
  • React / Next.js
  • Testing
  • Writing Standards

Complete Guide (PDF)

Learn to use Claude Code like a pro.

  • How to configure (globally and per project)
  • How to save tokens
  • Connecting the dots
  • Git Worktree + Tmux Integration

Hooks

Automate actions before and after each Claude response.

  • Completion sound notifications
  • Automatic code validation
  • Custom scripts

Skills

Professional development standards, activated in one command.

  • software-engineering: e2e type-safety, observability
  • typescript: strict types, never any
  • react: React 19, Server Components, hooks
  • reviewing-code: systematic review workflow
  • writing: clear, concise documentation

Commands

Automated workflows in one /command.

  • /investigate → detailed discovery
  • /investigate-batch → token-efficient discovery
  • /create-feature → worktree + implementation
  • /review-staged → analyze against guidelines
  • /open-pr → PR with mermaid diagrams

Ready Templates

Structures you can adapt to your projects.

  • settings.json (configuration model)
  • PR description template
  • Commit messages template

MCP Integrations

Expand Claude Code capabilities:

  • Playwright: browser automation, perfect for E2E tests
  • DevTools: DevTools Console/Network access
  • Context7: documentation repository (increases token usage, but improves convenience)

Pick a plan

Pay once. Use forever.

CLAUDE.md

Rules and standards in a single file.

$12

One-time payment

  • Software engineering best practices
  • Behavior-focused testing
  • Consistent and clear suggestions
  • Lifetime updates
  • 20% off future purchases

🟡 Loads ~91 lines per conversation

Best value

Complete .claude folder

Automate your workflows with ready-to-use commands and hooks.

$27

One-time payment

  • Optimized CLAUDE.md (80% smaller)
  • 3 skills on-demand
  • Software Engineering
  • Reviewing Code
  • Writing (Zinsser)
  • 6 commands to avoid fatigue

💡 Skills are loaded only when mentioned

7-Day Refund Guarantee

Try it. If it doesn't save time, get your money back.

Simple refund process
Fast support

No value, no charge.

FAQ

Quick answers

After downloading the folder, read the "guide.pdf" (or guide.md) file for detailed instructions on how to set up your Claude Code.

Questions? caiohoborghi@gmail.com