ateschh-kit 1.0.0

package/workflows/settings.md

@@ -0,0 +1,92 @@
+---
+command: "/settings"
+description: "View and edit your ateschh-kit configuration."
+phase: "any"
+agents: []
+skills: []
+outputs: [".state/USER-CONFIG.md"]
+---
+
+# /settings — View & Edit Configuration
+
+## Steps
+
+### Step 1: Read Config
+
+Read `.state/USER-CONFIG.md`:
+- If it exists → display current settings
+- If it doesn't exist → run first-time setup
+
+### Step 2: Display Settings
+
+```
+⚙️ ateschh-kit Settings
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Kit Version:     1.0.0
+Config File:     .state/USER-CONFIG.md
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+What would you like to change?
+1. View all settings
+2. Set active project
+3. Reset all state
+4. View system info
+5. Cancel
+```
+
+### Option 1: View All Settings
+
+Display contents of `.state/USER-CONFIG.md` in formatted output.
+
+### Option 2: Set Active Project
+
+List all projects in `projects/` folder.
+Ask: "Which project should be active?"
+Update `.state/ACTIVE-PROJECT.md`.
+
+### Option 3: Reset All State
+
+⚠️ Warning dialog:
+```
+WARNING: This will clear:
+- Active project reference
+- Session log
+- Active context
+
+It will NOT delete your projects/ or archive/ folders.
+
+Type "RESET" to confirm.
+```
+
+If confirmed:
+- Clear `.state/ACTIVE-PROJECT.md`
+- Clear `.state/ACTIVE_CONTEXT.md`
+- Leave `SESSION-LOG.md` intact (historical record)
+
+### Option 4: View System Info
+
+```
+System Info:
+- OS: {detected OS}
+- Kit location: {current directory}
+- Projects: {count} active, {count} archived
+- Total sessions: {count from SESSION-LOG.md}
+- Context7 MCP: {connected / not connected}
+- Other MCPs: {list}
+```
+
+## USER-CONFIG.md Format
+
+```markdown
+# User Configuration
+
+**Created**: {date}
+**Version**: 1.0.0
+
+## Preferences
+
+(No preferences configured yet — defaults are used)
+```
+
+Users can manually edit this file to add custom preferences that agents will respect.

package/workflows/status.md

@@ -0,0 +1,67 @@
+---
+command: "/status"
+description: "Shows current project progress and what comes next."
+phase: "any"
+agents: []
+skills: []
+outputs: ["Progress report"]
+---
+
+# /status — Progress Report
+
+## When to Use
+
+Any time you want to see where the project stands.
+
+## Steps
+
+### Step 1: Read Files
+
+Read:
+- `.state/ACTIVE-PROJECT.md`
+- `projects/{name}/STATE.md`
+- `projects/{name}/PLAN.md`
+
+### Step 2: Calculate Progress
+
+Count tasks in PLAN.md:
+- Total tasks
+- Completed tasks (checked)
+- Remaining tasks
+
+Calculate: `{done}/{total} tasks complete ({percent}%)`
+
+### Step 3: Generate Report
+
+```
+## Project Status — {name}
+📅 Last active: {date}
+
+### Phase Progress
+Phase 1 — Idea & Research:     ✅ Complete
+Phase 2 — Requirements:        ✅ Complete
+Phase 3 — Design:              ✅ Complete
+Phase 4 — Build:               🔄 In Progress (6/12 tasks)
+Phase 5 — Test:                ⬜ Not started
+Phase 6 — Deploy:              ⬜ Not started
+
+### Current Task
+➡️ {current task name}
+
+### Completed Today
+- {task 1}
+- {task 2}
+
+### Remaining in Phase 4
+- {task list}
+
+### Backlog
+{N} items in BACKLOG.md
+
+### Next Command
+Run `/build` to continue with: "{next task}"
+```
+
+### Step 4: Ask
+
+"Want to continue? Run `/build` or `/next` to keep going."

package/workflows/test.md

@@ -0,0 +1,105 @@
+---
+command: "/test"
+description: "Runs L3+L4 testing across the full app. Fixes bugs before deploy."
+phase: "5"
+agents: ["tester", "debugger"]
+skills: ["run-tests", "fix-bugs"]
+outputs: ["Test report", "Fixed bugs", "Updated STATE.md"]
+---
+
+# /test — Test & Fix
+
+## When to Use
+
+When all tasks in PLAN.md are complete and you're preparing for deployment.
+
+## Steps
+
+### Step 1: Verify Phase
+
+Read `projects/{name}/STATE.md`. Confirm all Phase 4 tasks are checked off.
+
+### Step 2: Spawn Tester Agent
+
+Read `agents/tester.md` and spawn the agent.
+
+The tester runs the full 4-level suite:
+
+#### L1 — Syntax
+- [ ] `npm run build` exits cleanly
+- [ ] Zero TypeScript errors
+- [ ] Zero ESLint errors
+
+#### L2 — Functionality (per feature)
+- [ ] Each feature in STRUCTURE.md works as described
+- [ ] No broken imports or missing components
+
+#### L3 — Integration
+- [ ] Navigation between pages works
+- [ ] Data flows correctly (form → database → UI)
+- [ ] Auth gates protect the right routes
+- [ ] API responses handled (success + error states)
+
+#### L4 — Quality
+- [ ] Mobile responsive (if web)
+- [ ] Loading states present
+- [ ] No console.log left in production code
+- [ ] Environment variables properly set
+- [ ] No hardcoded credentials
+
+### Step 3: Process Failures
+
+For each failure found:
+
+1. Log it: `[L{N}] {what broke} — {file:line}`
+2. Spawn `debugger` agent with the failure details
+3. Apply fix
+4. Re-verify that specific check
+
+### Step 4: Generate Test Report
+
+```
+## Test Report — {date}
+
+| Level | Total | Passed | Failed |
+|-------|-------|--------|--------|
+| L1 | N | N | N |
+| L2 | N | N | N |
+| L3 | N | N | N |
+| L4 | N | N | N |
+
+### Issues Fixed
+- {issue}: {fix applied}
+
+### Remaining Issues (if any)
+- {issue}: {reason not fixed / plan}
+```
+
+### Step 5: Update STATE.md
+
+Mark Phase 5 complete if all blocking issues are resolved.
+
+### Step 6: Confirm to User
+
+```
+✅ Testing complete!
+
+L1–L4 all passing.
+{N} issues found and fixed.
+
+Ready to deploy: run `/deploy`
+```
+
+Or if issues remain:
+```
+⚠️ Testing complete with {N} unresolved issues.
+
+These won't block deployment but should be addressed soon:
+- {issue list}
+
+Run `/deploy` when you're ready.
+```
+
+## Next Step
+
+`/deploy`