@relipa/ai-flow-kit 0.0.1

package/bin/aiflow.js

@@ -0,0 +1,178 @@
+#!/usr/bin/env node
+
+const { program } = require('commander');
+const chalk = require('chalk');
+const packageJson = require('../package.json');
+const initCommand     = require('../scripts/init');
+const updateCommand   = require('../scripts/update');
+const doctorCommand   = require('../scripts/doctor');
+const useCommand      = require('../scripts/use');
+const TaskDetector    = require('../scripts/detect');
+const validateCommand = require('../scripts/validate');
+const memoryCommand   = require('../scripts/memory');
+const contextCommand  = require('../scripts/context');
+const promptCommand   = require('../scripts/prompt');
+const removeCommand   = require('../scripts/remove');
+const guideCommand    = require('../scripts/guide');
+
+program
+    .version(packageJson.version)
+    .description('AI Flow Kit CLI - AI-powered development workflows for teams');
+
+// ── init ──────────────────────────────────────────────────────
+program
+    .command('init')
+    .description('Initialize AI Flow Kit in your project')
+    .option('-f, --framework <types>', 'framework(s), comma-separated (e.g. spring-boot,reactjs)')
+    .option('-a, --adapter <types>', 'adapter(s), comma-separated (e.g. backlog,jira)')
+    .action((options) => {
+        options.frameworks = options.framework
+            ? options.framework.split(',').map(s => s.trim()).filter(Boolean)
+            : [];
+        options.adapters = options.adapter
+            ? options.adapter.split(',').map(s => s.trim()).filter(Boolean)
+            : [];
+        initCommand(options);
+    });
+
+// ── use ───────────────────────────────────────────────────────
+program
+    .command('use [target]')
+    .description('Load context from ticket, version, or file')
+    .option('-m, --manual', 'manual context entry')
+    .option('-f, --file <path>', 'load from file')
+    .option('-s, --save <name>', 'save as named context')
+    .option('--with-comments', 'load all comments (default: description only)')
+    .option('--comments-last <n>', 'load only the last N comments', parseInt)
+    .option('--comments-from <n>', 'load comments from index N onward (0-based)', parseInt)
+    .action((target, options) => {
+        useCommand(target, options);
+    });
+
+// ── prompt ────────────────────────────────────────────────────
+program
+    .command('prompt [type]')
+    .description('Generate AI prompt with context and rules')
+    .option('-l, --list', 'list available prompt types')
+    .option('-o, --output <file>', 'save to file')
+    .option('--lang <lang>', 'language: english (default) or vietnamese')
+    .option('--detail <level>', 'detail level: minimal | standard (default) | comprehensive')
+    .action((type, options) => {
+        promptCommand(type, options);
+    });
+
+// ── detect ────────────────────────────────────────────────────
+program
+    .command('detect [description]')
+    .description('Auto-detect task type from description')
+    .option('-v, --verbose', 'show detection details')
+    .option('-t, --threshold <number>', 'confidence threshold (0-100)')
+    .action((description, options) => {
+        const detector = new TaskDetector();
+        const threshold = options.threshold ? parseInt(options.threshold) / 100 : 0.8;
+        const result = detector.detect(description, threshold);
+        console.log(chalk.cyan('\nTask Detection Results:\n'));
+        console.log(detector.formatOutput(result, options.verbose));
+    });
+
+// ── context ───────────────────────────────────────────────────
+program
+    .command('context [action]')
+    .description('Manage task contexts (list|show|save <name>|clear)')
+    .option('-s, --save <name>', 'save current context with name')
+    .option('--load <name>', 'load saved context by name')
+    .option('-d, --delete <name>', 'delete saved context')
+    .option('--clear', 'clear all saved contexts')
+    .option('--show', 'show current context')
+    .action((action, options) => {
+        contextCommand(action, options);
+    });
+
+// ── validate ──────────────────────────────────────────────────
+program
+    .command('validate <file>')
+    .description('Validate output against team rules')
+    .option('-r, --ruleset <set>', 'rule set: default | strict | lenient', 'default')
+    .option('-v, --verbose', 'detailed report')
+    .option('--fix', 'auto-fix trailing whitespace')
+    .action((file, options) => {
+        validateCommand(file, {
+            ruleset: options.ruleset,
+            verbose: options.verbose,
+            fix: options.fix
+        });
+    });
+
+// ── memory ────────────────────────────────────────────────────
+// Sub-commands to avoid the ambiguous "memory <action> --save key" pattern
+const memCmd = program.command('memory').description('Manage team knowledge and memory');
+
+memCmd
+    .command('save <key> <value>')
+    .description('Save a memory entry')
+    .action((key, value) => memoryCommand('save', { key, value }));
+
+memCmd
+    .command('get <key>')
+    .description('Retrieve a memory entry')
+    .action((key) => memoryCommand('get', { key }));
+
+memCmd
+    .command('list')
+    .description('List all memories')
+    .action(() => memoryCommand('list'));
+
+memCmd
+    .command('search <query>')
+    .description('Search memories by keyword')
+    .action((query) => memoryCommand('search', { query }));
+
+memCmd
+    .command('delete <key>')
+    .description('Delete a memory entry')
+    .action((key) => memoryCommand('delete', { key }));
+
+memCmd
+    .command('clear')
+    .description('Clear all memories')
+    .action(() => memoryCommand('clear'));
+
+// ── guide ─────────────────────────────────────────────────────
+program
+    .command('guide')
+    .description('Show quickstart guide, architecture, and command reference')
+    .option('--flow', 'show architecture & flow diagram only')
+    .option('--commands', 'show command reference only')
+    .action((options) => {
+        guideCommand(options);
+    });
+
+// ── remove ────────────────────────────────────────────────────
+program
+    .command('remove')
+    .description('Remove ai-flow-kit from project, a cached version, or uninstall globally')
+    .option('--version <ver>', 'remove a specific cached version from .aiflow/versions/')
+    .option('--global', 'uninstall the global npm package (removes `aiflow` command)')
+    .action((options) => {
+        removeCommand(options);
+    });
+
+// ── update ────────────────────────────────────────────────────
+program
+    .command('update')
+    .description('Update to latest version')
+    .option('--force', 'force update even if already on latest')
+    .action((options) => {
+        updateCommand(options);
+    });
+
+// ── doctor ────────────────────────────────────────────────────
+program
+    .command('doctor')
+    .description('Health check of AI Flow Kit setup')
+    .option('-v, --verbose', 'detailed output')
+    .action(() => {
+        doctorCommand();
+    });
+
+program.parse(process.argv);

