メニュー
Language-specific coding standards and validation rules. Provides Python, Go, TypeScript, Shell, YAML, JSON, and Markdown standards. Auto-loaded by /vibe, /implement, /doc, /bug-hunt, /complexity based on file types.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | standards |
| description | Language-specific coding standards and validation rules. Provides Python, Go, TypeScript, Shell, YAML, JSON, and Markdown standards. Auto-loaded by /vibe, /implement, /doc, /bug-hunt, /complexity based on file types. |
Language-specific coding standards loaded on-demand by other skills.
This is a library skill - it doesn't run standalone but provides standards references that other skills load based on file types being processed.
| Language | Reference | Loaded By |
|---|---|---|
| Python | references/python.md | vibe, implement, complexity |
| Go | references/go.md | vibe, implement, complexity |
| TypeScript | references/typescript.md | vibe, implement |
| Shell | references/shell.md | vibe, implement |
| YAML | references/yaml.md | vibe |
| JSON | references/json.md | vibe |
| Markdown | references/markdown.md | vibe, doc |
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')
# etc.
For comprehensive audits, skills can load extended standards from
vibe/references/*-standards.md which contain full compliance catalogs.
| Standard | Size | Use Case |
|---|---|---|
| Tier 1 (this skill) | ~5KB each | Normal validation |
| Tier 2 (vibe/references) | ~15-20KB each | Deep audits, --deep flag |
Skills that use standards:
/vibe - Loads based on changed file types/implement - Loads for files being modified/doc - Loads markdown standards/bug-hunt - Loads for root cause analysis/complexity - Loads for refactoring recommendationsThis skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Analyze code complexity and find refactor targets using radon/gocyclo. Triggers: "complexity", "analyze complexity", "find complex code", "refactor targets", "cyclomatic complexity", "code metrics".
Fully autonomous epic execution. Runs until ALL children are CLOSED. Level 1 uses /swarm (Task tool). Level 2 uses /spawn + Agent Mail for cross-session orchestration with Chiron help routing. NO human prompts, NO stopping.
This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.
Extract decisions and learnings from Claude session transcripts. Triggers: "extract learnings", "process pending", SessionStart hook.