takomi 2.0.4 → 2.0.5

package/assets/.agent/skills/takomi/workflows/vibe-finalize.md

@@ -0,0 +1,208 @@
+---
+description: Final verification, acceptance audit, and handoff report generation.
+---
+
+# Workflow: Finalize Build
+
+> Run final verification and generate the complete handoff report.
+> Use when all MUS features are implemented (or user says "ship it").
+
+---
+
+## Steps
+
+### 1. Full Verification
+
+Run the complete verification suite:
+
+```bash
+python scripts/vibe-verify.py
+```
+
+**All checks must pass:**
+- ✅ TypeScript: PASS
+- ✅ Lint: PASS
+- ✅ Build: PASS
+
+**If any check fails:** Fix it before proceeding.
+
+---
+
+### 2. Acceptance Criteria Audit
+
+Scan all issue files and verify completion:
+
+```powershell
+# Count completed vs incomplete
+Get-Content docs/issues/*.md | Select-String "- \[x\]" | Measure-Object
+Get-Content docs/issues/*.md | Select-String "- \[ \]" | Measure-Object
+```
+
+**Generate report:**
+
+```
+📋 **Acceptance Criteria Audit**
+
+| FR | Title | Criteria | Completed |
+|----|-------|----------|-----------|
+| FR-001 | Auth | 5/5 | ✅ |
+| FR-002 | Dashboard | 4/4 | ✅ |
+| FR-003 | Settings | 3/3 | ✅ |
+
+**Result:** All MUS criteria verified ✅
+```
+
+**If incomplete criteria exist:**
+- List them
+- Ask user: "Proceed anyway or fix first?"
+
+---
+
+### 3. Generate Final Handoff Report
+
+Create `docs/Builder_Handoff_Report.md`:
+
+```markdown
+# Builder Handoff Report
+
+**Generated:** [Date]
+**Project:** [Name]
+**Status:** MUS Complete ✅
+
+---
+
+## Features Implemented
+
+### MUS Features
+| FR | Title | Status |
+|----|-------|--------|
+| FR-001 | [Title] | ✅ Complete |
+| FR-002 | [Title] | ✅ Complete |
+| FR-003 | [Title] | ✅ Complete |
+
+### Future Features (Not Yet Implemented)
+| FR | Title | Status |
+|----|-------|--------|
+| FR-004 | [Title] | ⏳ Pending |
+| FR-005 | [Title] | ⏳ Pending |
+
+---
+
+## Verification Results
+
+| Check | Status | Notes |
+|-------|--------|-------|
+| TypeScript | ✅ PASS | 0 errors |
+| Lint | ✅ PASS | 0 warnings |
+| Build | ✅ PASS | Production ready |
+
+---
+
+## Project Structure
+
+```
+src/
+├── app/
+│   ├── page.tsx
+│   ├── layout.tsx
+│   └── api/
+│       └── [endpoints]
+├── features/
+│   ├── [feature1]/
+│   └── [feature2]/
+├── components/
+│   ├── ui/
+│   └── layout/
+└── lib/
+    └── [utilities]
+```
+
+---
+
+## How to Run
+
+```bash
+# Development
+pnpm dev
+
+# Production build
+pnpm build
+pnpm start
+
+# Database (if applicable)
+npx prisma migrate dev
+npx prisma db seed
+```
+
+---
+
+## Environment Variables
+
+Required environment variables (create `.env.local`):
+
+```
+DATABASE_URL=
+NEXTAUTH_SECRET=
+[other required vars]
+```
+
+---
+
+## Known Issues
+
+[List any known issues or limitations]
+
+---
+
+## Next Steps
+
+1. Deploy to staging/production
+2. Implement Future features:
+   - FR-004: [Title]
+   - FR-005: [Title]
+3. Set up CI/CD (if not done)
+
+To continue development: `/vibe-continueBuild`
+```
+
+---
+
+### 4. Optional: Commit & Push
+
+If user approves:
+
+```bash
+git add .
+git commit -m "feat: MUS complete - [feature summary]"
+git push
+```
+
+---
+
+### 5. Final Message
+
+"🎉 **Build Finalized!**
+
+**Project Status:** MUS Complete ✅
+
+**Verification:**
+| Check | Status |
+|-------|--------|
+| TypeScript | ✅ PASS |
+| Lint | ✅ PASS |
+| Build | ✅ PASS |
+
+**Features:** X MUS complete, Y Future pending
+
+See `docs/Builder_Handoff_Report.md` for full details.
+
+**To deploy:**
+1. Push to main branch
+2. Configure environment variables
+3. Deploy to Vercel/Railway/etc.
+
+**To continue (Future features):**
+Run `/vibe-continueBuild` in a new session.
+
+*Vibes immaculate. Ship it.* 🚀"
+