package/custom/mcp-presets/README.md

@@ -0,0 +1,138 @@
+# MCP Presets
+
+Pre-configured MCP (Model Context Protocol) adapters for various project management and collaboration tools.
+
+## Available Presets
+
+### Jira (`jira.json`)
+
+Connect to Atlassian Jira for loading issues and context.
+
+**Setup:**
+```bash
+aiflow init --adapter jira
+```
+
+**Required Environment Variables:**
+- `JIRA_API_TOKEN` — Your Jira API token
+- `JIRA_EMAIL` — Your Jira account email
+- `JIRA_DOMAIN` — Your Jira domain (e.g., "company" in company.atlassian.net)
+
+**Get API Token:**
+1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
+2. Create new API token
+3. Copy the token
+
+**Usage:**
+```bash
+aiflow use JIRA-123
+# Loads issue JIRA-123 from your Jira instance
+```
+
+### Backlog (`backlog.json`)
+
+Connect to Nulab Backlog for loading tasks and context.
+
+**Setup:**
+```bash
+aiflow init --adapter backlog
+```
+
+**Required Environment Variables:**
+- `BACKLOG_API_KEY` — Your Backlog API key
+- `BACKLOG_SPACE_KEY` — Your Backlog space key
+
+**Get API Key:**
+1. Log in to Backlog
+2. Go to Personal Settings → API Settings
+3. Generate new API token
+
+**Usage:**
+```bash
+aiflow use BACKLOG-456
+# Loads task from your Backlog instance
+```
+
+### Google Sheets (`google-sheets.json`)
+
+Connect to Google Sheets for loading task context.
+
+**Setup:**
+```bash
+aiflow init --adapter google-sheets
+```
+
+**Required Environment Variables:**
+- `GOOGLE_SHEETS_CREDS` — Path to service account JSON
+
+**Get Credentials:**
+1. Create Google Cloud project
+2. Enable Sheets API
+3. Create service account
+4. Download JSON credentials
+5. Store securely and set path
+
+**Usage:**
+```bash
+aiflow use SHEET-A1:D5
+# Loads data from Google Sheet
+```
+
+## Creating Custom Presets
+
+To add a new MCP adapter:
+
+1. Create `<adapter-name>.json`:
+
+```json
+{
+  "mcpServers": {
+    "<adapter-name>": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-<adapter-name>"
+      ],
+      "env": {
+        "ENV_VAR_1": "{{PLACEHOLDER}}",
+        "ENV_VAR_2": "{{PLACEHOLDER}}"
+      }
+    }
+  }
+}
+```
+
+2. Document in this README
+
+3. Users can install with:
+```bash
+aiflow init --adapter <adapter-name>
+```
+
+## Validators
+
+Each preset should be validated during `aiflow init`:
+
+- ✓ Environment variables set
+- ✓ API connectivity working
+- ✓ Proper permissions configured
+
+## Best Practices
+
+1. **Use placeholders** — {{VAR_NAME}} for env variables
+2. **Document setup** — Include step-by-step guide
+3. **Provide examples** — Show usage patterns
+4. **Handle errors** — Clear error messages if setup fails
+5. **Support multiple instances** — Allow team variations
+
+## Security
+
+- **Never commit credentials** — Use environment variables
+- **Use secure storage** — Store API tokens securely
+- **Rotate tokens** — Regularly update API tokens
+- **Restrict permissions** — Use minimal required permissions
+- **Audit access** — Monitor who accesses what
+
+---
+
+For more info: See [Configuration Guide](../../docs/configuration.md)

