jettypod 4.4.118 → 4.4.121

package/skills-templates/epic-planning/SKILL.md

@@ -17,7 +17,7 @@ When this skill is activated, you are helping plan an epic. Follow this structur
 
 ---
 
-**⚡ FIRST: Detect Technical Epic**
+**FIRST: Detect Technical Epic**
 
 Before proceeding, check if this is a **technical epic** by looking for these signals in the request or context passed from request-routing:
 
@@ -50,7 +50,7 @@ jettypod work status ${EPIC_ID}
 
 Capture the title, description, and any existing context.
 
-**🔄 WORKFLOW INTEGRATION: Start workflow tracking**
+**WORKFLOW INTEGRATION: Start workflow tracking**
 
 After getting the epic context, register this skill execution:
 
@@ -109,14 +109,23 @@ I'd like to understand this epic better before suggesting features.
 
 **WAIT for user answers.**
 
-Then synthesize into an epic title + description and create:
+Then synthesize into an epic title + description. Use the **Write** tool to create `/tmp/jettypod-create.json`:
+```json
+{
+  "type": "epic",
+  "title": "${EPIC_TITLE}",
+  "description": "${EPIC_DESCRIPTION}"
+}
+```
+
+Then run via **Bash**:
 ```bash
-jettypod work create epic "${EPIC_TITLE}" "${EPIC_DESCRIPTION}"
+jettypod work create --from=/tmp/jettypod-create.json
 ```
 
 Capture the new epic ID from output.
 
-**🔄 WORKFLOW INTEGRATION: Start workflow tracking**
+**WORKFLOW INTEGRATION: Start workflow tracking**
 
 After creating the epic, register this skill execution:
 
@@ -162,7 +171,7 @@ Fresh start.
 Previous planning was started but not completed. Present existing decisions:
 
 ```
-🎯 **Existing Architectural Decisions for This Epic:**
+**Existing Architectural Decisions for This Epic:**
 
 [For each decision:]
 - **[Aspect]:** [Decision]
@@ -181,7 +190,7 @@ Do these still apply, or should we revisit any?
 Planning was previously completed or partially completed. Present what exists:
 
 ```
-🎯 **This epic already has children:**
+**This epic already has children:**
 
 [List features/chores from children command]
 
@@ -212,6 +221,14 @@ Based on [epic name], here are the features I recommend:
 **Feature 3: [Name]** - [Brief description]
 ...
 
+**UX Completeness Check:**
+For each feature above, I've considered:
+- How users discover/reach it (entry point)
+- What they see while waiting (loading states)
+- What they see when there's no data (empty states)
+- What feedback they get after actions (success/error)
+- How screens transition between states
+
 **Questions:**
 - [Any clarifying questions about scope]
 - [Missing features to consider]
@@ -252,7 +269,7 @@ When user confirms chores (says "looks good", "yes", lists modifications, etc.),
 
 ### Step 4: Architectural Decision (Optional)
 
-**⚠️ SKIP THIS STEP if `IS_TECHNICAL_EPIC = true`** - Technical epics don't need architectural decisions. Go directly to Step 6.
+**SKIP THIS STEP if `IS_TECHNICAL_EPIC = true`** - Technical epics don't need architectural decisions. Go directly to Step 6.
 
 After features are defined, ask if this epic needs a shared technical approach.
 
@@ -284,18 +301,18 @@ Present exactly 3 approaches. Fill in the bracketed parts with actual content ba
 > Here are 3 different architectural approaches for **[fill in epic title]**:
 >
 > **Option 1: [Simple approach - you fill this in]**
-> - **Pros**: ✅ [2-3 actual advantages]
-> - **Cons**: ❌ [2-3 actual trade-offs]
+> - **Pros**: [2-3 actual advantages]
+> - **Cons**: [2-3 actual trade-offs]
 > - **Technical Impact**: [How this affects the features]
 >
 > **Option 2: [Balanced approach - you fill this in]**
-> - **Pros**: ✅ [2-3 actual advantages]
-> - **Cons**: ❌ [2-3 actual trade-offs]
+> - **Pros**: [2-3 actual advantages]
+> - **Cons**: [2-3 actual trade-offs]
 > - **Technical Impact**: [How this affects the features]
 >
 > **Option 3: [Advanced approach - you fill this in]**