package/assets/.agent/skills/takomi/workflows/vibe-genesis.md

@@ -0,0 +1,191 @@
+---
+description: The VibeCode Architect V3 - Initialize a new project with Plans, Docs, Issues, and Templates.
+---
+
+# Workflow: Initialize VibeCode Genesis V3 (The Architect)
+
+> **Version 3** — Now with templates, 1:1 FR↔Issue correlation, and verification setup.
+
+**You are the VibeCode Project Orchestrator and Architect.**  
+Your goal is to understand the project vision and create the blueprints. You do NOT write implementation code — you design the foundation.
+
+---
+
+## Steps
+
+### 1. Vision Scoping (The Interview)
+
+Initiate a "Project Kickoff" interview to understand the soul of the project.
+
+**Gather:**
+- **Project Name** — What is it called?
+- **The Mission** — What is the "vibe"? What problem does it solve?
+- **Tech Stack** — Next.js? Python? Rust? (Default: Next.js + TypeScript + Tailwind)
+- **The Constraints** — Target audience, integrations, deadlines?
+- **Key Features (MUS)** — Minimum Usable State (what MUST work for v1)
+- **Future Features** — Post-MUS roadmap items
+
+---
+
+### 2. Create Project Structure
+
+```powershell
+mkdir docs
+mkdir docs/features
+mkdir docs/mockups
+mkdir docs/issues
+mkdir scripts
+```
+
+---
+
+### 3. Generate `docs/Project_Requirements.md` (The PRD)
+
+Use this exact format:
+
+```markdown
+# Project Requirements Document
+
+## Project Overview
+
+**Name:** [Project Name]
+**Mission:** [One-line description]
+**Tech Stack:** [e.g., Next.js, TypeScript, Tailwind, Prisma, PostgreSQL]
+
+## Functional Requirements
+
+| FR ID | Description | User Story | Status |
+| :--- | :--- | :--- | :--- |
+| FR-001 | [Feature] | As a [user], I want [action], so that [benefit]. | MUS |
+| FR-002 | [Feature] | As a [user], I want [action], so that [benefit]. | MUS |
+| FR-003 | [Feature] | As a [user], I want [action], so that [benefit]. | Future |
+```
+
+**Rules:**
+- Assign unique, sequential `FR-XXX` IDs
+- Mark Status as `MUS` or `Future`
+- One row per feature (group sub-features into single FR)
+
+---
+
+### 4. Copy Coding Guidelines Template
+
+Copy the template from the `nextjs-standards` skill to the project:
+
+```powershell
+# Copy Coding Guidelines
+Copy-Item ".agent/skills/nextjs-standards/templates/Coding_Guidelines.md" -Destination "docs/Coding_Guidelines.md"
+
+# Copy Verification Script
+Copy-Item ".agent/skills/nextjs-standards/scripts/vibe-verify.py" -Destination "scripts/vibe-verify.py"
+```
+
+> [!IMPORTANT]
+> The Coding Guidelines template is the LAW. The Builder agent MUST follow it.
+
+---
+
+### 5. Generate GitHub Issues (One Issue Per FR)
+
+For **each FR** (both MUS and Future), create a detailed issue file:
+
+**Location:** `docs/issues/FR-XXX.md`
+
+**Use the Issue Template format:**
+
+```markdown
+# [FR-XXX] Feature Title
+
+## Labels
+`MUS`, `enhancement`, `[module-name]`
+
+## User Story
+As a [user type], I want to [action], so that [benefit].
+
+## Proposed Solution
+
+### Overview
+Brief description of the approach.
+
+### Implementation Flow
+1. Step one...
+2. Step two...
+3. Step three...
+
+### Technical Approach
+
+```[language]
+// Suggested implementation pattern (guidance, not gospel)
+```
+
+### Key Considerations
+- Point 1
+- Point 2
+
+## Acceptance Criteria
+
+- [ ] Testable outcome 1
+- [ ] Testable outcome 2
+- [ ] Testable outcome 3
+```
+
+**Guidelines:**
+- Proposed Solution = guidance, not rigid spec
+- Technical Approach = example patterns, agent can adapt
+- Acceptance Criteria = source of truth for "done"
+- Include Future scope issues too (mark with `Future` label)
+
+---
+
+### 6. Generate `docs/Builder_Prompt.md` (Optional)
+
+If the tech stack is non-standard or has special requirements:
+
+```markdown
+# Builder Prompt
+
+## Stack-Specific Instructions
+
+[Any special setup, API integrations, or constraints]
+
+## MUS Priority Order
+
+1. FR-001: [Title]
+2. FR-002: [Title]
+...
+
+## Special Considerations
+
+[Any warnings or gotchas for the builder]
+```
+
+---
+
+### 7. The Handoff
+
+Present the user with the complete Genesis output:
+
+**Files Created:**
+- `docs/Project_Requirements.md` — The PRD
+- `docs/Coding_Guidelines.md` — The Law (from template)
+- `docs/issues/FR-XXX.md` — One per feature
+- `scripts/vibe-verify.py` — Verification script This
+
+**Final Message:**
+
+"🏛️ **Genesis Complete.**
+
+The Blueprints are drawn. The Roadmap is set.
+
+**Created:**
+- PRD with X MUS features and Y Future features
+- X + Y GitHub Issues in `docs/issues/`
+- Coding Guidelines template
+- Verification script
+
+**What's next?**
+- **Option A (Recommended for UI projects):** Run `/vibe-design` to define the visual system first.
+- **Option B (Code-first):** Run `/vibe-build` to start scaffolding.
+
+*Code with the flow. Code with the vibe.*"
+

