pattern-generate

Synchronize coding rule files with a master PATTERNS.md reference document.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill pattern-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-generate
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/pattern-generate
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill pattern-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually keeping coding pattern rule files in sync with a central master pattern reference document is time-consuming and prone to human error, especially for teams maintaining large sets of prescriptive coding standards across multiple project areas.

Core Features & Use Cases

  • Automated Rule Generation: Creates new pattern rule files directly from sections of the master PATTERNS.md reference document, following a standardized template.
  • Gap Detection & Sync: Diffs existing rule files against the master reference to identify new patterns, outdated entries, and orphaned rules, with support for targeted section sync and dry-run previews.
  • Compliance Validation: Automatically validates generated rule files against team prescriptive content standards and token limits before applying changes.
  • Use Case: A .NET engineering team can use this skill to quickly propagate new security or architecture patterns from a central PATTERNS.md document to individual rule files, ensuring all team members follow the latest coding standards without manual copy-paste work.

Quick Start

Invoke the pattern-generate skill with the --sync flag to automatically sync all patterns from the master reference document to your project's rule files.

Frequently Asked Questions about pattern-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically sync coding standards from a master pattern document to individual rule files?

Automated pattern synchronization propagates updates from a central master reference document to enforceable coding rule files, eliminating manual copy-paste errors. It diffs existing rules against the source to identify new patterns, outdated entries, and orphaned rules for targeted syncing.

What is the best way to generate enforceable code standards from a centralized reference?

Generating enforceable code standards directly from a master pattern reference document creates standardized rule files automatically. This mechanism validates generated content against team prescriptive content standards and token limits before applying changes to ensure full compliance.

Can I detect gaps between my source of truth and existing coding rule files?

Gap detection compares your existing rule files against the master reference document to identify missing patterns, outdated entries, and orphaned rules. It supports targeted section syncing and dry-run previews so you can review changes before applying them.

Does automated rule generation work for .NET codebases and general software engineering projects?

Automated rule generation applies to software engineering workflows maintaining centralized pattern libraries for .NET and general codebases. It requires no external dependencies, using your existing master pattern reference document as the single source of truth for propagation.

Why do manually updated coding rule files become inconsistent across development teams?

Manually updating coding rule files is time-consuming and prone to human error, especially for teams maintaining large sets of prescriptive coding standards across multiple project areas. Automated synchronization eliminates this by propagating updates without manual intervention.

How do I validate generated rule files against team prescriptive content standards?

Compliance validation automatically checks generated rule files against team prescriptive content standards and token limits before applying changes. This ensures all propagated patterns meet your project's specific coding requirements and remain consistent across the development team.