Create Standard

Create a new technical standard document in the [plugin]/constitution/standards directory following the template structure. $ARGUMENTS

🎯 Purpose & Scope

What this command does NOT do:

• Modify existing standards (use update-standard)
• Create workflows (use create-workflow)
• Override existing files without confirmation
• Create non-standard documentation

When to REJECT:

• Empty or unclear standard name
• Standard already exists
• Invalid name format
• Updating existing standards
• Creating non-standard files

🔄 Workflow

ultrathink: you'd perform the following steps

Step 1: Planning

1. Analyze Requirements

   • Parse $ARGUMENTS to extract standard name and details
   • Determine appropriate category (code, frontend, backend, security, quality, project)
   • Identify related existing standards
   • Plan standard structure and content

2. Identify Applicable Workflows & Standards

   • Check /create-standard.md for creation process
   • Review existing standards in target category for patterns
   • Note related standards to reference

3. Risk Assessment

   • Check for name conflicts with existing standards
   • Verify category directory exists
   • Ensure no duplicate standards

Step 2: Execution

1. Workflow Compliance

   • Follow /create-standard.md
   • Load template from template:standard
   • Apply standard naming conventions

2. Primary Implementation

   • Generate standard title from arguments
   • Determine category placement
   • Populate template sections with relevant content
   • Include practical code examples
   • Add decision matrices and quick references

3. Standards Enforcement

   • Use lowercase, hyphen-separated naming
   • Follow template structure exactly
   • Include both good and bad examples
   • Add related standards references

4. Edge Case Handling

   • Check if file already exists before writing
   • Create category directory if needed
   • Handle complex multi-word names properly
   • Preserve any existing backups

Step 3: Verification

1. Workflow-Based Verification

   • Verify follows template structure
   • Check all required sections present
   • Validate code examples are TypeScript

2. Automated Testing

   • Verify markdown syntax is valid
   • Check file saved to correct location
   • Ensure proper formatting

3. Quality Assurance

   • Confirm examples include ✅ and ❌ patterns
   • Validate related standards links
   • Check decision trees are complete

4. Side Effect Validation

   • File saved to
   • No existing files overwritten
   • Category directory created if needed

Step 4: Reporting

Output Format:

[✅/❌] Command: $ARGUMENTS

## Summary
- Standard created: [name].md
- Location: [name].md
- Category: [category]

## Actions Taken
1. Generated standard from template
2. Populated with relevant guidelines
3. Created file at specified location

## 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 for completeness
- Add specific code examples if needed
- Link from related documentation

📝 Examples

Basic Standard Creation

/create-standard "error-handling"
# Generates: error-handling.md
# Category: Automatically determined as 'code'

Frontend Standard with Detail

/create-standard "component-testing" --detail="React component testing patterns"
# Generates: component-testing.md
# Includes: React-specific testing examples

Security Standard

/create-standard "api-authentication" --category=security
# Generates: api-authentication.md
# Category: Explicitly set to 'security'

Backend Standard with Context

/create-standard "database-migrations" --detail="PostgreSQL migration patterns" --category=backend
# Generates: database-migrations.md
# Includes: PostgreSQL-specific examples

Quality Standard

/create-standard "code-coverage" --category=quality
# Generates: code-coverage.md
# Includes: Coverage metrics and thresholds

Error Case Handling

/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

With Existing File

/create-standard "naming"
# Warning: naming.md already exists
# Prompt: "Standard 'naming' already exists. Create with different name?"
# Alternative: Use /update-standard to modify existing