rule

Generate structured English coding rules from natural-language descriptions.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/agentteamland/rule --skill rule-agentteamland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule
Source: https://github.com/agentteamland/rule/tree/main/skills/rule
Command: npx skills add https://github.com/agentteamland/rule --skill rule-agentteamland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert natural-language coding and architecture ideas into enforceable, consistently formatted rules that live in the correct repository location, reducing manual drafting and duplication.

Core Features & Use Cases

  • Generate a clear, English-structured rule from a natural-language description.
  • Auto-select the target file based on scope: project (.claude/), global (~/.claude/rules/), or team (~/.claude/repos/agentteamland/{team}/).
  • Check existing rules to prevent duplicates and to detect conflicts before writing.
  • Support multi-rule flows with a guided wizard for complex rules.

Quick Start

Describe a rule in natural language and the skill will write a structured rule to the appropriate file in English.

Frequently Asked Questions about rule

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

FAQPage Schema
How do I convert natural-language coding standards into structured architecture rules?

The skill automates rule generation by parsing natural-language descriptions into a structured English format, checking existing rules for duplicates, and writing the output to the correct file path based on your chosen scope.

Can I set coding rules at global, project, or team scope?

The skill supports three scopes: project (default), global (--global), and team (--team), automatically routing each structured rule to its corresponding directory path.

How do I prevent duplicate architecture rules when generating new ones?

To prevent duplicate architecture rules, the skill reads existing rules in the target file before writing, detecting overlaps and conflicts to ensure only unique, enforceable standards are added to your repository.

What is the best way to automate the creation of enforceable development standards?

Automating standard creation through a structured rule generator ensures consistent formatting and correct file placement, eliminating the manual effort of drafting and maintaining architecture guidelines.

Does the rule generation wizard support complex multi-rule flows?

Yes, the rule generation wizard supports complex multi-rule flows by providing a guided process that helps you structure and write multiple related coding standards into the correct repository locations.

When should I not use an automated rule generator for coding standards?

You should not use an automated rule generator when your coding standards require highly customized formatting outside the structured English template, or when your repository lacks the supported directory structure for scope-based routing.