joycraft 0.5.15 → 0.5.16

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/README.md CHANGED
@@ -52,7 +52,7 @@ Joycraft auto-detects your tech stack and creates:
52
52
 
53
53
  - **CLAUDE.md** with behavioral boundaries (Always / Ask First / Never) and correct build/test/lint commands
54
54
  - **AGENTS.md** for Codex compatibility
55
- - **11 skills** installed to `.claude/skills/` (Claude Code) and `.agents/skills/` (Codex) — see [Which skill do I need?](#which-skill-do-i-need) below
55
+ - **14 skills** installed to `.claude/skills/` (Claude Code) and `.agents/skills/` (Codex) — see [Which skill do I need?](#which-skill-do-i-need) below
56
56
  - **docs/** structure: `briefs/`, `specs/`, `discoveries/`, `contracts/`, `decisions/`, `context/`
57
57
  - **Context documents** in `docs/context/`: production map, dangerous assumptions, decision log, institutional knowledge, and troubleshooting guide
58
58
  - **Templates** including atomic spec, feature brief, implementation plan, boundary framework, and workflow templates for scenario generation and autofix loops
@@ -75,6 +75,7 @@ Frameworks auto-detected: Next.js, FastAPI, Django, Flask, Actix, Axum, Express,
75
75
  | Align on approach before writing code | `/joycraft-design` | Design discussion → ~200-line artifact for human review |
76
76
  | Break a feature into small, independent tasks | `/joycraft-decompose` | Feature Brief → testable Atomic Specs |
77
77
  | Fix a bug with a structured workflow | `/joycraft-bugfix` | Reproduce → isolate → fix → verify loop |
78
+ | Implement a spec with TDD | `/joycraft-implement` | Read spec → write failing tests → implement until green |
78
79
  | Run specs autonomously without hand-holding | `/joycraft-implement-level5` | Autofix loop + holdout scenario testing |
79
80
  | Verify an implementation independently | `/joycraft-verify` | Read-only subagent checks work against the spec |
80
81
 
@@ -84,23 +85,23 @@ The core loop:
84
85
  flowchart LR
85
86
  A[Interview] --> B[Feature Brief]
86
87
  B --> C{Complex?}
87
- C -- "Simple/clear scope" --> F[Decompose]
88
- C -- "Complex/unfamiliar" --> D[Research]
88
+ C -- "Simple" --> F[Decompose]
89
+ C -- "Complex" --> D[Research]
89
90
  D --> E[Design]
90
91
  E --> F
91
92
  F --> G[Atomic Specs]
92
- G --> H[Execute]
93
+ G --> H[Implement]
93
94
  H --> I[Session End]
94
95
 
95
- style A fill:#e8f4fd,stroke:#4a90d9
96
- style B fill:#e8f4fd,stroke:#4a90d9
97
- style C fill:#fef3cd,stroke:#d4a843
98
- style D fill:#f0e8fd,stroke:#9b72cf
99
- style E fill:#f0e8fd,stroke:#9b72cf
100
- style F fill:#e8f4fd,stroke:#4a90d9
101
- style G fill:#e8f4fd,stroke:#4a90d9
102
- style H fill:#d4edda,stroke:#5a9a6e
103
- style I fill:#d4edda,stroke:#5a9a6e
96
+ style A fill:#fff,stroke:#333,stroke-width:2px
97
+ style B fill:#fff,stroke:#333,stroke-width:2px
98
+ style C fill:#fff,stroke:#333,stroke-width:2px
99
+ style D fill:#e8e8e8,stroke:#333,stroke-width:2px
100
+ style E fill:#e8e8e8,stroke:#333,stroke-width:2px
101
+ style F fill:#fff,stroke:#333,stroke-width:2px
102
+ style G fill:#fff,stroke:#333,stroke-width:2px
103
+ style H fill:#333,stroke:#333,color:#fff,stroke-width:2px
104
+ style I fill:#333,stroke:#333,color:#fff,stroke-width:2px
104
105
  ```
105
106
 
106
107
  ### The Interview