thanh-kit 2.5.0

package/templates/commands/skill/plan.md

@@ -0,0 +1,45 @@
+---
+description: Plan to create a new agent skill
+argument-hint: [skill-name] [prompt]
+---
+
+Think harder.
+First: Activate `skill-creator` and `claude-code` skills.
+Use `docs-seeker` skills to search for documentation if needed.
+Employ `sequential-thinking` or `problem-solving` skills for complex problem-solving that requires structured analysis
+Finally, when creating a plan, activate `planning` skill.
+
+## Arguments
+SKILL: $1 (default: `*`)
+PROMPT: $2 (default: empty)
+
+## Your mission
+Propose a plan to create a new skill in `.claude/skills/${SKILL}` directory. 
+When you finish, ask user to review your plan:
+- If the user approve: Write down a plan follow "Output Requirements", then ask user if they want to start implementing.
+- If the user reject: Revise the plan or ask more questions to clarify more about the user's request (ask one question at the time), then repeat the review process.
+
+## Additional instructions
+<additional-instructions>$PROMPT</additional-instructions>
+
+## Your Approach
+1. **Question Everything**: Ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+2. **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.
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+## Output Requirements
+An output implementation plan must also follow the progressive disclosure structure:
+- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
+- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
+- 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).
+
+**IMPORTANT:**
+- Analyze the given task and use `AskUserQuestion` tool to ask for more details if needed.
+- Ensure token consumption efficiency while maintaining high quality.
+- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches Claude how to perform a specific development task, not what a tool does.
+- Claude Code can activate multiple skills automatically to achieve the user's request.

package/templates/commands/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 `planning` 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/commands/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/commands/use-mcp.md

@@ -0,0 +1,34 @@
+---
+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)
+   echo "$ARGUMENTS. Return JSON only per GEMINI.md instructions." | gemini -y -m gemini-2.5-flash
+   ```
+
+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-2.5-flash -p "..."
+```

package/templates/commands/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/commands/worktree.md

