Files
Claude-Code-Workflow/.ccw/specs/architecture-constraints.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

732 B

title, dimension, category, keywords, readMode, priority, scope
title dimension category keywords readMode priority scope
Architecture Constraints specs planning
architecture
module
layer
pattern
required high project

Architecture Constraints

Module Boundaries

  • Each module owns its data and exposes a public API
  • No circular dependencies between modules
  • Shared utilities live in a dedicated shared layer

Layer Separation

  • Presentation layer must not import data layer directly
  • Business logic must be independent of framework specifics
  • Configuration must be externalized, not hardcoded

Dependency Rules

  • External dependencies require justification
  • Prefer standard library when available
  • Pin dependency versions for reproducibility