@relipa/ai-flow-kit 0.0.4-beta.2 → 0.0.4

package/docs/developer-overview.md

@@ -1,126 +1,126 @@
-# AI Flow Kit — Developer Rollout Guide
-
-Welcome to the **AI Flow Kit**! This guide is designed to get you up and running with our standardized AI development workflow.
-
-## 1. What is AI Flow Kit?
-
-It's a "Zero-Config" framework for AI-assisted development. It automatically:
-- Pulls ticket context (requirements, comments) from Backlog/Jira.
-- Orchestrates a **5-Gate Workflow** (Analyze → Plan → Code → Review → PR).
-- Enforces team coding standards and architecture rules.
-- Synchronizes state across different AI tools (Claude, Cursor, Gemini).
-
----
-
-## 2. Prerequisites
-
-Before starting, ensure you have:
-1. **Node.js** (v18 or higher).
-2. **AI Tool(s)**:
-   - **Claude Code CLI** (Recommended for analysis and heavy tasks).
-   - **Cursor AI** (Recommended for coding and UI work).
-   - **Gemini CLI** or **GitHub Copilot** (Alternative options).
-
----
-
-## 3. Installation
-
-Run this command to install the CLI tool globally:
-
-```bash
-# Stable version
-npm install -g @relipa/ai-flow-kit
-
-# Beta version (recommend for newest features)
-npm install -g @relipa/ai-flow-kit@beta
-
-# Verification
-aiflow --version
-
-# Uninstall
-npm uninstall -g @relipa/ai-flow-kit
-
----
-
-## 4. First-time Setup
-
-In your project root, run:
-
-```bash
-aiflow init --framework [your-framework] --adapter [backlog/jira]
-```
-*Example: `aiflow init --framework nestjs --adapter backlog`*
-
-**What this does:**
-1. Verifies your API keys.
-2. Creates instruction files: `CLAUDE.md`, `.cursorrules`, `GEMINI.md`.
-3. Installs "Superpowers" skills.
-
----
-
-## 5. Daily Task Workflow (The 5 Gates)
-
-### Step 1: Start a Task
-Load the ticket context from your issue tracker:
-```bash
-aiflow use PROJ-33
-```
-
-### Step 2: Open your AI Tool
-- **Claude Code**: Type `claude`. The AI will automatically start **Gate 1**.
-- **Cursor**: Just start chatting with Cursor. It will detect the active ticket and start analyzing.
-
-### Step 3: Follow the Gates
-The AI *must* pass each gate in order. You act as the **Reviewer**.
-
-1. **⛩️ Gate 1: Requirement Analysis**
-   - AI reads code + ticket.
-   - AI outputs `plan/PROJ-33/requirement.md`.
-   - **Your Action**: Read the doc. If OK, type `APPROVED`.
-
-2. **⛩️ Gate 2: Implementation Plan**
-   - AI creates a step-by-step TDD plan.
-   - **Your Action**: Type `APPROVED` to start coding.
-
-3. **⛩️ Gate 3: Coding (TDD)**
-   - AI writes tests first, then code.
-   - **Your Action**: Monitor.
-
-4. **⛩️ Gate 4: Self-Review**
-   - AI verifies tests and checks a review-checklist.
-   - **Your Action**: Review the final diff. If OK, type `APPROVED`.
-
-5. **⛩️ Gate 5: Pull Request**
-   - AI helps you write a detailed PR description.
-   - **Your Action**: Create the PR and ask for a peer review.
-
----
-
-## 6. Switching AI Tools Mid-Task
-
-You can switch tools at any time because the "brain" (the State) is stored in your project files.
-
-**Example Scenario:**
-1. Use **Claude Code CLI** for **Gate 1** (Analysis) because it's great at exploring many files.
-2. Once you type `APPROVED`, close Claude.
-3. Open **Cursor** for **Gate 3** (Coding) to take advantage of its excellent editor integration. Cursor will see you've already finished the analysis and will continue from the plan.
-
----
-
-## 7. Best Practices
-
-- **One question at a time**: If the AI asks 5 questions, answer them one by one or ignore the irrelevant ones.
-- **Small commits**: Let the AI commit frequently (default behavior).
-- **Be the Pilot**: The AI is your co-pilot. If its solution looks over-engineered, tell it: *"Simplify this by using [X] pattern"*.
-
----
-
-## 8. Troubleshooting
-
-- **AI is stuck**: Type `reset context` or use `aiflow doctor` to check setup.
-- **Credentials fail**: Re-run `aiflow init --adapter backlog` to update keys.
-- **Rules not followed**: Remind the AI: *"Follow the rules in CLAUDE.md"*.
-
----
-
-**Happy Coding!** สำหรับรายละเอียดเชิงลึก โปรดดู [AIFLOW.md](../AIFLOW.md).
+# AI Flow Kit — Developer Rollout Guide
+
+Welcome to the **AI Flow Kit**! This guide is designed to get you up and running with our standardized AI development workflow.
+
+## 1. What is AI Flow Kit?
+
+It's a "Zero-Config" framework for AI-assisted development. It automatically:
+- Pulls ticket context (requirements, comments) from Backlog/Jira.
+- Orchestrates a **5-Gate Workflow** (Analyze → Plan → Code → Review → PR).
+- Enforces team coding standards and architecture rules.
+- Synchronizes state across different AI tools (Claude, Cursor, Gemini).
+
+---
+
+## 2. Prerequisites
+
+Before starting, ensure you have:
+1. **Node.js** (v18 or higher).
+2. **AI Tool(s)**:
+   - **Claude Code CLI** (Recommended for analysis and heavy tasks).
+   - **Cursor AI** (Recommended for coding and UI work).
+   - **Gemini CLI** or **GitHub Copilot** (Alternative options).
+
+---
+
+## 3. Installation
+
+Run this command to install the CLI tool globally:
+
+```bash
+# Stable version
+npm install -g @relipa/ai-flow-kit
+
+# Beta version (recommend for newest features)
+npm install -g @relipa/ai-flow-kit@beta
+
+# Verification
+aiflow --version
+
+# Uninstall
+npm uninstall -g @relipa/ai-flow-kit
+
+---
+
+## 4. First-time Setup
+
+In your project root, run:
+
+```bash
+aiflow init --framework [your-framework] --adapter [backlog/jira]
+```
+*Example: `aiflow init --framework nestjs --adapter backlog`*
+
+**What this does:**
+1. Verifies your API keys.
+2. Creates instruction files: `CLAUDE.md`, `.cursorrules`, `GEMINI.md`.
+3. Installs "Superpowers" skills.
+
+---
+
+## 5. Daily Task Workflow (The 5 Gates)
+
+### Step 1: Start a Task
+Load the ticket context from your issue tracker:
+```bash
+aiflow use PROJ-33
+```
+
+### Step 2: Open your AI Tool
+- **Claude Code**: Type `claude`. The AI will automatically start **Gate 1**.
+- **Cursor**: Just start chatting with Cursor. It will detect the active ticket and start analyzing.
+
+### Step 3: Follow the Gates
+The AI *must* pass each gate in order. You act as the **Reviewer**.
+
+1. **⛩️ Gate 1: Requirement Analysis**
+   - AI reads code + ticket.
+   - AI outputs `plan/PROJ-33/requirement.md`.
+   - **Your Action**: Read the doc. If OK, type `APPROVED`.
+
+2. **⛩️ Gate 2: Implementation Plan**
+   - AI creates a step-by-step TDD plan.
+   - **Your Action**: Type `APPROVED` to start coding.
+
+3. **⛩️ Gate 3: Coding (TDD)**
+   - AI writes tests first, then code.
+   - **Your Action**: Monitor.
+
+4. **⛩️ Gate 4: Self-Review**
+   - AI verifies tests and checks a review-checklist.
+   - **Your Action**: Review the final diff. If OK, type `APPROVED`.
+
+5. **⛩️ Gate 5: Pull Request**
+   - AI helps you write a detailed PR description.
+   - **Your Action**: Create the PR and ask for a peer review.
+
+---
+
+## 6. Switching AI Tools Mid-Task
+
+You can switch tools at any time because the "brain" (the State) is stored in your project files.
+
+**Example Scenario:**
+1. Use **Claude Code CLI** for **Gate 1** (Analysis) because it's great at exploring many files.
+2. Once you type `APPROVED`, close Claude.
+3. Open **Cursor** for **Gate 3** (Coding) to take advantage of its excellent editor integration. Cursor will see you've already finished the analysis and will continue from the plan.
+
+---
+
+## 7. Best Practices
+
+- **One question at a time**: If the AI asks 5 questions, answer them one by one or ignore the irrelevant ones.
+- **Small commits**: Let the AI commit frequently (default behavior).
+- **Be the Pilot**: The AI is your co-pilot. If its solution looks over-engineered, tell it: *"Simplify this by using [X] pattern"*.
+
+---
+
+## 8. Troubleshooting
+
+- **AI is stuck**: Type `reset context` or use `aiflow doctor` to check setup.
+- **Credentials fail**: Re-run `aiflow init --adapter backlog` to update keys.
+- **Rules not followed**: Remind the AI: *"Follow the rules in CLAUDE.md"*.
+
+---
+
+**Happy Coding!** สำหรับรายละเอียดเชิงลึก โปรดดู [AIFLOW.md](../AIFLOW.md).

