thanh-kit 2.5.4 → 2.5.5

package/templates/command-archive/review/codebase/parallel.md

@@ -0,0 +1,122 @@
+---
+description: ⚡⚡⚡ Ultrathink edge cases, then parallel verify with code-reviewers
+argument-hint: [scope-or-prompt]
+---
+
+**Ultrathink** to exhaustively list ALL potential edge cases, then dispatch parallel `code-reviewer` agents to verify: <scope>$ARGUMENTS</scope>
+
+**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
+
+## Workflow
+
+### 1. Ultrathink Edge Cases
+
+Main agent deeply analyzes the scope to LIST all potential edge cases FIRST:
+- Read `codebase-summary.md` for context
+- Use `/scout:ext` to find relevant files
+- **Think exhaustively** about what could go wrong:
+  - Null/undefined scenarios
+  - Boundary conditions (off-by-one, empty, max values)
+  - Error handling gaps
+  - Race conditions, async edge cases
+  - Input validation holes
+  - Security vulnerabilities
+  - Resource leaks
+  - Untested code paths
+
+**Output format:**
+```markdown
+## Edge Cases Identified
+
+### Category: [scope-area]
+1. [edge case description] → files: [file1, file2]
+2. [edge case description] → files: [file3]
+
+### Category: [another-area]
+1. [edge case description] → files: [file4, file5]
+```
+
+### 2. Categorize & Assign
+
+Group edge cases by similar scope for parallel verification:
+- Each category → one `code-reviewer` agent
+- Max 6 categories (merge small ones)
+- Each reviewer gets specific edge cases to VERIFY, not discover
+
+### 3. Parallel Verification
+
+Launch N `code-reviewer` subagents simultaneously:
+- Pass: category name, list of edge cases, relevant files
+- Task: **VERIFY** if each edge case is properly handled in code
+- Report: which edge cases are handled vs unhandled
+
+**Reviewer instruction:**
+```
+Verify these specific edge cases in the given files:
+[list of edge cases]
+
+For each, report:
+- ✅ Handled: [how it's handled]
+- ❌ Unhandled: [what's missing]
+- ⚠️ Partial: [what needs improvement]
+```
+
+### 4. Aggregate Results
+
+Collect all verification reports:
+```markdown
+## Edge Case Verification Report
+
+### Summary
+- Total edge cases: X
+- Handled: Y ✅
+- Unhandled: Z ❌
+- Partial: W ⚠️
+
+### Unhandled Edge Cases (Need Fix)
+| # | Edge Case | File | Status |
+|---|-----------|------|--------|
+| 1 | ...       | ...  | ❌     |
+
+### Partial Handling (Need Review)
+| # | Edge Case | File | Issue |
+|---|-----------|------|-------|
+| 1 | ...       | ...  | ...   |
+```
+
+### 5. Auto-Fix Pipeline
+
+**IF** unhandled/partial edge cases found:
+- Ask: "Found N unhandled edge cases. Fix with /fix --parallel? [Y/n]"
+- **IF yes:** Trigger `/fix --parallel` with unhandled list
+
+### 6. Final Report
+
+- Summary of verification
+- Ask: "Commit? [Y/n]" → use `git-manager`
+
+## Example
+
+```
+User: /review:codebase:parallel auth module
+
+1. Ultrathink → Lists 12 edge cases for auth:
+   - Empty password submission
+   - Token expiry during request
+   - Concurrent login attempts
+   - Invalid refresh token
+   ...
+
+2. Categorize → 3 groups:
+   - Login flow (4 cases)
+   - Token handling (5 cases)
+   - Session management (3 cases)
+
+3. Parallel → 3 code-reviewers verify simultaneously
+
+4. Aggregate → 8 handled, 3 unhandled, 1 partial
+
+5. Fix → User approves → /fix --parallel
+
+6. Final → Commit changes
+```

package/templates/command-archive/review/codebase.md

@@ -0,0 +1,49 @@
+---
+description: ⚡⚡⚡ Scan & analyze the codebase.
+argument-hint: [tasks-or-prompt]
+---
+
+Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+---
+
+## Role Responsibilities
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+---
+
+## Workflow:
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use 2 `researcher` subagents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+* Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+
+### Code Review
+
+* After finishing, use multiple `code-reviewer` subagents in parallel to review code. 
+* If there are any issues, duplicate code, or security vulnerabilities, ask main agent to improve the code and repeat the "Testing" process until all tests pass. 
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Plan
+* Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an improvement plan following the progressive disclosure structure:
+  - Create a directory using naming pattern from `## Naming` section.
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+
+**REMEMBER**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.