@@ -0,0 +1,126 @@
+---
+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 Repository Info
+
+```bash
+node .claude/scripts/worktree.cjs info --json
+```
+
+**Response fields:**
+- `repoType`: "monorepo" or "standalone"
+- `baseBranch`: detected base branch
+- `projects`: array of {name, path} for monorepo
+- `envFiles`: array of .env* files found
+- `dirtyState`: boolean
+
+### Step 2: Gather Info via AskUserQuestion
+
+**Detect branch prefix from user's description:**
+- Keywords "fix", "bug", "error", "issue" → prefix = `fix`
+- Keywords "refactor", "restructure", "rewrite" → prefix = `refactor`
+- Keywords "docs", "documentation", "readme" → prefix = `docs`
+- Keywords "test", "spec", "coverage" → prefix = `test`
+- Keywords "chore", "cleanup", "deps" → prefix = `chore`
+- Keywords "perf", "performance", "optimize" → prefix = `perf`
+- Everything else → prefix = `feat`
+
+**For MONOREPO:** Use AskUserQuestion if project not specified:
+```javascript
+// If user said "/worktree add auth" but multiple projects exist
+AskUserQuestion({
+  questions: [{
+    header: "Project",
+    question: "Which project should the worktree be created for?",
+    options: projects.map(p => ({ label: p.name, description: p.path })),
+    multiSelect: false
+  }]
+})
+```
+
+**For env files:** Always ask which to copy:
+```javascript
+AskUserQuestion({
+  questions: [{
+    header: "Env files",
+    question: "Which environment files should be copied to the worktree?",
+    options: envFiles.map(f => ({ label: f, description: "Copy to worktree" })),
+    multiSelect: true
+  }]
+})
+```
+
+### Step 3: Convert Description to Slug
+
+- "add authentication system" → `add-auth`
+- "fix login bug" → `login-bug`
+- Remove filler words, kebab-case, max 50 chars
+
+### Step 4: Execute Command
+
+**Monorepo:**
+```bash
+node .claude/scripts/worktree.cjs create "<PROJECT>" "<SLUG>" --prefix <TYPE> --env "<FILES>"
+```
+
+**Standalone:**
+```bash
+node .claude/scripts/worktree.cjs create "<SLUG>" --prefix <TYPE> --env "<FILES>"
+```
+
+**Options:**
+- `--prefix` - Branch type: feat|fix|refactor|docs|test|chore|perf
+- `--env` - Comma-separated .env files to copy
+- `--json` - Output JSON for parsing
+- `--dry-run` - Preview without executing
+
+## Commands
+
+| Command | Usage | Description |
+|---------|-------|-------------|
+| `create` | `create [project] <feature>` | Create new worktree |
+| `remove` | `remove <name-or-path>` | Remove worktree and branch |
+| `info` | `info` | Get repo info |
+| `list` | `list` | List existing worktrees |
+
+## Error Codes
+
+| Code | Meaning | Action |
+|------|---------|--------|
+| `MISSING_ARGS` | Missing project/feature for monorepo | Ask for both |
+| `MISSING_FEATURE` | No feature name (standalone) | Ask for feature |
+| `PROJECT_NOT_FOUND` | Project not in .gitmodules | Show available projects |
+| `MULTIPLE_PROJECTS_MATCH` | Ambiguous project name | Use AskUserQuestion |
+| `MULTIPLE_WORKTREES_MATCH` | Ambiguous worktree for remove | Use AskUserQuestion |
+| `BRANCH_CHECKED_OUT` | Branch in use elsewhere | Suggest different name |
+| `WORKTREE_EXISTS` | Path already exists | Suggest use or remove |
+| `WORKTREE_CREATE_FAILED` | Git command failed | Show git error |
+| `WORKTREE_REMOVE_FAILED` | Cannot remove worktree | Check uncommitted changes |
+
+## Example Session
+
+```
+User: /worktree fix the login validation bug
+
+Claude: [Runs: node .claude/scripts/worktree.cjs info --json]
+        [Detects: standalone repo, envFiles: [".env.example"]]
+        [Detects prefix from "fix" keyword: fix]
+        [Converts slug: "login-validation-bug"]
+
+Claude: [Uses AskUserQuestion for env files]
+        "Which environment files should be copied?"
+        Options: .env.example
+
+User: .env.example
+
+Claude: [Runs: node .claude/scripts/worktree.cjs create "login-validation-bug" --prefix fix --env ".env.example"]
+
+Output: Worktree created at ../worktrees/myrepo-login-validation-bug
+        Branch: fix/login-validation-bug
+```

package/templates/discord/README.md

