@haposoft/cafekit 0.7.13 → 0.7.14

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@haposoft/cafekit",
3
- "version": "0.7.13",
3
+ "version": "0.7.14",
4
4
  "description": "Spec-Driven Development workflow for AI coding assistants. Supports Claude Code and Antigravity with spec-first workflows plus Claude Code hapo: skills.",
5
5
  "author": "Haposoft <nghialt@haposoft.com>",
6
6
  "license": "MIT",
@@ -11,15 +11,13 @@ Focus on capabilities and outcomes, not code structure.
11
11
  - Features and capabilities
12
12
  - Domain language and concepts
13
13
  - Data relationships and workflows
14
+ **Required (Code-Level Implementation Style)**:
15
+ - File paths and specific UI components
16
+ - Database tables, columns, and Zod/Type schemas
17
+ - API payloads, routes, and JSON contracts
18
+ - Edge cases, error handling, and exact validation thresholds
14
19
 
15
- **Avoid**:
16
- - File paths and directory structure
17
- - Function/method names and signatures
18
- - Type definitions and interfaces
19
- - Class names and API contracts
20
- - Specific data structures
21
-
22
- **Rationale**: Implementation details (files, methods, types) are defined in design.md. Tasks describe the functional work to be done.
20
+ **Rationale**: AI Coders (like god-developer or ck) consume these tasks directly. If a sub-task is written like PM business jargon (e.g., "Define pass thresholds") instead of code-level instructions (e.g., "Implement `gap_ratio < 15%` threshold in `evaluator.ts`"), the AI coder will hallucinate or fail. Tasks are not PRDs; they are explicit coding orders.
23
21
 
24
22
  ### 2. Task Integration & Progression
25
23