Pattern Abstract Grammar

Directory Structure & Memory Files
18 lines
# Project: MyApp

THIS INSTRUCTION DEFINES workspace conventions for MyApp development.

## Architecture
- Frontend: React + TypeScript in /src/components
- Backend: Node.js + Express in /src/api
- Tests: Jest in /tests, run with `npm test`

ALWAYS:
- Run tests before committing changes
- Use TypeScript strict mode
- Follow existing naming conventions

NEVER:
- Modify /src/config/production.json directly
- Commit .env files
- Skip type definitions

Permissions & Security
15 lines
{
    "permissions": {
        "allow": [
            "Read(**)",
            "Glob(**)",
            "Grep(**)",
            "Bash(npm run:*)",
            "Bash(npm test:*)",
            "Bash(git status:*)",
            "Bash(git diff:*)",
            "Bash(git log:*)"
        ],
        "deny": ["Read(.env*)", "Read(**/secrets/**)", "Bash(rm -rf:*)"]
    }
}

Custom Commands, Agents & Hooks
27 lines
# Example: Code reviewer agent (.claude/agents/code-reviewer.md)
---
name: code-reviewer
description: Reviews code changes for quality, security, and consistency
tools: Read, Glob, Grep
---

THIS AGENT PERFORMS systematic code review.

# PHASE 1: Discovery
READ recent changes via git diff
IDENTIFY modified files and their purposes

VALIDATION GATE:
✅ All changed files identified
✅ Change scope understood

# PHASE 2: Analysis
FOR EACH modified file:
CHECK code style consistency
CHECK error handling completeness
CHECK security implications

ALWAYS:
- Cite specific line numbers
- Explain why something is problematic
- Suggest concrete fixes

The Iteration Cycle & Communication
Original: "Implement user authentication with login, registration,
          password reset, and session management"

Decomposed:
1. Create user data model and database schema
2. Implement registration endpoint with validation
3. Implement login endpoint with password verification
4. Add session token generation and validation
5. Implement password reset flow
6. Add authentication middleware to protected routes

Quality Gates & Session Management
VALIDATION GATE: Feature Complete
  ✅ All acceptance criteria met
  ✅ Unit tests written and passing
  ✅ Integration tests passing
  ✅ No linting errors
  ✅ Documentation updated
  ✅ Code reviewed
  IF FAIL: REPORT specific failing criteria

Multi-Agent Workflows & State Persistence
16 lines
# Session State: Feature X Implementation

## Completed
- [x] Database schema created
- [x] API endpoints implemented
- [x] Unit tests for endpoints

## In Progress
- [ ] Frontend components (50% complete)

## Blockers
- Need design decision on error message format

## Context for Next Session
- Using React Query for data fetching (see /src/hooks/useFeatureX.ts)
- Authentication middleware already handles token validation