Claude Code for IT Operations: Building a Multi-Project

┌─────────────────────────────────────────────────────────────┐
│            Claude Code Automation Framework                  │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌──────────────────────────────────────────────────────┐   │
│  │                   CLAUDE.md                           │   │
│  │  Project context · Stack · Routes · Commands          │   │
│  └──────────────────────┬───────────────────────────────┘   │
│                         │                                    │
│  ┌──────────┐  ┌───────┴────────┐  ┌──────────────────┐   │
│  │  Hooks   │  │  Claude Code   │  │   MCP Servers    │   │
│  │  ───────  │  │   ──────────   │  │   ──────────     │   │
│  │  pre-     │◀─│  Orchestrator  │─▶│  Playwright     │   │
│  │  commit   │  │                │  │  Figma          │   │
│  │  build    │  │                │  │  Custom         │   │
│  └──────────┘  └───────┬────────┘  └──────────────────┘   │
│                         │                                    │
│            ┌────────────┼────────────┐                      │
│            ▼            ▼            ▼                      │
│     ┌──────────┐ ┌──────────┐ ┌──────────┐                │
│     │  Agents  │ │  Skills  │ │  Plugins │                │
│     │  ──────  │ │  ──────  │ │  ──────  │                │
│     │  test    │ │ /deploy  │ │ superpow │                │
│     │  review  │ │ /status  │ │ context7 │                │
│     │  deploy  │ │ /dev     │ │ figma    │                │
│     └──────────┘ └──────────┘ └──────────┘                │
│                                                             │
└─────────────────────────────────────────────────────────────┘

# CLAUDE.md
 
## Project Name
 
One-line description of what this project does.
 
## Project Overview
 
- **Stack**: Next.js 15 + React 19 + TypeScript + Tailwind CSS
- **Type**: Web application / API / CLI tool
- **Deployed**: Platform (e.g., Vercel, Docker, AWS)
- **Purpose**: What problem this solves
 
## Architecture
 
2-3 sentences about how the project is structured. Mention the key
patterns (App Router, REST API, event-driven, etc.) and any unusual
design decisions.
 
## Key Files
 
| File | Purpose |
|------|---------|
| `src/app/layout.tsx` | Root layout |
| `src/lib/constants.ts` | Site-wide constants |
| `next.config.ts` | Build configuration |
 
## Development Commands
 