-> - **Pros**: ✅ [2-3 actual advantages]
-> - **Cons**: ❌ [2-3 actual trade-offs]
+> - **Pros**: [2-3 actual advantages]
+> - **Cons**: [2-3 actual trade-offs]
 > - **Technical Impact**: [How this affects the features]
 >
 > Would you like me to create working prototypes to compare these?
@@ -322,10 +339,16 @@ jettypod work prototype start 5 websockets
 
 This creates a worktree at `.jettypod-work/prototype-<id>-<slug>-<approach>/` where prototypes can be safely built and committed.
 
-**🛑 STOP AND CHECK:** Verify worktree was created successfully before proceeding.
+**STOP AND CHECK:** Verify worktree was created successfully before proceeding.
 
 **Sub-step 2: Build prototypes in the worktree**
 
+**Design system check:** Before building, check if a design system directory is configured:
+```bash
+node -e "const c=JSON.parse(require('fs').readFileSync('.jettypod/config.json','utf-8')); c.designSystemDir && console.log(c.designSystemDir)"
+```
+If a path is returned, read the files in that directory and apply the project's design tokens (colors, typography, spacing, border radii, component patterns) to all prototypes.
+
 1. Build prototypes using **absolute paths** to the worktree:
    - `<worktree_path>/prototypes/epic-${EPIC_ID}-${APPROACH_NAME}/`
 2. Build 2-3 working prototypes demonstrating the architectural difference
@@ -380,24 +403,30 @@ jettypod backlog
 
 **If `IS_TECHNICAL_EPIC = true`:** Create chores
 
-For each chore the user agreed on, execute this command:
-
-```bash
-jettypod work create chore "${CHORE_TITLE}" "${CHORE_DESCRIPTION}" --parent=${EPIC_ID}
+For each chore the user agreed on, use the **Write** tool to create `/tmp/jettypod-create.json`:
+```json
+{
+  "type": "chore",
+  "title": "${CHORE_TITLE}",
+  "description": "${CHORE_DESCRIPTION}",
+  "parent": ${EPIC_ID}
+}
 ```
 
-**Example** (if epic ID is 5):
+Then run via **Bash**:
 ```bash
-jettypod work create chore "Migrate auth module to ESM" "Convert require() to import in auth/" --parent=5
+jettypod work create --from=/tmp/jettypod-create.json
 ```
 
+**Example** (if epic ID is 5): Write `{"type":"chore","title":"Migrate auth module to ESM","description":"Convert require() to import in auth/","parent":5}` to `/tmp/jettypod-create.json`, then run `jettypod work create --from=/tmp/jettypod-create.json`.
+
 After each successful creation, emit gate signal and tell the user:
 
 ```bash
 jettypod ui gate work-created --data='{"id":[id],"title":"[chore title]"}'
 ```
 
-> ✅ Created Chore #[id from output]: [title]
+> Created Chore #[id from output]: [title]
 
 **Then skip to Step 7** (no architectural decision for technical epics).
 
@@ -405,24 +434,30 @@ jettypod ui gate work-created --data='{"id":[id],"title":"[chore title]"}'
 
 **If `IS_TECHNICAL_EPIC = false`:** Create features
 
-For each feature the user agreed on, execute this command using the epic ID from Step 1:
-
-```bash
-jettypod work create feature "${FEATURE_TITLE}" "${FEATURE_DESCRIPTION}" --parent=${EPIC_ID}
+For each feature the user agreed on, use the **Write** tool to create `/tmp/jettypod-create.json`:
+```json
+{
+  "type": "feature",
+  "title": "${FEATURE_TITLE}",
+  "description": "${FEATURE_DESCRIPTION}",
+  "parent": ${EPIC_ID}
+}
 ```
 
-**Example** (if epic ID is 5):
+Then run via **Bash**:
 ```bash
-jettypod work create feature "Live cursor tracking" "Track cursor positions in real-time" --parent=5
+jettypod work create --from=/tmp/jettypod-create.json
 ```
 
+**Example** (if epic ID is 5): Write `{"type":"feature","title":"Live cursor tracking","description":"Track cursor positions in real-time","parent":5}` to `/tmp/jettypod-create.json`, then run `jettypod work create --from=/tmp/jettypod-create.json`.
+
 After each successful creation, emit gate signal and tell the user:
 
 ```bash
 jettypod ui gate work-created --data='{"id":[id],"title":"[feature title]"}'
 ```
 
