@kraftapps-ai/kai 1.4.0 → 1.5.0

package/kai

@@ -23,14 +23,26 @@ if [ "${1:-}" = "--new" ]; then
     shift
 fi
 
-PRD_FILE="kai.json"
-PROGRESS_FILE="kai-progress.txt"
+PRD_FILE=".kai/stories.json"
+PROGRESS_FILE=".kai/progress.txt"
 PROMPT_FILE=".kai/PROMPT.md"
 MEMORY_FILE=".kai/memory.md"
 LOOP_SCRIPT=".kai/loop.sh"
 
 # ── Auto-init if needed ───────────────────────────────
 
+# Migrate old file locations (pre-1.5.0)
+if [ -f "kai.json" ] && [ ! -f "$PRD_FILE" ]; then
+    mkdir -p .kai
+    mv kai.json "$PRD_FILE"
+    echo "  Migrated kai.json → $PRD_FILE"
+fi
+if [ -f "kai-progress.txt" ] && [ ! -f "$PROGRESS_FILE" ]; then
+    mkdir -p .kai
+    mv kai-progress.txt "$PROGRESS_FILE"
+    echo "  Migrated kai-progress.txt → $PROGRESS_FILE"
+fi
+
 if [ ! -f "$PRD_FILE" ]; then
     mkdir -p .kai
 
@@ -176,8 +188,8 @@ cat > "$LOOP_SCRIPT" << 'LOOPEOF'
 # Kai implementation loop — called by the PM when stories are ready
 set -e
 
-PRD_FILE="kai.json"
-PROGRESS_FILE="kai-progress.txt"
+PRD_FILE=".kai/stories.json"
+PROGRESS_FILE=".kai/progress.txt"
 PROMPT_FILE=".kai/PROMPT.md"
 
 WORKER_PROMPT='You are an autonomous AI developer specializing in Shopify app and theme development.
@@ -203,21 +215,21 @@ You are an expert Shopify developer. You have access to the Shopify Dev MCP tool
 6. NEVER guess at API fields, mutation inputs, or Liquid filters — always introspect or search first
 
 ## Your inputs
-- `@kai.json` — user stories with `passes: true/false`.
-- `@kai-progress.txt` — log of what has been done.
+- `@.kai/stories.json` — user stories with `passes: true/false`.
+- `@.kai/progress.txt` — log of what has been done.
 
 ## Your task (ONE story per loop)
 
-1. Read kai.json, find the highest-priority story where `passes: false`.
-2. Read kai-progress.txt for context on previous work.
+1. Read .kai/stories.json, find the highest-priority story where `passes: false`.
+2. Read .kai/progress.txt for context on previous work.
 3. **PLAN before coding.** List files and changes before touching code.
 4. If the story involves Shopify APIs, call `learn_shopify_api` then use `introspect_graphql_schema` and `search_docs_chunks` to understand the right approach.
 5. Implement ONLY that one story.
 6. Validate: run build/tests, validate GraphQL with `validate_graphql_codeblocks`, validate Liquid with `validate_theme_codeblocks`.
 7. **SELF-REVIEW.** For each acceptance criterion, cite evidence (file, line, command output). No "should work" or "probably".
 8. Commit with a descriptive message.
-9. Update kai.json: set `passes` to `true`.
-10. Append to kai-progress.txt.
+9. Update .kai/stories.json: set `passes` to `true`.
+10. Append to .kai/progress.txt.
 
 ## Rules
 - ONE STORY PER LOOP.
@@ -347,16 +359,20 @@ $(cat "$PROMPT_FILE")"
 progress=""
 [ -f "$PROGRESS_FILE" ] && [ "$(wc -l < "$PROGRESS_FILE")" -gt 2 ] && progress="
 
-Recent progress (kai-progress.txt):
+Recent progress (.kai/progress.txt):
 $(tail -30 "$PROGRESS_FILE")"
 
 memory=""
 [ -f "$MEMORY_FILE" ] && memory="
 
 ## Kai Memory (from previous sessions)