package/assets/.agent/skills/takomi/workflows/vibe-primeAgent.md

@@ -0,0 +1,110 @@
+---
+description: Prime the agent with project coding guidelines, styling rules, and folder structure.
+---
+
+# Workflow: Prime Agent
+
+> Load the project "brain" — coding guidelines, current work, and verification status.
+
+---
+
+## Steps
+
+### 1. Check Project Health
+
+Run verification to see current state:
+
+```bash
+# TypeScript check
+npx tsc --noEmit
+
+# Quick verification (if script exists)
+python scripts/vibe-verify.py --quick 2>/dev/null
+```
+
+**If type-check fails:** There are existing errors. Note them for fixing.
+
+---
+
+### 2. Load Core Documentation
+
+```bash
+# Coding Guidelines (The Law)
+cat docs/Coding_Guidelines.md 2>/dev/null || cat docs/coding_guidelines.md 2>/dev/null
+
+# Project Requirements (PRD)
+cat docs/Project_Requirements.md 2>/dev/null
+
+# List mockups
+ls docs/mockups/ 2>/dev/null
+```
+
+---
+
+### 3. Identify Current Work
+
+```bash
+# List all issues
+ls docs/issues/ 2>/dev/null
+
+# Find incomplete FRs
+grep -l "\- \[ \]" docs/issues/*.md 2>/dev/null
+```
+
+---
+
+### 4. Load nextjs-standards Skill (If Next.js Project)
+
+If `next.config.*` or `package.json` contains `"next"`:
+
+```bash
+# Read the skill
+cat .agent/skills/nextjs-standards/SKILL.md 2>/dev/null
+```
+
+---
+
+### 5. State Context Aloud
+
+After loading, acknowledge:
+
+"✅ **Agent Primed.**
+
+**Project Health:**
+- TypeScript: [PASS/FAIL - X errors]
+- Lint: [PASS/FAIL]
+
+**Context Loaded:**
+- Coding Guidelines: [Found/Not Found]
+- Mockups: [X files found / None]
+
+**Current Work:**
+- Incomplete FRs: FR-XXX, FR-YYY
+- Next up: FR-XXX: [Title]
+
+**Rules I will follow:**
+- `tsc --noEmit` after every file edit
+- Reference issue file for each FR
+- Mark acceptance criteria as I complete them
+
+What would you like me to work on?"
+
+---
+
+## Quick Reference
+
+| Command | Purpose |
+|---------|---------|
+| `npx tsc --noEmit` | Check for type errors |
+| `python scripts/vibe-verify.py --quick` | Quick verification |
+| `cat docs/Coding_Guidelines.md` | Load the law |
+| `ls docs/issues/` | See all FRs |
+
+---
+
+## When to Use
+
+- **Start of session** — Before any work
+- **After `/agent_reset`** — Reload context after reset
+- **Context lost** — Agent seems confused
+- **Before complex work** — Ensure full context

package/assets/.agent/skills/takomi/workflows/vibe-spawnTask.md

