Files
Claude-Code-Workflow/.ccw/specs/coding-conventions.md
catlog22 ecf4e4d848 fix: align spec paths from .workflow/specs to .ccw/specs
- Fix path mismatch between command files and frontend/backend spec-index-builder
- Update init-specs.md, init-guidelines.md, sync.md, solidify.md to use .ccw/specs/
- Update init.md, start.md, clean.md, unified-execute-with-file.md, collaborative-plan-with-file.md
- Add scope field to architecture-constraints.md and coding-conventions.md
- Ensures specs created by commands are visible in frontend Spec Settings page
2026-03-01 13:28:54 +08:00

722 B

title, dimension, category, keywords, readMode, priority, scope
title dimension category keywords readMode priority scope
Coding Conventions specs general
typescript
naming
style
convention
required high project

Coding Conventions

Naming

  • Use camelCase for variables and functions
  • Use PascalCase for classes and interfaces
  • Use UPPER_SNAKE_CASE for constants

Formatting

  • 2-space indentation
  • Single quotes for strings
  • Trailing commas in multi-line constructs

Patterns

  • Prefer composition over inheritance
  • Use early returns to reduce nesting
  • Keep functions under 30 lines when practical

Error Handling

  • Always handle errors explicitly
  • Prefer typed errors over generic catch-all
  • Log errors with sufficient context