package/docs/troubleshooting.md

@@ -171,7 +171,7 @@ Options are overridden in this order:
 
 ```bash
 # Check context exists
-ls .claude/context/
+ls .aiflow/context/
 
 # If missing, reload context
 aiflow use JIRA-123  # Reload from ticket

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@relipa/ai-flow-kit",
-  "version": "0.0.4-beta.2",
+  "version": "0.0.4",
   "description": "All-in-one AI Flow Kit for team development with Claude AI - skills, templates, and MCP adapters",
   "author": "Relipa AI Team",
   "publishConfig": {
@@ -20,13 +20,7 @@
     "upstream",
     "docs",
     "package.json",
-    "index.js",
-    "README.md",
-    "QUICK_START.md",
-    "AIFLOW.md",
-    "CONTRIBUTING.md",
-    "IMPLEMENTATION_SUMMARY.md",
-    "CHANGELOG.md"
+    "index.js"
   ],
   "keywords": [
     "ai",

package/scripts/hooks/session-start.js

@@ -14,7 +14,7 @@ const path = require('path');
 // Project root is 3 levels up
 const projectRoot = path.resolve(__dirname, '..', '..', '..');
 const skillPath = path.join(projectRoot, '.claude', 'skills', 'using-superpowers', 'SKILL.md');
-const contextPath = path.join(projectRoot, '.claude', 'context', 'current.json');
+const contextPath = path.join(projectRoot, '.aiflow', 'context', 'current.json');
 
 // ── 1. Load superpowers skill ──────────────────────────────────
 let skillContent = '';
@@ -138,4 +138,4 @@ function buildContextPrompt(ctx) {
     lines.push('</ACTIVE_TASK>');
 
     return lines.join('\n');
-}
+}