Blueprint Generate Rules

What it does

This skill automatically generates rule sets from Product Requirements Documents (PRDs). It analyzes PRD files to extract architecture patterns, testing strategies, implementation guides, and quality standards, then aggregates these into four domain-specific rules: architecture-patterns.md, testing-strategies.md, implementation-guides.md, and a fourth unspecified rule. The generated rules are saved in the .claude/rules/ directory and can be loaded conditionally based on file paths specified in their frontmatter.

When to use it

• You need to generate rules from existing PRDs.
• You want path-scoped rules for specific file types within your project.
• You are automating rule creation directly from requirements outlined in PRDs.

Key capabilities

• PRD Analysis: Reads and analyzes .md files located in the docs/prds/ directory to extract key information.
• Architecture Pattern Extraction: Identifies project structure, architectural styles (MVC, layered, etc.), design patterns, dependency injection approaches, error handling strategies, code organization conventions, integration patterns.
• Testing Strategy Extraction: Extracts TDD workflow requirements, test types (unit, integration, e2e), mocking patterns, coverage requirements, and test commands.
• Implementation Guide Generation: Creates step-by-step guides for API/endpoint implementation, UI components, database operations, external service integrations, and background jobs.
• Quality Standard Definition: Defines code review checklists, performance baselines, security requirements (OWASP), code style guidelines, documentation requirements, and dependency management practices.
• Rule Generation & Storage: Generates four aggregated domain rules (architecture-patterns.md, testing-strategies.md, implementation-guides.md) and saves them in the .claude/rules/ directory.
• Path Frontmatter Support: Allows specifying file paths within rules to enable conditional loading based on project structure.

Example prompts

• "Generate rules from my PRDs."
• "Create architecture patterns rule for this project."
• "Update the testing strategies rule with new coverage requirements."

Tips & gotchas

• Prerequisites: The docs/prds/ directory must exist and contain at least one PRD file.
• Existing Rules: If rules already exist, you will be prompted to overwrite, skip, or backup the existing files before generating new ones.
• File Paths: Use paths frontmatter within generated rule files (e.g., testing-strategies.md) to control when those rules are applied based on file locations.