package/templates/command-archive/test/ui.md

@@ -0,0 +1,92 @@
+---
+description: '⚡⚡ Run UI tests on a website & generate a detailed report.'
+argument-hint: '[url] [options]'
+---
+
+Activate the chrome-devtools skill.
+
+## Purpose
+Run comprehensive UI tests on a website and generate a detailed report.
+
+## Arguments
+- $1: URL - The URL of the website to test
+- $2: OPTIONS - Optional test configuration (e.g., --headless, --mobile, --auth)
+
+## Testing Protected Routes (Authentication)
+
+For testing protected routes that require authentication, follow this workflow:
+
+### Step 1: User Manual Login
+Instruct the user to:
+1. Open the target site in their browser
+2. Log in manually with their credentials
+3. Open browser DevTools (F12) → Application tab → Cookies/Storage
+
+### Step 2: Extract Auth Credentials
+Ask the user to provide one of:
+- **Cookies**: Copy cookie values (name, value, domain)
+- **Access Token**: Copy JWT/Bearer token from localStorage or cookies
+- **Session Storage**: Copy relevant session keys
+
+### Step 3: Inject Authentication
+Use the `inject-auth.js` script to inject credentials before testing:
+
+```bash
+cd $SKILL_DIR  # .claude/skills/chrome-devtools/scripts
+
+# Option A: Inject cookies
+node inject-auth.js --url https://example.com --cookies '[{"name":"session","value":"abc123","domain":".example.com"}]'
+
+# Option B: Inject Bearer token
+node inject-auth.js --url https://example.com --token "Bearer eyJhbGciOi..." --header Authorization --token-key access_token
+
+# Option C: Inject localStorage
+node inject-auth.js --url https://example.com --local-storage '{"auth_token":"xyz","user_id":"123"}'
+
+# Combined (cookies + localStorage)
+node inject-auth.js --url https://example.com --cookies '[{"name":"session","value":"abc"}]' --local-storage '{"user":"data"}'
+```
+
+### Step 4: Run Tests
+After auth injection, the browser session persists. Run tests normally:
+
+```bash
+# Navigate and screenshot protected pages
+node navigate.js --url https://example.com/dashboard
+node screenshot.js --url https://example.com/profile --output profile.png
+
+# The auth session persists until --close true is used
+node screenshot.js --url https://example.com/settings --output settings.png --close true
+```
+
+### Auth Script Options
+- `--cookies '<json>'` - Inject cookies (JSON array)
+- `--token '<token>'` - Inject Bearer token
+- `--token-key '<key>'` - localStorage key for token (default: access_token)
+- `--header '<name>'` - Set HTTP header with token (e.g., Authorization)
+- `--local-storage '<json>'` - Inject localStorage items
+- `--session-storage '<json>'` - Inject sessionStorage items
+- `--reload true` - Reload page after injection
+- `--clear true` - Clear saved auth session
+
+## Workflow
+- Use `plan` skill to organize the test plan & report in the current project directory.
+- All the screenshots should be saved in the same report directory.
+- Browse $URL with the specified $OPTIONS, discover all pages, components, and endpoints.
+- Create a test plan based on the discovered structure
+- Use multiple `tester` subagents or tool calls in parallel to test all pages, forms, navigation, user flows, accessibility, functionalities, usability, responsive layouts, cross-browser compatibility, performance, security, seo, etc.
+- Use `ai-multimodal` to analyze all screenshots and visual elements.
+- Generate a comprehensive report in Markdown format, embedding all screenshots directly in the report.
+- Finally respond to the user with a concise summary of findings and recommendations.
+- Use `AskUserQuestion` tool to ask if user wants to preview the report with `/preview` slash command.
+
+## Output Requirements
+How to write reports:
+- Format: Use clear, structured Markdown with headers, lists, and code blocks where appropriate
+- Include the test results summary, key findings, and screenshot references
+- **IMPORTANT:** Ensure token efficiency while maintaining high quality.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**IMPORTANT**: **Do not** start implementing the fixes.
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.

package/templates/command-archive/test.md

@@ -0,0 +1,8 @@
+---
+description: ⚡ Run tests locally and analyze the summary report.
+---
+
+Use the `tester` subagent to run tests locally and analyze the summary report.
+
+**IMPORTANT**: **Do not** start implementing.
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.

package/templates/command-archive/use-mcp.md