-> ✅ Created Feature #[id from output]: [title]
+> Created Feature #[id from output]: [title]
 
 #### Step 6B: Record Architectural Decision (Conditional)
 
@@ -455,7 +490,7 @@ jettypod work epic-implement 5 --aspect="Architecture" --decision="WebSockets wi
 ```
 
 After success, tell the user:
-> ✅ Architectural decision recorded
+> Architectural decision recorded
 
 ---
 
@@ -474,13 +509,13 @@ Based on the output, recommend which item to plan first.
 
 **Say to user:**
 > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-> 🎯 Epic Planning Complete!
+> Epic Planning Complete!
 > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 >
 > Created under this epic:
 > [List the actual items from the children command output]
 >
-> 💡 Recommendation: Start with Feature #[actual id] ([actual title])
+> Recommendation: Start with Feature #[actual id] ([actual title])
 >    [Your reasoning - e.g., "It's foundational - other features depend on it."]
 >
 > Plan this one now? [yes / pick different / done for now]
@@ -526,9 +561,9 @@ Display a numbered list of all created items:
 ```
 Which item would you like to plan?
 
-1. ✨ Feature #[id]: [title]
-2. ✨ Feature #[id]: [title]
-3. 🔧 Chore #[id]: [title]
+1. Feature #[id]: [title]
+2. Feature #[id]: [title]
+3. Chore #[id]: [title]
 
 Enter the number of your choice:
 ```
@@ -558,7 +593,7 @@ Chores:
 Or run: jettypod backlog to see all items.
 ```
 
-**🔄 WORKFLOW INTEGRATION: Complete workflow**
+**WORKFLOW INTEGRATION: Complete workflow**
 
 ```bash
 jettypod workflow complete epic-planning <epic-id>
@@ -593,18 +628,18 @@ Epic: "Real-time Collaboration"
 **Architectural approaches suggested:**
 
 **Option 1: Long Polling (REST)**
-- **Pros**: ✅ Simple, works with all proxies, uses existing HTTP infrastructure
-- **Cons**: ❌ Higher latency (1-2s), more server load, inefficient for high-frequency updates
+- **Pros**: Simple, works with all proxies, uses existing HTTP infrastructure
+- **Cons**: Higher latency (1-2s), more server load, inefficient for high-frequency updates
 - **Technical Impact**: Each feature polls independently, easy to implement per feature
 
 **Option 2: Server-Sent Events (SSE)**
-- **Pros**: ✅ Lightweight, auto-reconnection, efficient one-way streaming
-- **Cons**: ❌ One-direction only (server→client), limited browser connections (6 per domain)
+- **Pros**: Lightweight, auto-reconnection, efficient one-way streaming
+- **Cons**: One-direction only (server→client), limited browser connections (6 per domain)
 - **Technical Impact**: Good for cursor/presence, requires separate POST for edits
 
 **Option 3: WebSockets (Socket.io)**
-- **Pros**: ✅ Bidirectional, low latency (<100ms), perfect for real-time, fallback support
-- **Cons**: ❌ More complex infrastructure, requires sticky sessions, WebSocket proxies needed
+- **Pros**: Bidirectional, low latency (<100ms), perfect for real-time, fallback support
+- **Cons**: More complex infrastructure, requires sticky sessions, WebSocket proxies needed
 - **Technical Impact**: All features use unified connection, best UX but infrastructure complexity
 
 **Additional approaches considered:**
@@ -657,13 +692,12 @@ Epic: "Migrate Codebase from CommonJS to ESM"
 
 **Architectural decision:** Skipped (not needed for technical work)
 
-**Commands run:**
+**Commands run (Write tool + Bash for each):**
 ```bash
-jettypod work create chore "Migrate utility modules" "Convert src/utils/ from require() to import" --parent=42
-jettypod work create chore "Migrate lib modules" "Convert lib/ from require() to import" --parent=42
-jettypod work create chore "Migrate core business logic" "Convert src/core/ from require() to import" --parent=42
-jettypod work create chore "Update build configuration" "Update webpack/rollup for ESM output" --parent=42
-jettypod work create chore "Update test configuration" "Update Jest config for ESM" --parent=42
+# For each chore: Write JSON to /tmp/jettypod-create.json, then:
+jettypod work create --from=/tmp/jettypod-create.json
+# Repeated for: Migrate utility modules, Migrate lib modules,
+# Migrate core business logic, Update build configuration, Update test configuration
 ```
 
 **Routing:** All chores route to `chore-planning` → `chore-mode` (no mode progression)

package/skills-templates/external-transition/SKILL.md

@@ -31,7 +31,7 @@ Say to the user:
 ```
 You're ready to transition to external state. Here's what that means:
 
