Claude Code Guide

cd your-project
claude

{
  "permissions": {
    "allow": [
      "Read",
      "Grep",
      "Glob"
    ]
  }
}

{
  "permissions": {
    "allow": [
      "Bash(npm *)",
      "Bash(git *)",
      "Read",
      "Edit",
      "Grep",
      "Glob",
      "WebFetch",
      "WebSearch",
      "mcp__*"
    ]
  }
}

{
  "permissions": {
    "allow": [
      "Bash(npm run *)",
      "Bash(git commit *)",
      "Read",
      "Grep",
      "Glob"
    ],
    "deny": [
      "Bash(git push *)",
      "Bash(rm -rf *)"
    ]
  }
}

Review the changes on the current branch compared to main.

Focus on:
1. Logic errors and edge cases
2. Security issues
3. Performance concerns
4. Missing error handling

Reference file names and line numbers.
Show the diff summary first.

Write tests for $ARGUMENTS

Cover:
- Happy path
- Empty / null input
- Error cases
- Edge cases

Use the existing test framework. Run tests after writing them.

Refactor $ARGUMENTS to be cleaner and more maintainable.

Rules:
- Keep the same behavior (no feature changes)
- Improve naming and readability
- Extract repeated logic into functions
- Add type hints if missing
- Run tests after to confirm nothing broke

{
  "hooks": {
    "PostToolUse": [{
      "matcher": "Write|Edit",
      "hooks": [{
        "type": "command",
        "command": "jq -r '.tool_input.file_path' | xargs black 2>/dev/null; exit 0"
      }]
    }]
  }
}

{
  "hooks": {
    "PostToolUse": [{
      "matcher": "Write|Edit",
      "hooks": [{
        "type": "command",
        "command": "jq -r '.tool_input.file_path' | xargs npx prettier --write 2>/dev/null; exit 0"
      }]
    }]
  }
}

{
  "hooks": {
    "PreToolUse": [{
      "matcher": "Bash",
      "hooks": [{
        "type": "command",
        "command": "jq -r '.tool_input.command' | grep -qE 'rm -rf|git push.*--force|git reset --hard' && echo 'Blocked: dangerous command' >&2 && exit 2 || exit 0"
      }]
    }]
  }
}

{
  "hooks": {
    "PreToolUse": [{
      "matcher": "Write|Edit",
      "hooks": [{
        "type": "command",
        "command": "bash -c 'FILE=$(jq -r \".tool_input.file_path\"); for p in \".env\" \"secrets/\" \".git/\"; do [[ \"$FILE\" == *\"$p\"* ]] && echo \"Protected file\" >&2 && exit 2; done; exit 0'"
      }]
    }]
  }
}

{
  "hooks": {
    "Notification": [{
      "matcher": "",
      "hooks": [{
        "type": "command",
        "command": "osascript -e 'display notification \"Claude Code needs input\" with title \"Claude Code\" sound name \"Ping\"'"
      }]
    }]
  }
}

{
  "hooks": {
    "Notification": [{
      "matcher": "",
      "hooks": [{
        "type": "command",
        "command": "powershell -Command \"Add-Type -AssemblyName System.Windows.Forms; [System.Windows.Forms.MessageBox]::Show('Claude Code needs your attention','Claude Code')\""
      }]
    }]
  }
}

# Project: [Name]

## Tech Stack
- [Framework], [Language + version]
- [Database], [Key libraries]

## Commands
- Dev: [command]
- Build: [command]
- Test: [command]
- Lint: [command]

## Architecture
- [Where services live]
- [Where routes/views live]
- [Where models/types live]
- [Where tests live]

## Code Style
- [Rule 1 — be specific]
- [Rule 2]
- [Rule 3]

## Rules
- ALWAYS run tests after changes
- ALWAYS use TypeScript strict mode
- NEVER commit directly to main
- Keep files under 300 lines — split if larger

---
name: explain-code
description: Explains code with diagrams and analogies. Use when the user asks "how does this work?"
---

When explaining code, always include:

1. **Start with an analogy** — compare the code to something from everyday life
2. **Draw a diagram** — use ASCII art to show the flow or structure
3. **Walk through the code** — explain step-by-step what happens
4. **Highlight a gotcha** — what's a common mistake or misconception?

Keep explanations conversational.

# UI generation with design system
/plugin install frontend-design@claude-plugins-official

# GitHub integration
/plugin install github@claude-plugins-official

# Sentry error monitoring
/plugin install sentry@claude-plugins-official

# TypeScript code intelligence
/plugin install typescript-lsp@claude-plugins-official

# Browser automation — Claude can see your UI
claude mcp add --transport stdio playwright -- npx @playwright/mcp@latest

# Fetch web content — read docs, APIs
claude mcp add --transport stdio fetch -- npx @anthropic-ai/mcp-fetch@latest

# SimplerLLM — AI library docs and code examples
claude mcp add --transport sse simplerllm https://learnwithhasan.com/simplerllm/mcp/server/sse/

# Notion — connect to your workspace
claude mcp add --transport http notion https://mcp.notion.com/mcp