@@ -0,0 +1,38 @@
+---
+description: Utilize tools of Model Context Protocol (MCP) servers
+argument-hint: [task]
+---
+Execute MCP operations via **Gemini CLI** to preserve context budget.
+
+## Execution Steps
+
+1. **Execute task via Gemini CLI** (using stdin pipe for MCP support):
+   ```bash
+   # IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
+   # Read model from .claude/.ck.json: gemini.model (default: gemini-3-flash-preview)
+   echo "$ARGUMENTS. Return JSON only per GEMINI.md instructions." | gemini -y -m <gemini.model>
+   ```
+
+2. **Fallback to mcp-manager subagent** (if Gemini CLI unavailable):
+   - Use `mcp-manager` subagent to discover and execute tools
+   - If the subagent got issues with the scripts of `mcp-management` skill, use `mcp-builder` skill to fix them
+   - **DO NOT** create ANY new scripts
+   - The subagent can only use MCP tools if any to achieve this task
+   - If the subagent can't find any suitable tools, just report it back to the main agent to move on to the next step
+
+## Important Notes
+
+- **MUST use stdin piping** - the deprecated `-p` flag skips MCP initialization
+- Use `-y` flag to auto-approve tool execution
+- **GEMINI.md auto-loaded**: Gemini CLI automatically loads `GEMINI.md` from project root, enforcing JSON-only response format
+- **Parseable output**: Responses are structured JSON: `{"server":"name","tool":"name","success":true,"result":<data>,"error":null}`
+
+## Anti-Pattern (DO NOT USE)
+
+```bash
+# BROKEN - deprecated -p flag skips MCP server connections!
+gemini -y -m <gemini.model> -p "..."
+
+# ALSO BROKEN - --model flag with -p
+gemini -y -p "..." --model gemini-3-flash-preview
+```

package/templates/command-archive/watzup.md

@@ -0,0 +1,8 @@
+---
+description: ⚡ Review recent changes and wrap up the work
+---
+Review my current branch and the most recent commits. 
+Provide a detailed summary of all changes, including what was modified, added, or removed. 
+Analyze the overall impact and quality of the changes.
+
+**IMPORTANT**: **Do not** start implementing.

package/templates/command-archive/worktree.md

@@ -0,0 +1,109 @@
+---
+description: 'Create isolated git worktree for parallel development'
+argument-hint: '[feature-description] OR [project] [feature] (monorepo)'
+---
+
+Create an isolated git worktree for parallel feature development.
+
+## Workflow
+
+### Step 1: Get Repo Info
+
+```bash
+node .claude/scripts/worktree.cjs info --json
+```
+
+Parse JSON response for: `repoType`, `baseBranch`, `projects`, `worktreeRoot`, `worktreeRootSource`.
+
+### Step 2: Detect Branch Prefix
+
+From user's description:
+- "fix", "bug", "error", "issue" → `fix`
+- "refactor", "restructure", "rewrite" → `refactor`
+- "docs", "documentation", "readme" → `docs`
+- "test", "spec", "coverage" → `test`
+- "chore", "cleanup", "deps" → `chore`
+- "perf", "performance", "optimize" → `perf`
+- Default → `feat`
+
+### Step 3: Convert to Slug
+
+"add authentication system" → `add-auth`
+"fix login bug" → `login-bug`
+Max 50 chars, kebab-case.
+
+### Step 4: Handle Monorepo
+
+If `repoType === "monorepo"` and project not specified, use AskUserQuestion:
+```javascript
+AskUserQuestion({
+  questions: [{
+    header: "Project",
+    question: "Which project for the worktree?",
+    options: projects.map(p => ({ label: p.name, description: p.path })),
+    multiSelect: false
+  }]
+})
+```
+
+### Step 5: Execute
+
+**Monorepo:**
+```bash
+node .claude/scripts/worktree.cjs create "<PROJECT>" "<SLUG>" --prefix <TYPE>
+```
+
+**Standalone:**
+```bash
+node .claude/scripts/worktree.cjs create "<SLUG>" --prefix <TYPE>
+```
+
+**Options:**
+- `--prefix` - Branch type: feat|fix|refactor|docs|test|chore|perf
+- `--worktree-root <path>` - Override default location (only if needed)
+- `--json` - JSON output
+- `--dry-run` - Preview
+
+### Step 6: Install Dependencies
+
+Based on project context, run in background:
+- `bun.lock` → `bun install`
+- `pnpm-lock.yaml` → `pnpm install`
+- `yarn.lock` → `yarn install`
+- `package-lock.json` → `npm install`
+- `poetry.lock` → `poetry install`
+- `requirements.txt` → `pip install -r requirements.txt`
+- `Cargo.toml` → `cargo build`
+- `go.mod` → `go mod download`
+
+## Commands
+
+| Command | Usage | Description |
+|---------|-------|-------------|
+| `create` | `create [project] <feature>` | Create worktree |
+| `remove` | `remove <name-or-path>` | Remove worktree |
+| `info` | `info` | Repo info with worktree location |
+| `list` | `list` | List worktrees |
+
+## Example
+
+```
+User: /worktree fix the login validation bug
+
+Claude: [Runs: node .claude/scripts/worktree.cjs info --json]
+        repoType: standalone
+        worktreeRoot: /home/user/worktrees
+        worktreeRootSource: sibling directory
+
+        [Prefix: fix, Slug: login-validation-bug]
+        [Runs: node .claude/scripts/worktree.cjs create "login-validation-bug" --prefix fix]
+
+Output: Worktree created at /home/user/worktrees/my-project-login-validation-bug
+```
+
+## Notes
+
+- Script auto-detects superproject, monorepo, and standalone repos
+- Default worktree location is smart: superproject > monorepo > sibling
+- Use `--worktree-root` only to override defaults
+- Env templates (`.env*.example`) auto-copied with `.example` suffix removed