@@ -0,0 +1,274 @@
+# Discord + OpenClaw Setup Guide
+
+This directory contains configuration for running your AI agent on Discord via [OpenClaw](https://docs.openclaw.ai).
+
+## Features
+
+- **Auto Intent Detection** - No need to type `/plan` or `/brainstorm`, bot understands natural language
+- **Skills System** - Commands converted to skills format for better context
+- **Train Prompt** - Add new knowledge via URLs, files, or inline content
+- **Progressive Disclosure** - Skills load on-demand to save tokens
+- **Gemini CLI OAuth** - Use Google OAuth via Gemini CLI (no API key needed!)
+
+## Quick Start
+
+### 1. Install Required CLIs
+
+```bash
+# Install OpenClaw CLI
+npm install -g openclaw
+
+# Install Gemini CLI (for OAuth authentication)
+npm install -g @anthropic-ai/gemini-cli
+```
+
+### 2. Setup AI Model Authentication (Choose One)
+
+#### Option A: Gemini CLI OAuth (Recommended)
+
+No API key needed! Uses Google OAuth via Gemini CLI plugin.
+
+```bash
+# Login to Gemini CLI
+gemini auth login
+
+# Enable Gemini CLI auth plugin
+openclaw plugins enable google-gemini-cli-auth
+
+# Set as default model provider
+openclaw models auth login --provider google-gemini-cli --set-default
+```
+
+**Or use the start script:**
+```bash
+./start-bot.sh
+```
+
+#### Option B: API Key
+
+```bash
+# Set your API key
+openclaw config set models.anthropic.apiKey '"sk-your-api-key"' --json
+```
+
+### 3. Create Discord Bot
+
+1. Go to [Discord Developer Portal](https://discord.com/developers/applications)
+2. Click "New Application" and name your bot
+3. Go to "Bot" section and click "Add Bot"
+4. Enable these Intents:
+   - **Message Content Intent** (required)
+   - **Server Members Intent** (recommended)
+5. Click "Reset Token" to get your bot token
+
+### 4. Configure Bot Token
+
+**Option A: Environment Variable (Recommended)**
+```bash
+export DISCORD_BOT_TOKEN="your-bot-token-here"
+```
+
+**Option B: Direct Configuration**
+```bash
+openclaw config set channels.discord.token '"your-bot-token-here"' --json
+```
+
+### 5. Enable Discord Channel
+
+```bash
+openclaw config set channels.discord.enabled true --json
+```
+
+### 6. Start Gateway
+
+```bash
+# Using start script (handles Gemini CLI auth automatically)
+./start-bot.sh
+
+# Or directly
+openclaw gateway
+```
+
+### 6. Invite Bot to Server
+
+1. Go to OAuth2 > URL Generator in Discord Developer Portal
+2. Select scopes: `bot`, `applications.commands`
+3. Select permissions:
+   - View Channels
+   - Send Messages
+   - Read Message History
+   - Embed Links
+   - Attach Files
+   - Add Reactions
+4. Copy the generated URL and open it to invite the bot
+
+### 7. Pairing (First-time Setup)
+
+1. Send a DM to your bot in Discord
+2. Bot responds with a pairing code
+3. Approve the pairing:
+   ```bash
+   openclaw pairing approve discord <CODE>
+   ```
+
+## Using Commands
+
+Your commands are available in two ways:
+
+### As Slash Commands
+Discord will automatically register your commands as slash commands.
+Type `/` in Discord to see available commands.
+
+Example:
+- `/plan create a login feature`
+- `/brainstorm how to optimize database queries`
+
+### As Message Commands
+Mention the bot with a command:
+```
+@YourBot /plan create a login feature
+```
+
+## Configuration
+
+Edit `config.json5` to customize:
+
+- **dmPolicy**: Control who can DM the bot
+- **groupPolicy**: Control which servers can use the bot
+- **guilds**: Configure per-server settings
+- **streaming**: Enable live typing preview
+- **bindings**: Route different users to different agents
+
+## Commands Available
+
+Your commands are defined in the `commands/` directory:
+
+| Command | Description |
+|---------|-------------|
+| `/plan` | Create implementation plans |
+| `/brainstorm` | Brainstorm solutions |
+| `/fix` | Fix code issues |
+| `/code` | Write code |
+| `/review` | Review code changes |
+| ... | See `commands/` for full list |
+
+## Useful OpenClaw Commands
+
+```bash
+# Check status
+openclaw channels status --probe
+
+# View logs
+openclaw logs --follow
+
+# List pairings
+openclaw pairing list discord
+
+# Restart gateway
+openclaw gateway restart
+
+# Health check
+openclaw doctor
+```
+
+## Skills System
+
+Your commands are converted to **OpenClaw Skills** format for better AI understanding.
+
+### Structure
+```
+.discord/
+├── skills/
+│   ├── auto-intent-router/    # Auto-detects user intent
+│   │   └── SKILL.md
+│   ├── train-prompt/          # Add new knowledge
+│   │   └── SKILL.md
+│   ├── planning/              # Converted from /plan
+│   │   └── SKILL.md
+│   ├── brainstorm/            # Converted from /brainstorm
+│   │   └── SKILL.md
+│   └── ...
+├── commands/                  # Original commands (backup)
+├── commands.json5             # Slash commands config
+└── config.json5               # Main config
+```
+
+### How It Works
+
+1. **Auto Intent Router** detects what user wants from natural language
+2. **Appropriate skill** is activated automatically
+3. User gets response without typing commands
+
+Example:
+```
+User: "I need to add payment processing"
+Bot: [Detects PLANNING intent, activates planning skill]
+     "I'll help you plan the payment processing feature..."
+```
+
+## Training New Knowledge
+
+Use the **train-prompt** skill to teach the bot new things:
+
+### Train from URL
+```
+/train https://docs.stripe.com/api
+```
+
+### Train from File
+```
+/train:file ./docs/coding-standards.md
+```
+
+### Train Inline
+```
+/train:inline
+Our deployment process:
+1. Run tests
+2. Build
+3. Deploy staging
+4. Deploy production
+```
+
+### List Trained Knowledge
+```
+/train:list
+```
+
+## Troubleshooting
+
+**Bot not responding?**
+- Check Message Content Intent is enabled
+- Verify bot token is correct
+- Run `openclaw doctor` for diagnostics
+
+**Commands not showing?**
+- Wait a few minutes for Discord to sync
+- Check `commands.native` is set to `"auto"`
+
+**Permission errors?**
+- Verify bot has required permissions
+- Check guild configuration in `config.json5`
+
+**Skills not loading?**
+- Check `skills/` directory exists
+- Verify SKILL.md files have correct frontmatter
+- Run `openclaw skills list` to see active skills
+
+**Gemini CLI OAuth issues?**
+- Re-login: `gemini auth login`
+- Check plugin status: `openclaw plugins list`
+- Re-enable plugin: `openclaw plugins enable google-gemini-cli-auth`
+- Check auth status: `openclaw models auth status --provider google-gemini-cli`
+- Set as default again: `openclaw models auth login --provider google-gemini-cli --set-default`
+
+**Token expired?**
+- Gemini CLI OAuth tokens auto-refresh
+- If issues persist, run `gemini auth login` again
+
+## Resources
+
+- [OpenClaw Documentation](https://docs.openclaw.ai)
+- [Discord Channel Guide](https://docs.openclaw.ai/channels/discord)
+- [Skills Guide](https://docs.openclaw.ai/tools/skills)
+- [Slash Commands](https://docs.openclaw.ai/tools/slash-commands)

package/templates/discord/config.json5

@@ -0,0 +1,87 @@
+// Clawbot Discord Configuration
+// Generated by Apero Kit CLI
+// Documentation: https://docs.openclaw.ai/channels/discord
+{
+  // Discord Channel Settings
+  "channels": {
+    "discord": {
+      // Bot token - set via environment variable or here
+      // Recommended: Use DISCORD_BOT_TOKEN environment variable
+      "token": "${DISCORD_BOT_TOKEN}",
+
+      // Enable Discord channel
+      "enabled": true,
+
+      // Direct Message Policy
+      // "pairing" - Require pairing approval (recommended)
+      // "allowlist" - Only allow specific users
+      // "open" - Allow all DMs
+      // "disabled" - Disable DMs
+      "dmPolicy": "pairing",
+
+      // Guild (Server) Policy
+      // "open" - Allow all guilds
+      // "allowlist" - Only allow specific guilds
+      // "disabled" - Disable guild messages
+      "groupPolicy": "allowlist",
+
+      // Message History Limit (for context)
+      "historyLimit": 20,
+      "dmHistoryLimit": 50,
+
+      // Reply Mode
+      // "off" - No reply threading
+      // "first" - Reply to first message only
+      // "all" - Reply to all messages
+      "replyToMode": "first",
+
+      // Streaming Mode (live typing preview)
+      // "off" - No streaming
+      // "partial" - Partial updates
+      // "block" - Block updates
+      // "progress" - Progress indicator
+      "streaming": "partial",
+
+      // Guild Configurations
+      // Add your server(s) here
+      "guilds": {
+        // Example guild configuration
+        // Replace YOUR_SERVER_ID with actual Discord server ID
+        // "YOUR_SERVER_ID": {
+        //   "requireMention": true,
+        //   "users": ["YOUR_USER_ID"],
+        //   "roles": ["ALLOWED_ROLE_ID"],
+        //   "channels": {
+        //     "general": { "allow": true },
+        //     "bot-commands": { "allow": true }
+        //   }
+        // }
+      },
+
+      // Bot Presence
+      "status": "online",
+      "activity": "Ready to assist",
+      "activityType": 4  // 0=Playing, 1=Streaming, 2=Listening, 3=Watching, 4=Custom
+    }
+  },
+
+  // Commands Configuration
+  "commands": {
+    // Enable native Discord slash commands
+    "native": "auto"
+  },
+
+  // Agent Bindings (optional)
+  // Route different users/roles to different agents
+  "bindings": [
+    // Example: Route users with specific role to opus agent
+    // {
+    //   "agentId": "opus",
+    //   "match": {
+    //     "channel": "discord",
+    //     "guildId": "YOUR_SERVER_ID",
+    //     "roles": ["PREMIUM_ROLE_ID"]
+    //   }
+    // }
+  ]
+}