-🏗️  **Infrastructure Work Items Will Be Created:**
+ **Infrastructure Work Items Will Be Created:**
 
 I'll create an "Infrastructure Readiness" epic with 15 work items across 4 categories:
 
@@ -58,7 +58,7 @@ I'll create an "Infrastructure Readiness" epic with 15 work items across 4 categ
   - Data retention policy
   - Security headers implemented
 
-📦 **Production Chores Will Be Generated:**
+**Production Chores Will Be Generated:**
 
 For each feature currently in stable mode, I'll:
   • Generate production scenarios from your chosen standards
@@ -68,7 +68,7 @@ For each feature currently in stable mode, I'll:
 
 This uses your feature's BDD scenarios as context for what needs hardening.
 
-⚠️  **Mode Requirement Changes:**
+ **Mode Requirement Changes:**
 
 After this transition, ALL customer-facing features MUST be built through Production mode (not Stable).
 
@@ -83,7 +83,7 @@ Ready to proceed? (yes/no)
 
 Wait for the user to respond with "yes" or similar affirmative response.
 
-**🔄 WORKFLOW INTEGRATION: Start workflow tracking**
+**WORKFLOW INTEGRATION: Start workflow tracking**
 
 After receiving initial confirmation, register this skill execution:
 
@@ -103,67 +103,67 @@ After user confirms, explain production standards and show preset options:
 Before we transition, let's establish your production standards. These define what "production-ready" means for your project and will guide all future production work.
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📋 Choose Your Production Standards Preset
+Choose Your Production Standards Preset
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-🚀 **Startup MVP**
+**Startup MVP**
 Early-stage products, internal tools going external, prototypes with first users
 
 Examples: Beta SaaS with first 20 customers, internal tool opened to partners, developer tool in early access, side project gaining traction
 
 What you get:
-  ✅ HTTPS/TLS, basic auth, structured logging
-  ✅ Health checks, daily backups (24h RPO)
-  ✅ Single region, 2 instances, 99.0% SLO
-  ❌ No 24/7 on-call, no multi-region
+  HTTPS/TLS, basic auth, structured logging
+  Health checks, daily backups (24h RPO)
+  Single region, 2 instances, 99.0% SLO
+  No 24/7 on-call, no multi-region
 
 Cost: $200–$500/mo | Time: 1–2 weeks
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-🏢 **Production SaaS**
+**Production SaaS**
 Established SaaS with paying customers, revenue dependency, uptime expectations
 
 Examples: B2B SaaS with annual contracts, consumer app with 5k DAU, API service with enterprise customers, e-commerce platform
 
 What you get:
-  ✅ WAF + rate limiting, OAuth/OIDC
-  ✅ APM with SLO dashboards, PII sanitization
-  ✅ Zero-downtime deployments, 15min backups
-  ✅ Multi-AZ, on-call rotation, 99.9% SLO
-  ⚠️ Single region (multi-region optional)
+  WAF + rate limiting, OAuth/OIDC
+  APM with SLO dashboards, PII sanitization
+  Zero-downtime deployments, 15min backups
+  Multi-AZ, on-call rotation, 99.9% SLO
+  Single region (multi-region optional)
 
 Cost: $1.5k–$4k/mo infra + $2k–$3k/mo ops | Time: 4–6 weeks
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-🏛️ **Enterprise**
+**Enterprise**
 Mission-critical systems, large customer base with strict SLAs, Fortune 500 customers
 
 Examples: Enterprise SaaS for F500, financial services platform, infrastructure/DevOps tooling, global marketplace
 
 What you get:
