Standards Skill

Language-specific coding standards loaded on-demand by other skills.

Purpose

This is a library skill - it doesn't run standalone but provides standards references that other skills load based on file types being processed.

Standards Available

How It Works

Skills declare standards as a dependency:

skills:
  - standards

Then load the appropriate reference based on file type:

# Pseudo-code for standard loading
if file.endswith('.py'):
    load('standards/references/python.md')
elif file.endswith('.go'):
    load('standards/references/go.md')
elif file.endswith('.rs'):
    load('standards/references/rust.md')
# etc.

Domain-Specific Checklists

Specialized checklists for high-risk code patterns. Loaded automatically by /vibe and /pre-mortem when matching code patterns are detected:

Skills detect triggers via file content patterns and import statements. Each checklist's "When to Apply" section defines exact detection rules.

Deep Standards

For comprehensive audits, skills can load extended standards from vibe/references/*-standards.md which contain full compliance catalogs.

Integration

Skills that use standards:

• /vibe - Loads based on changed file types
• /implement - Loads for files being modified
• /review - Loads for change-quality and blast-radius checks
• /doc - Loads markdown standards
• /bug-hunt - Loads for root cause analysis
• /complexity - Loads for refactoring recommendations

Examples

Vibe Loads Python Standards

User says: /vibe (detects changed Python files)

What happens:

1. Vibe skill checks git diff for file types
2. Vibe finds auth.py in changeset
3. Vibe loads standards/references/python.md automatically
4. Vibe validates against Python standards (type hints, docstrings, error handling)
5. Vibe reports findings with standard references

Result: Python code validated against language-specific standards without manual reference loading.

Implement Loads Go Standards

User says: /implement ag-xyz-123 (issue modifies Go files)

What happens:

1. Implement skill reads issue metadata to identify file targets
2. Implement finds server.go in implementation scope
3. Implement loads standards/references/go.md for context
4. Implement writes code following Go standards (error handling, naming, package structure)
5. Implement validates output against loaded standards before committing

Result: Go code generated conforming to standards, reducing post-implementation vibe findings.

Troubleshooting

Reference Documents

• references/common-standards.md
• references/behavioral-discipline.md
• references/examples-troubleshooting-template.md
• references/go.md
• references/json.md
• references/markdown.md
• references/python.md
• references/rust.md
• references/shell.md
• references/skill-structure.md
• references/standards-index.md
• references/typescript.md
• references/sql-safety-checklist.md
• references/llm-trust-boundary-checklist.md
• references/race-condition-checklist.md
• references/codex-skill.md
• references/test-pyramid.md
• references/yaml.md