coding-standards

name	coding-standards
description	Bootstrap, update, or audit a project against deznode coding standards. Copies Claude rules, config templates (EditorConfig, Prettier, ESLint, Lefthook, Taskfile), and hooks into projects with ecosystem-aware selection and path customization. Use when user mentions "coding standards", "bootstrap rules", "update rules", "audit standards", "install coding standards", "sync standards", "check rule drift", "coding-standards setup", "apply coding standards", "mobile standards", "android rules", "kmp setup", "install ApiResult", "install source template", or "source files".
disable-model-invocation	true

Coding Standards

Bootstrap, update, or audit project configuration against deznode coding standards.

Pre-flight

Run detection script to assess current state:

python3 ${CLAUDE_SKILL_DIR}/scripts/detect_standards.py <project-root> [--standards-path <path>]

If standards_repo.found is false, ask user for the coding-standards repo path via AskUserQuestion.

Decision Flow

standards_repo.found?
├── No → Ask for path, re-run detector
└── Yes
    ├── No installed rules/configs AND no devtools_local → Bootstrap
    ├── devtools_local exists → AskUserQuestion: Update, Audit, or Install Source Templates?
    └── Has installed rules but no devtools_local → Offer Audit first

Operations

Bootstrap (first-time setup)

1. Confirm detected ecosystems (JVM → backend rules, Node.js → frontend rules, KMP/Android → mobile rules, infra always)
2. Collect project paths (API dir, web dir) via AskUserQuestion
3. Copy templates → .claude/rules/, configs → root, hooks → .claude/hooks/
4. Replace TODO markers with actual paths
5. Run lefthook install, chmod +x hooks, write .claude/devtools.local.md

Update (sync to latest)

1. Load config from .claude/devtools.local.md
2. Show comparison: new, modified, removed files
3. User selects updates to apply (with diff preview)
4. Apply and update last_update timestamp

Audit (read-only drift check)

1. Present compliance score and per-file status table
2. Offer to route to Update or Install Source Templates if issues found

Install Source Templates

1. List available source templates from templates/source-files/
2. Check which are already installed in the project (grep for key class names)
3. For each uninstalled template, offer to install with package substitution
4. Currently available: ApiResult.kt (API response wrappers)

See WORKFLOW.md for detailed steps. See EXAMPLES.md for usage examples. See TROUBLESHOOTING.md for common issues.

Key Rules

• Never overwrite without asking — always offer merge/replace/skip
• Detect first — run script before any file operations
• Ecosystem-aware — only copy relevant templates for detected stack (JVM → backend, Node.js → frontend, KMP/Android → mobile)
• Non-destructive — configs are expected to be customized; "modified" status in audit is informational
• Aspirational templates -- template rules describe target patterns (marked standard_type: aspirational). A codebase compatibility check (Step 4.5) identifies gaps and lets the user decide how to handle them. Source files like ApiResult.kt can be installed to implement the patterns.