blueprint-development

# Blueprint Development Rule Generator

This skill teaches Claude how to generate project-specific behavioral rules and commands from Product Requirements Documents (PRDs) as part of the Blueprint Development methodology.

## When to Use This Skill

Activate this skill when:
- User runs `/blueprint:generate-rules` command
- User runs `/blueprint:generate-commands` command
- User asks to "generate rules from PRDs"
- User asks to "create project-specific rules"
- User initializes Blueprint Development in a project

## Rule Generation Process

### Step 1: Analyze PRDs

Read all PRD files in `docs/prds/` and extract:

**Architecture Patterns**:
- Project structure and organization
- Dependency injection patterns
- Error handling approaches
- Module boundaries and layering
- Code organization conventions

**Testing Strategies**:
- TDD workflow (RED → GREEN → REFACTOR)
- Test types (unit, integration, e2e)
- Mocking patterns
- Coverage requirements
- Test structure and organization

**Implementation Guides**:
- How to implement specific feature types (API endpoints, UI components, etc.)
- Step-by-step patterns for common tasks
- Integration with external services
- Data flow patterns

**Quality Standards**:
- Code review checklist items
- Performance baselines and targets
- Security requirements (OWASP, validation, etc.)
- Style and formatting standards

### Step 2: Generate Four Domain Rules

Create project-specific behavioral rules in `.claude/rules/` alongside manual rules.

**Two-Layer Architecture**:
1. **Plugin layer**: Generic skills from blueprint-plugin (auto-updated)
2. **Rules layer**: Behavioral rules from PRDs in `.claude/rules/` (project-specific, can be manually edited)

Generated rules are behavioral guidelines that Claude follows during development:

#### 1. Architecture Patterns Rule

**Location**: `.claude/rules/architecture-patterns.md`

**Structure**:
```markdown
# Architecture Patterns

> Architecture patterns and code organization for [project name]