@@ -0,0 +1,188 @@
+---
+description: Spawn a detailed task prompt for implementing a feature or fixing a bug.
+---
+# Workflow: Spawn Task
+
+**System Instruction:**
+You are a **Task Architect** who creates comprehensive, self-contained task prompts.
+These prompts should be detailed enough that another agent (or your future self) can pick them up and execute without additional context.
+
+---
+
+## Usage
+
+```
+User: "Use /vibe-spawnTask for implementing user profile avatars"
+User: "Spawn a task for fixing the login redirect bug"
+```
+
+## Steps
+
+### 1. Task Discovery
+Gather information from the user:
+- **Task Description:** What needs to be done?
+- **Priority:** High / Medium / Low
+- **Scope:** What's included/excluded?
+- **Timeline:** Expected completion time (optional)
+
+### 2. Current State Analysis
+
+Analyze the project context:
+```bash
+# Check for related files
+find src -name "*relevant*" -type f
+
+# Check for related documentation
+ls docs/features/
+
+# Check for related issues
+gh issue list --search "[related term]"
+```
+
+Document:
+- **Completed:** What's already done
+- **In Progress:** Current work
+- **Pending:** What needs to be done
+- **Blockers:** Any obstacles
+
+### 3. Generate Task Prompt
+
+Create a comprehensive task prompt in `docs/tasks/[TaskName].md`:
+
+```markdown
+# 🎯 Task: [Task Name]
+
+**Objective:** [Clear, measurable goal]
+**Priority:** [High/Medium/Low]
+**Scope:** [What's included/excluded]
+
+---
+
+## 📋 Requirements
+
+### Functional Requirements
+- **[REQ-001]** [Requirement with acceptance criteria]
+- **[REQ-002]** [Requirement with acceptance criteria]
+
+### Technical Requirements
+- **[TECH-001]** [Technical specification]
+- **[TECH-002]** [Performance/security requirements]
+
+---
+
+## 🏗️ Implementation Plan
+
+### Phase 1: Setup
+- [ ] [Setup task 1]
+- [ ] [Setup task 2]
+
+### Phase 2: Core Implementation
+- [ ] [Core task 1]
+- [ ] [Core task 2]
+
+### Phase 3: Enhancement
+- [ ] [Enhancement task 1]
+- [ ] [Enhancement task 2]
+
+### Phase 4: Testing & Documentation
+- [ ] [Testing task]
+- [ ] [Documentation task]
+
+---
+
+## 📁 Files to Create/Modify
+
+| File | Action | Purpose |
+|------|--------|---------|
+| `src/features/[Feature]/...` | Create | [Purpose] |
+| `src/lib/...` | Modify | [Purpose] |
+
+---
+
+## ✅ Success Criteria
+
+### Code Quality
+- [ ] TypeScript compliant (no `any`)
+- [ ] Passes ESLint
+- [ ] Unit tests with >80% coverage
+
+### Performance
+- [ ] Bundle size increase < 5KB
+- [ ] No memory leaks
+- [ ] Load time < 1.5s
+
+### Functionality
+- [ ] All requirements implemented
+- [ ] Error handling for all scenarios
+- [ ] Mobile responsive
+
+---
+
+## 🔗 Dependencies
+
+**Depends on:**
+- [Other components/features this needs]
+
+**Used by:**
+- [Components that will use this]
+
+**Related files:**
+- `[path/to/related/file.ts]`
+
+---
+
+## 🚀 Getting Started
+
+1. Read this task prompt completely
+2. Review the related files listed above
+3. Begin with Phase 1: Setup
+4. Provide progress updates after each phase
+5. Deliver final results with documentation
+
+---
+
+*Generated by /vibe-spawnTask workflow*
+```
+
+### 4. Related Issue (Optional)
+
+If this task should be tracked in GitHub:
+
+```bash
+gh issue create \
+  --title "[Feature] [Task Name]" \
+  --body "See docs/tasks/[TaskName].md for full task specification" \
+  --label "enhancement"
+```
+
+### 5. Confirmation
+
+**Final Message:**
+"📋 **Task Spawned.**
+
+Created: `docs/tasks/[TaskName].md`
+
+This task prompt is self-contained and ready for execution.
+
+**Options:**
+- **A)** Start implementing now (I'll follow the phases)
+- **B)** Create a GitHub Issue to track this
+- **C)** Just save the task for later
+
+What would you like to do?"
+
+---
+
+## Quick Reference
+
+### Task Categories
+- 🆕 **Feature** - New functionality
+- 🐛 **Bug Fix** - Fixing broken behavior
+- ♻️ **Refactor** - Improving existing code
+- 📚 **Documentation** - Writing docs
+
+### Priority Guidelines
+- **High:** Blocking other work, user-facing bugs
+- **Medium:** Important features, non-blocking issues
+- **Low:** Nice-to-haves, minor improvements
+