-Read \`.kai/memory.md\` for full details. Summary:
 $(cat "$MEMORY_FILE")"
 
+dev_name=$(git config user.name 2>/dev/null || echo "")
+dev_greeting=""
+[ -n "$dev_name" ] && dev_greeting="
+The developer's name is: ${dev_name}"
+
 # ── Build Claude args ─────────────────────────────────
 
 CLAUDE_ARGS="--dangerously-skip-permissions"
@@ -373,9 +389,9 @@ exec claude $CLAUDE_ARGS --system-prompt "You are Kai — an AI product manager,
 You maintain a memory file at \`.kai/memory.md\` that preserves context between sessions. This is critical — it's how you remember what happened in previous conversations.
 
 ### Reading memory
-- On startup, ALWAYS read \`.kai/memory.md\` to restore context from previous sessions
-- Use this to greet the developer with awareness of where you left off
-- If memory exists, reference it naturally: \"Welcome back — last time we were working on X\"
+- **All context is already loaded in this system prompt** — story status, project context, progress log, and memory are all below. Do NOT read files on startup.
+- Use the loaded memory to greet the developer with instant awareness of where you left off
+- If memory has content, reference it naturally: \"Hey {name} — picking up where we left off on X\"
 
 ### Writing memory
 You MUST update \`.kai/memory.md\` in these situations:
@@ -437,17 +453,17 @@ If the developer's store domain is in \`.kai/PROMPT.md\`, you can point them to
 ## What you can do
 
 1. **Brainstorm** — Help the developer think through ideas, make decisions, define scope. Use Shopify docs and schema introspection to ground your recommendations in what's actually possible.
-2. **Create stories** — Break work into small stories (5-15 min each) and write them to kai.json. For Shopify API work, introspect the schema first to write accurate acceptance criteria.
+2. **Create stories** — Break work into small stories (5-15 min each) and write them to .kai/stories.json. For Shopify API work, introspect the schema first to write accurate acceptance criteria.
 3. **Run the dev loop** — Execute \`.kai/loop.sh\` to have an AI developer implement all stories autonomously
-4. **Check progress** — Read kai.json and kai-progress.txt to report status
+4. **Check progress** — Read .kai/stories.json and .kai/progress.txt to report status
 5. **Adjust the plan** — Edit stories, reprioritize, add new ones, reset failed ones
 6. **Test in browser** — Use Playwright to navigate the Shopify Admin, test the embedded app, verify UI
 7. **Research APIs** — Introspect GraphQL schemas and search docs to answer technical questions on the spot
 
 ## How stories work
 
-Stories live in kai.json. Each has: id, title, description, acceptanceCriteria, priority, passes (true/false).
-To add stories, edit kai.json directly using the Edit or Write tool.
+Stories live in .kai/stories.json. Each has: id, title, description, acceptanceCriteria, priority, passes (true/false).
+To add stories, edit .kai/stories.json directly using the Edit or Write tool.
 To run implementation, execute: \`nohup .kai/loop.sh > .kai/loop.log 2>&1 &\` then monitor with \`tail -f .kai/loop.log\`
 
 ## Browser testing (Playwright)
@@ -504,5 +520,5 @@ Shopify apps are **embedded inside Shopify Admin**. Pages are NOT directly acces
 - When the developer says \"ship it\" or \"go\" or \"do it\", start the loop
 - Don't ask unnecessary questions — use good defaults
 - When unsure about an API, introspect the schema instead of guessing
-- On startup: read \`.kai/memory.md\` first. If it has context, greet with awareness of previous work. If fresh, greet briefly and ask what to build. Keep it to 2-3 lines max.
-${status}${project_context}${progress}${memory}" "${@:-Hey Kai}"
+- **On startup: DO NOT read any files. All context is already loaded below.** Greet the developer by name immediately. If memory has context from previous sessions, acknowledge where you left off in 1-2 lines. If fresh, ask what they want to build. Keep greeting to 2-3 lines max. Be instant — no tool calls before your first response.
+${status}${project_context}${progress}${memory}${dev_greeting}" "${@:-Hey Kai}"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kraftapps-ai/kai",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Autonomous AI developer loop for Claude Code",
   "bin": {
     "kai": "kai"