From governance
Create a new technical standard directory with three-tier structure (meta.md, scan.md, write.md, rules/) from templates. Use when establishing new coding standards, documenting technical requirements, or creating compliance guidelines.
How this skill is triggered — by the user, by Claude, or both
Slash command
/governance:create-standardopusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new technical standard directory in the [plugin]/constitution/standards directory following the three-tier structure (meta.md, scan.md, write.md, and rules/). $ARGUMENTS
Create a new technical standard directory in the [plugin]/constitution/standards directory following the three-tier structure (meta.md, scan.md, write.md, and rules/). $ARGUMENTS
What this command does NOT do:
When to REJECT:
ultrathink: you'd perform the following steps
Analyze Requirements
Identify Applicable Skills & Standards
create-standard skill for creation processRisk Assessment
Skill Compliance
create-standard skillPrimary Implementation
mkdir -p <name>/rules/<name>/meta.md from template:standard-meta with metadata, principles, and overview<name>/scan.md from template:standard-scan with scanning/review rules<name>/write.md from template:standard-write with writing/implementation guidanceStandards Enforcement
Edge Case Handling
Template-Based Verification
Automated Testing
Quality Assurance
Side Effect Validation
Output Format:
[✅/❌] Command: $ARGUMENTS
## Summary
- Standard created: [name]/
- Files: meta.md, scan.md, write.md, rules/
- Location: [plugin]/constitution/standards/[name]/
- Category: [category]
## Actions Taken
1. Created standard directory and rules/ subdirectory
2. Generated meta.md from template:standard-meta
3. Generated scan.md from template:standard-scan
4. Generated write.md from template:standard-write
5. Populated all files with relevant guidelines
## Content Structure
- Core Principles: [count]
- Main Topics: [list]
- Code Examples: [count]
- Anti-patterns: [count]
## Related Standards
- [Related standard 1]
- [Related standard 2]
## Next Steps
- Review generated standard files for completeness
- Add specific code examples if needed
- Add individual rule files to rules/ subdirectory
- Link from related documentation
/create-standard "error-handling"
# Generates: error-handling/meta.md, error-handling/scan.md, error-handling/write.md, error-handling/rules/
# Category: Automatically determined as 'code'
/create-standard "component-testing" --detail="React component testing patterns"
# Generates: component-testing/meta.md, component-testing/scan.md, component-testing/write.md, component-testing/rules/
# Includes: React-specific testing examples
/create-standard "api-authentication" --category=security
# Generates: api-authentication/meta.md, api-authentication/scan.md, api-authentication/write.md, api-authentication/rules/
# Category: Explicitly set to 'security'
/create-standard "database-migrations" --detail="PostgreSQL migration patterns" --category=backend
# Generates: database-migrations/meta.md, database-migrations/scan.md, database-migrations/write.md, database-migrations/rules/
# Includes: PostgreSQL-specific examples
/create-standard "code-coverage" --category=quality
# Generates: code-coverage/meta.md, code-coverage/scan.md, code-coverage/write.md, code-coverage/rules/
# Includes: Coverage metrics and thresholds
/create-standard ""
# Error: Empty standard name
# Prompt: "What is the name of the standard you want to create?"
# Action: Wait for user input before proceeding
/create-standard "naming"
# Warning: naming/ directory already exists
# Prompt: "Standard 'naming' already exists. Create with different name?"
# Alternative: Use /update-standard to modify existing
npx claudepluginhub alvis/.claude --plugin governanceUpdates or creates .maister project standards from conversation context, descriptions, or by syncing/merging from other projects' standards directories.
Updates or creates project standards in .maister/docs/standards/ from conversation context, explicit descriptions, or by syncing from another project. Auto-detects categories like frontend, backend, testing.
Generates steering documents with project standards, git workflows, and tech guidelines in .kiro/steering/ for frontend, backend, fullstack, or library projects.