-  ✅ Everything in Production SaaS, plus:
-  ✅ Multi-region active-passive or active-active
-  ✅ Advanced DDoS, mTLS, per-tenant encryption
-  ✅ SOC2 Type II ready, chaos engineering
-  ✅ PITR backups (1min RPO), 99.95% SLO
+  Everything in Production SaaS, plus:
+  Multi-region active-passive or active-active
+  Advanced DDoS, mTLS, per-tenant encryption
+  SOC2 Type II ready, chaos engineering
+  PITR backups (1min RPO), 99.95% SLO
 
 Cost: $5k–$15k/mo infra + $4k–$8k/mo ops | Time: 8–12 weeks
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-🏥 **Regulated (Healthcare, Finance, Gov)**
+**Regulated (Healthcare, Finance, Gov)**
 Products handling PHI, PCI, FedRAMP - strict compliance mandates, legal liability
 
 Examples: Healthcare app (HIPAA), fintech/payments (PCI), government contractor (FedRAMP), legal tech, HR platform
 
 What you get:
-  ✅ Everything in Enterprise, plus:
-  ✅ HIPAA/PCI/FedRAMP compliance controls
-  ✅ Encryption at rest/in transit, MFA, PAM
-  ✅ Quarterly pentesting, annual audits
-  ✅ Real-time replication, 99.99% SLO
+  Everything in Enterprise, plus:
+  HIPAA/PCI/FedRAMP compliance controls
+  Encryption at rest/in transit, MFA, PAM
+  Quarterly pentesting, annual audits
+  Real-time replication, 99.99% SLO
 
 Cost: $10k–$30k/mo infra + $6k–$12k/mo ops + $20k–$50k/yr audits | Time: 12–24 weeks
 
@@ -236,7 +236,7 @@ Then show recommendations to the user:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📋 Recommended Production Standards
+Recommended Production Standards
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Based on:
@@ -250,33 +250,33 @@ Based on:
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-✅ SECURITY ([X] standards)
+SECURITY ([X] standards)
 
-  [✓] TLS/HTTPS enforcement
+  [] TLS/HTTPS enforcement
       Why: [reasoning]
       Test: [acceptance criteria]
 
-  [✓] [Other security standards...]
+  [] [Other security standards...]
 
-✅ PERFORMANCE & SCALE ([X] standards)
+PERFORMANCE & SCALE ([X] standards)
 
-  [✓] Performance budgets
+  [] Performance budgets
       Why: [reasoning]
       Test: [acceptance criteria]
 
-  [✓] [Other scale standards...]
+  [] [Other scale standards...]
 
-✅ COMPLIANCE ([X] standards)
+COMPLIANCE ([X] standards)
 
-  [✓] [Compliance standards if applicable]
+  [] [Compliance standards if applicable]
 
-✅ INFRASTRUCTURE ([X] standards)
+INFRASTRUCTURE ([X] standards)
 
-  [✓] [Infrastructure standards]
+  [] [Infrastructure standards]
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-💰 Estimated Cost: $[X]–$[Y]/mo
+Estimated Cost: $[X]–$[Y]/mo
 
   Infrastructure: $[range]
   Operations: $[range]
@@ -284,7 +284,7 @@ Based on:
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-⚠️  Warnings (if any)
+ Warnings (if any)
 
   • [Warning messages for edge cases]
 
@@ -325,12 +325,12 @@ saveStandards(generatedStandards);
 Then confirm to user:
 
 ```
-✅ Production standards saved to .jettypod/production-standards.json
+Production standards saved to .jettypod/production-standards.json
 
 These standards will guide all production mode work going forward.
 ```
 
-**🔄 WORKFLOW CHECKPOINT: Standards saved**
+**WORKFLOW CHECKPOINT: Standards saved**
 
 ```bash
 jettypod workflow checkpoint --step=7
@@ -359,15 +359,15 @@ jettypod project external
 After the command completes successfully, relay the results to the user:
 
 ```
-✅ **Transition Complete!**
+**Transition Complete!**
 
 Your project is now in external state.
 
-📦 Created Infrastructure Readiness epic with:
+Created Infrastructure Readiness epic with:
   • 4 features (Security, Monitoring, Infrastructure, Compliance)
   • 15 chores across those features
 
-🔍 Production mode work items are now visible in your backlog.
+Production mode work items are now visible in your backlog.
 
 **Next Steps:**
 
@@ -378,7 +378,7 @@ Your project is now in external state.
 **Want to start on infrastructure work now?**
 ```
 
-**🔄 WORKFLOW INTEGRATION: Complete workflow**
+**WORKFLOW INTEGRATION: Complete workflow**
 
 ```bash
 jettypod workflow complete external-transition