package/templates/hooks/.logs/hook-log.jsonl

@@ -0,0 +1,26 @@
+{"ts":"2026-03-04T16:03:43.971Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:03:43.978Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:03:56.874Z","hook":"scout-block","tool":"Glob","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:03:56.880Z","hook":"scout-block","tool":"Bash","dur":7,"status":"block","exit":2,"error":""}
+{"ts":"2026-03-04T16:03:57.560Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:18.074Z","hook":"scout-block","tool":"Bash","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:18.082Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:26.893Z","hook":"scout-block","tool":"Bash","dur":7,"status":"block","exit":2,"error":""}
+{"ts":"2026-03-04T16:04:32.226Z","hook":"scout-block","tool":"Bash","dur":6,"status":"block","exit":2,"error":""}
+{"ts":"2026-03-04T16:04:32.234Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:44.444Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:44.445Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:56.769Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:04:56.773Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:11:33.817Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:11:40.915Z","hook":"scout-block","tool":"Bash","dur":5,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:13:15.301Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:13:22.848Z","hook":"scout-block","tool":"Glob","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:13:22.859Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:13:25.718Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:13:25.719Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:13:54.959Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:16:20.243Z","hook":"scout-block","tool":"Bash","dur":4,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:18:06.224Z","hook":"scout-block","tool":"Read","dur":3,"status":"ok","exit":0,"error":""}
+{"ts":"2026-03-04T16:18:27.165Z","hook":"scout-block","tool":"Glob","dur":3,"status":"block","exit":2,"error":""}
+{"ts":"2026-03-04T16:18:27.166Z","hook":"scout-block","tool":"Bash","dur":2,"status":"ok","exit":0,"error":""}

package/templates/settings.local.json

@@ -0,0 +1,13 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(cat:*)",
+      "Bash(ls:*)",
+      "Bash(test:*)",
+      "Bash(chmod:*)",
+      "Bash(./install.sh)",
+      "Bash(.venv/bin/pip install:*)",
+      "Bash(grep:*)"
+    ]
+  }
+}

package/templates/commands/bootstrap/auto/fast.md

