create-standard

Create a new three-tier technical standard with meta, scan, write, and rule guides.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill create-standard-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-standard
Source: https://github.com/alvis/.agents/tree/main/plugins/governance/skills/create-standard
Command: npx skills add https://github.com/alvis/.agents --skill create-standard-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Establishing a new reusable coding or compliance policy requires consistent structure across rationale, violation detection, and compliant-pattern documentation; this Skill scaffolds that entire three-tier standard with stable rule IDs and cross-tier consistency checks. ## Core Features & Use Cases - Three-Tier Standard Generation: Creates meta.md (rationale, exceptions, rule groups), scan.md (violation detection with quick scan and rule matrix), and write.md (compliant patterns and decision trees) from canonical templates. - Stable Rule ID Management: Enforces a unique uppercase prefix, rejects duplicate prefixes or rule IDs across all plugin standards, and generates per-rule detail guides under rules/. - Registry and Verification: Registers the standard in the plugin's standards INDEX.md and runs cross-tier consistency, link resolution, dependency-cycle, and plugin validation checks. - Use Case: A team wants to enforce a new logging policy across a plugin. Invoke this Skill with the plugin and standard name to produce the full standard directory, rule guides, and INDEX registration, ready for review. ## Quick Start Ask the agent to create a new standard named error-handling in the coding plugin with detail about structured logging requirements.

Frequently Asked Questions about create-standard

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

FAQPage Schema
How do I create a new coding standard for a plugin?

Invoke the create-standard skill with the target plugin and a lowercase kebab-case standard name, optionally passing --detail for domain specifics. It generates meta.md, scan.md, write.md, and rule guides from templates, then registers the standard in the plugin's standards INDEX.md.

What is the three-tier structure of a standard?

Each standard has meta.md for rationale, dependencies, exceptions, and rule groups; scan.md for violation detection with a quick scan and rule matrix; and write.md for compliant patterns and decision trees. Detailed rules get individual guides under rules/.

When should I use update-standard instead of create-standard?

Use update-standard for any revision to an existing standard. create-standard only establishes a new standard directory and rejects duplicate targets, duplicate rule-ID prefixes, or policy that belongs to an existing owner.

How are rule IDs and prefixes validated?

The skill searches every standard under plugins/*/standards/ for the proposed prefix and rule IDs before drafting. Verification builds ID sets from meta groups, scan items, write summaries, and rule filenames, failing on undeclared, missing, duplicated, or cross-prefix IDs.

What validation runs after creating a standard?

Verification includes cross-tier ID consistency, INDEX row presence, clean and violating candidate walkthroughs, Markdown link resolution, dependency-cycle checks, claude plugin validate --strict, and the write-skill quick_validate.ts script.