Skip to content
TrustedSkillsbeta
Back to all skills

Blueprint Generate Rules

Checked
laurigates·vlatest·ai-ml·MIT

Automatically creates rule sets from provided blueprints, streamlining automation workflows and reducing manual configuration.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add laurigates/claude-plugins --skill blueprint-generate-rules -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

laurigates

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned laurigates/claude-plugins at 45d1d7dcf6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
45d1d7dcf6
Manifest
blueprint-plugin/skills/blueprint-generate-rules/SKILL.md
Scanned
1 file, 242 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

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.