@@ -1,111 +0,0 @@
----
-description: ⚡⚡⚡ Quickly bootstrap a new project automatically
-argument-hint: [user-requirements]
----
-
-**Think hard** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file: 
-
----
-
-## User's Objectives & Requirements
-
-<user-requirements>$ARGUMENTS</user-requirements>
-
----
-
-## Role Responsibilities
-
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- Your core mission is to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your subagents to implement the plan.
-- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
----
-
-## Your Approach
-
-1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-Follow strictly these following steps:
-
-**First thing first:** check if Git has been initialized, if not, use `git-manager` subagent to quickly initialize it (use `main` branch).
-
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-
-### Research & Planning: Tech Stack, Wireframe & Design
-
-1. **Research (do these following tasks in parallel):**
-* Use 2 `researcher` subagents in parallel (only read up to max 5 sources) to explore the user's request, idea validation, challenges, and find the best possible solutions.
-* Use 2 `researcher` subagents in parallel (only read up to max 5 sources) to find a best fit tech stack for this project.
-* Use 2 `researcher` subagents in parallel (only read up to max 5 sources) to create a design plan that follows the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
-   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
-   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-2. **Planning (do these following tasks one after another):**
-* Use `ui-ux-designer` subagent to analyze the research results and create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
-* If there are no logo provided, use `ai-multimodal` skill to generate a logo.
-* Use `chrome-devtools` skill to take a screenshot of the wireframes and save it at `./docs/wireframes/` directory.
-* Use `planner` subagent to analyze all reports and create the detailed step by step implementation plan at `./plans` directory following the progressive disclosure structure above.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Implementation
-
-* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `./plans` directory.
-* Use `ui-ux-designer` subagent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `ai-multimodal` skill to generate the assets.
-  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
-  * Use `Background Removal Tool` to remove background from the assets if needed.
-  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
-  * Use `imagemagick` skill to crop or resize the assets if needed.
-* Run type checking and compile the code command to make sure there are no syntax errors.
-
-### Testing
-
-* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-* Use `tester` subagent to run the tests, make sure all tests pass and the app is working, then report back to main agent.
-* If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them. 
-* Repeat the process until all tests pass or no more issues are reported. 
-* **Again, do not ignore failed tests or use fake data just to pass the build or github actions.**
-
-### Code Review
-
-* After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
-* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Documentation
-
-* Use `docs-manager` subagent to update the docs if needed.
-  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
-  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
-  * Create/update `./docs/code-standards.md` file.
-  * Create/update `./docs/system-architecture.md` file.
-  * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-* Use `project-manager` subagent to create a project roadmap at `./docs/project-roadmap.md` file.
-
-### Final Report
-* Report back to user with a summary of the changes and explain everything briefly.
-* Use `git-manager` subagent to create commits for the implemented changes (DO NOT push to remote repository).
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-
-### Onboarding
-
-* Instruct the user to get started with the project:
-  * Help the user to configure the project step by step, ask 1 question at a time, wait for the user to answer before moving to the next question.
-  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
-
-

package/templates/commands/bootstrap/auto/parallel.md

@@ -1,66 +0,0 @@
----
-description: ⚡⚡⚡⚡⚡ Bootstrap project with parallel execution
-argument-hint: [user-requirements]
----
-
-**Ultrathink parallel** to bootstrap: <user-requirements>$ARGUMENTS</user-requirements>
-
-**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
-**YAGNI, KISS, DRY** principles apply.
-
-## Workflow
-
-### 1. Git Init
-- Check if Git initialized, if not: use `git-manager` (main branch)
-
-### 2. Research
-- Use max 2 `researcher` agents in parallel
-- Explore requirements, validation, challenges, solutions
-- Keep reports ≤150 lines
-
-### 3. Tech Stack
-- Use `planner` + multiple `researcher` agents in parallel for best fit tech stack
-- Write to `./docs` directory (≤150 lines)
-
-### 4. Wireframe & Design
-- Use `ui-ux-designer` + `researcher` agents in parallel
-- Research: style, trends, fonts, colors, spacing, positions
-- Describe assets for `ai-multimodal` generation
-- Create design guidelines at `./docs/design-guidelines.md`
-- Generate wireframes HTML at `./docs/wireframe`
-- Generate logo with `ai-multimodal` if needed
-- Screenshot with `chrome-devtools` → save to `./docs/wireframes/`
-- Ask user to approve (repeat if rejected)
-
-### 5. Parallel Planning & Implementation
-- Trigger `/plan:parallel <detailed-instruction>` for parallel-executable plan
-- Read `plan.md` for dependency graph and execution strategy
-- Launch multiple `fullstack-developer` agents in PARALLEL for concurrent phases
-  - Pass: phase file path, environment info
-- Use `ui-ux-designer` for frontend (generate/analyze assets with `ai-multimodal`, edit with `imagemagick`)
-- Run type checking after implementation
-
-### 6. Testing
-- Write real tests (NO fake data/mocks)
-- Use `tester` subagent
-- If fail: `debugger` → fix → repeat
-
-### 7. Code Review
-- Use `code-reviewer`
-- If critical: fix → retest → repeat
-
-### 8. Documentation
-- Use `docs-manager` to create/update:
-  - `./docs/README.md` (≤300 lines)
-  - `./docs/project-overview-pdr.md`
-  - `./docs/code-standards.md`
-  - `./docs/system-architecture.md`
-- Use `project-manager` for `./docs/project-roadmap.md`
-
-### 9. Onboarding
-- Guide user to get started (1 question at a time)
-- Help configure (API keys, env vars, etc.)
-
-### 10. Final Report
-- Summary, guide, next steps
-- Ask to commit (use `git-manager` if yes)