\`\`\`bash
npm run dev        # Start dev server
npm run build      # Production build
npm test           # Run test suite
npm run lint       # ESLint
\`\`\`
 
## Environment Variables
 
| Variable | Description | Required |
|----------|-------------|----------|
| `DATABASE_URL` | DB connection string | Yes |
| `API_SECRET` | Auth signing key | Yes (prod) |
 
Copy `.env.example` → `.env.local` for local development.
 
## Routes
 
| Route | Purpose |
|-------|---------|
| `/` | Home page |
| `/api/health` | Health check endpoint |
 
## Before Committing
 
1. Run `npm run build` — catch type errors
2. Run `npm test` — verify no regressions
3. Run `npm run lint` — fix style issues
4. No API keys or secrets committed

# Workspace
 
## Structure
 
\`\`\`
workspace/
├── project-web/        # Next.js frontend
├── project-api/        # Express API
├── project-infra/      # Terraform/Docker
└── CLAUDE.md           # This file
\`\`\`
 
## Conventions
 
- **Commits**: Conventional commit style (fix:, feat:, perf:)
- **Branches**: main for all projects
- **Deploy**: `npx vercel --prod` for web, `docker compose up -d` for API
 
## Per-Project CLAUDE.md
 
Each project has its own CLAUDE.md. Always read the project-level
CLAUDE.md before working on that project.

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "command": "if echo '$TOOL_INPUT' | grep -qE 'git push.*(main|master|production)'; then echo 'BLOCKED: Direct push to protected branch. Use a PR instead.' && exit 1; fi; exit 0"
      }
    ]
  }
}

#!/bin/bash
# .claude/hooks/verify-build.sh
FILE_PATH=$(echo "$TOOL_INPUT" | jq -r '.file_path // empty')
 
# Only trigger for source files
case "$FILE_PATH" in
  *.ts|*.tsx|*.js|*.jsx)
    echo "Source file modified. Consider running 'npm run build' to verify."
    ;;
  package.json)
    echo "Dependencies changed. Run 'npm install' then 'npm run build'."
    ;;
esac
exit 0

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "command": ".claude/hooks/suggest-tests.sh"
      }
    ]
  }
}

#!/bin/bash
# .claude/hooks/suggest-tests.sh
FILE_PATH=$(echo "$TOOL_INPUT" | jq -r '.file_path // empty')
 
# Check if a corresponding test file exists
TEST_FILE=$(echo "$FILE_PATH" | sed 's/\/src\//\/src\/__tests__\//' | sed 's/\.tsx\?/.test.ts/')
 
if [ -f "$TEST_FILE" ]; then
  echo "Test file exists: $TEST_FILE — consider running it."
fi
exit 0

---
name: code-reviewer
description: Review code changes for quality, bugs, and best practices
model: sonnet
---
 
You are a code reviewer. Analyze the provided code for:
 
1. **Bugs**: Logic errors, off-by-one, null/undefined risks
2. **Performance**: Unnecessary re-renders, O(n²) loops, missing memoization
3. **Conventions**: Naming, file structure, import ordering
4. **Types**: Missing types, overly broad `any` usage
5. **Tests**: Missing test coverage for critical paths
 
Report findings by severity:
- **CRITICAL**: Will cause bugs in production
- **IMPORTANT**: Should fix before merge
- **SUGGESTION**: Nice to have improvements
 
Be concise. Only report issues you're confident about.

---
name: deploy-verifier
description: Verify a deployment is healthy after pushing to production
model: haiku
---
 
Verify the deployment is healthy:
 
1. Check that the site responds with HTTP 200
2. Verify key pages load without errors
3. Check for console errors using browser automation
4. Confirm API health endpoint returns OK
5. Report any issues found
 
Use curl for basic checks and Playwright (if available) for browser tests.

---
name: deploy
description: Build, test, and deploy to production
user-invocable: true
---
 
Deploy the application to production.
 
Steps:
1. Run `npm run lint` — abort if errors
2. Run `npm test` — abort if failures
3. Run `npm run build` — abort if build fails
4. Run `git status` — check for uncommitted changes
5. If clean, deploy:
   - For Vercel: `npx vercel --prod`
   - For Docker: `docker compose up -d --build`
6. After deploy, verify the production URL responds with HTTP 200
7. Report success or failure with the deployment URL

---
name: status
description: Show project health status
user-invocable: true
---
 
Report the current project health.
 
Check and report:
1. `git status` — uncommitted changes?
2. `git log --oneline -5` — recent commits
3. `npm test` — test suite status
4. `npm run build` — build status
5. `npm audit --production` — vulnerability count
6. Check if production URL is responding
 
Format as a status dashboard:
| Check | Status |
|-------|--------|
| Git | Clean / X uncommitted |
| Tests | X/Y passing |
| Build | Pass/Fail |
| Vulnerabilities | X high, Y moderate |
| Production | Online/Offline |

---
name: dev
description: Start the development server
user-invocable: true
---
 
Start the development environment.
 
1. Check if port 3000 is already in use
2. If `.env.local` is missing, warn (don't create — may contain secrets)
3. Run `npm run dev` in background
4. Wait for the server to be ready
5. Report the local URL

npx @anthropic-ai/claude-code mcp add playwright -- npx @anthropic-ai/mcp-server-playwright

npx @anthropic-ai/claude-code mcp add context7 -- npx -y @anthropic-ai/mcp-server-context7

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": ["@anthropic-ai/mcp-server-playwright"]
    },
    "context7": {
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-server-context7"]
    }
  }
}

# Add the superpowers plugin (planning, TDD, code review workflows)
npx @anthropic-ai/claude-code plugins add superpowers
 
# List installed plugins
npx @anthropic-ai/claude-code plugins list

{
  "name": "my-ops-plugin",
  "version": "1.0.0",
  "description": "IT operations automation for Claude Code",
  "skills": ["skills/deploy.md", "skills/status.md"],
  "agents": ["agents/reviewer.md"]
}