@boopkit/cap-product-design 0.6.6 → 0.6.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -98,6 +98,12 @@ The positive form is also more durable. Defects get fixed and the prose goes sta
|
|
|
98
98
|
|
|
99
99
|
This is a stronger form of the strawman rule: do not motivate a design against a wrong implementation, real or imagined. State the destination.
|
|
100
100
|
|
|
101
|
+
## No verify-later breadcrumbs
|
|
102
|
+
|
|
103
|
+
Do not write "verify X during design" or "confirm the capability supports Y" notes into specs.
|
|
104
|
+
Research always precedes the work, so discovery surfaces these naturally — a pre-written flag adds noise and goes stale.
|
|
105
|
+
State the decision; let the design phase find its own facts.
|
|
106
|
+
|
|
101
107
|
## Architecture Layering
|
|
102
108
|
|
|
103
109
|
Well-designed systems separate concerns into layers with clear responsibilities and one-directional dependencies. The exact layers vary by project type, but the principle is universal:
|