package/custom/mcp-presets/backlog.json

@@ -0,0 +1,15 @@
+{
+  "mcpServers": {
+    "backlog": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-backlog"
+      ],
+      "env": {
+        "BACKLOG_API_KEY": "{{BACKLOG_API_KEY}}",
+        "BACKLOG_SPACE_KEY": "{{BACKLOG_SPACE_KEY}}"
+      }
+    }
+  }
+}

package/custom/mcp-presets/figma.json

@@ -0,0 +1,15 @@
+{
+  "mcpServers": {
+    "figma": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "figma-developer-mcp",
+        "--stdio"
+      ],
+      "env": {
+        "FIGMA_API_TOKEN": "{{FIGMA_API_TOKEN}}"
+      }
+    }
+  }
+}

package/custom/mcp-presets/google-sheets.json

@@ -0,0 +1,14 @@
+{
+  "mcpServers": {
+    "google-sheets": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-google-sheets"
+      ],
+      "env": {
+        "GOOGLE_CREDENTIALS_JSON": "{{GOOGLE_CREDENTIALS_JSON}}"
+      }
+    }
+  }
+}

package/custom/mcp-presets/jira.json

@@ -0,0 +1,16 @@
+{
+  "mcpServers": {
+    "jira": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-jira"
+      ],
+      "env": {
+        "JIRA_API_TOKEN": "{{JIRA_API_TOKEN}}",
+        "JIRA_EMAIL": "{{JIRA_EMAIL}}",
+        "JIRA_DOMAIN": "{{JIRA_DOMAIN}}"
+      }
+    }
+  }
+}

package/custom/prompts/bug-fix.md

@@ -0,0 +1,149 @@
+# Bug Fix Investigation Prompt
+
+## 📋 Context
+
+**Title:** {{TITLE}}
+
+**Description:**
+{{DESCRIPTION}}
+
+**Reproduction Steps:**
+{{STEPS}}
+
+**Expected Behavior:**
+{{EXPECTED}}
+
+**Actual Behavior:**
+{{ACTUAL}}
+
+**Impact:** {{IMPACT}}
+
+---
+
+## 🎯 Your Task
+
+Investigate and fix this bug following the structured approach below.
+
+### Step 1: Understand the Error
+
+- Read and understand the error message completely
+- Identify which feature or component is affected
+- Check error logs, stack traces, or user reports
+- Understand the business impact
+
+### Step 2: Trace the Data Flow
+
+Start from where the user interacts with the system and trace through your application:
+
+```
+Controller/Route (receives request)
+    ↓
+Service/Action (processes business logic)
+    ↓
+Model/Repository (database operations)
+    ↓
+External APIs (if applicable)
+```
+
+Add logging at each step if needed to understand variable values:
+- What data enters the function?
+- What transformations happen?
+- What data is returned or saved?
+
+### Step 3: Check Git History
+
+Use Git to understand the context:
+
+```bash
+# Find suspicious changes
+git blame <file>
+
+# See full history of changes
+git log -p <file>
+
+# Check recent commits
+git log --oneline -20
+```
+
+Look for:
+- Recent changes that could have broken this
+- Why code was changed this way
+- Dependencies on other changes
+
+### Step 4: Identify Root Cause
+
+List the root cause with:
+- Exact location in code (file:line)
+- What is wrong
+- Why it's wrong
+- Impact on the system
+
+### Step 5: Propose Solution
+
+Suggest the best fix:
+- Minimal change (only fix the bug, don't refactor)
+- No breaking changes to other features
+- Consider performance and security
+- Add tests to verify the fix
+
+### Step 6: Test the Fix
+
+```bash
+# Run specific test
+npm test -- tests/[feature].test.js
+
+# Run all tests
+npm test
+
+# Check for linting issues
+npm run lint
+```
+
+Verify:
+- ✅ The bug is fixed
+- ✅ No other tests break
+- ✅ Code style compliant
+- ✅ No performance regression
+
+---
+
+## 📚 Team Framework Rules
+
+{{FRAMEWORK_RULES}}
+
+---
+
+## 📏 Team Rules & Standards
+
+{{TEAM_RULES}}
+
+---
+
+## ✅ Success Criteria
+
+- [ ] Root cause identified with code reference
+- [ ] Fix implemented and tested
+- [ ] All tests passing
+- [ ] No breaking changes
+- [ ] Code follows team standards
+- [ ] Solution is minimal and focused
+
+---
+
+## 💡 Tips
+
+- **Don't guess** → Investigate systematically
+- **Don't break things** → Verify no side effects
+- **Don't over-engineer** → Keep fix minimal
+- **Do test thoroughly** → Verify all scenarios
+- **Do document** → Explain why you fixed it this way
+
+---
+
+**Remember:** A good bug fix is one that:
+1. Solves the problem completely
+2. Doesn't create new problems
+3. Is understood and maintainable
+4. Is tested and verified
+
+Start your investigation now! 🔍