@neyugn/agent-kits 0.1.0

package/kits/coder/workflows/create.md

@@ -0,0 +1,152 @@
+---
+description: Create new application from scratch. Triggers app-builder skill with multi-agent orchestration.
+---
+
+# /create - Application Creation Workflow
+
+$ARGUMENTS
+
+---
+
+## Trigger
+
+Use when user says: "create", "build", "tạo", "make", "new app", or `/create`
+
+## Agent
+
+Route to `orchestrator` agent → coordinates specialists
+
+---
+
+## 🔴 Critical Rules
+
+1. **Socratic Gate First** - Do NOT start building without understanding requirements
+2. **Plan Before Code** - Create or reference a plan before implementation
+3. **Multi-Agent** - Orchestrate specialists for each domain
+4. **Preview at End** - Start dev server and provide URL
+
+---
+
+## Workflow
+
+### Phase 1: Request Analysis
+
+Understand user's request:
+
+```markdown
+## Request Analysis
+
+- **Type**: Web app / Mobile app / API / CLI
+- **Core Features**: [List main features]
+- **Stack**: [Inferred or specified tech stack]
+- **Complexity**: Simple / Medium / Complex
+```
+
+If unclear, ask:
+
+```markdown
+Before I start building, I need to understand:
+
+1. **Type**: What kind of application? (Web/Mobile/API)
+2. **Features**: What are the 3 most important features?
+3. **Users**: Who will use this application?
+```
+
+### Phase 2: Project Planning
+
+Two options:
+
+| Condition   | Action                                    |
+| ----------- | ----------------------------------------- |
+| Plan exists | Read `docs/PLAN-*.md`                     |
+| No plan     | Create brief plan using `project-planner` |
+
+Determine:
+
+- Tech stack selection
+- File structure
+- Component breakdown
+- API design (if applicable)
+
+### Phase 3: Orchestrated Building
+
+Coordinate specialists:
+
+```markdown
+## Agent Assignments
+
+| Agent                 | Task                |
+| --------------------- | ------------------- |
+| `database-specialist` | Schema design       |
+| `backend-specialist`  | API implementation  |
+| `frontend-specialist` | UI components       |
+| `devops-engineer`     | Config & deployment |
+```
+
+Build order:
+
+1. Database schema → 2. Backend API → 3. Frontend UI → 4. Integration
+
+### Phase 4: Testing & Preview
+
+After building:
+
+```bash
+# Start development server
+pnpm dev
+```
+
+### Phase 5: Report
+
+Present to user:
+
+```markdown
+✅ **Application Created!**
+
+**Stack:** [Tech stack used]
+**Structure:**
+
+- `src/` - Source code
+- `api/` - Backend routes
+- `components/` - UI components
+
+**Preview:** http://localhost:3000
+
+**Next Steps:**
+
+- Review the code
+- Run `/test` to add tests
+- Run `/deploy` when ready
+```
+
+---
+
+## Tech Stack Decision Framework
+
+| Project Type | Recommended Stack        |
+| ------------ | ------------------------ |
+| Simple Web   | Vanilla HTML/CSS/JS      |
+| React App    | Vite + React + CSS       |
+| Full-Stack   | Next.js / Vite + Express |
+| Mobile       | React Native / Flutter   |
+| API Only     | Express / Hono / Fastify |
+
+---
+
+## Exit Conditions
+
+- ✅ **Success:** App running at localhost with core features
+- ❌ **Failure:** User cancels or critical dependency unavailable
+- ⚠️ **Warning:** Partial build, some features incomplete
+
+---
+
+## Usage Examples
+
+```
+/create blog site
+/create e-commerce app with cart
+/create todo app
+/create Instagram clone
+/create CRM với quản lý khách hàng
+```

package/kits/coder/workflows/debug.md

@@ -0,0 +1,223 @@
+---
+description: Debugging command. Activates DEBUG mode for systematic problem investigation using 4-phase methodology.
+---
+
+# /debug - Systematic Debugging Workflow
+
+$ARGUMENTS
+
+---
+
+## Trigger
+
+Use when user says: "debug", "fix", "gỡ lỗi", "investigate", "error", or `/debug`
+
+## Agent
+
+Route to `debugger` agent
+
+---
+
+## 🔴 Critical Rules
+
+1. **Gather Evidence First** - Never guess without information
+2. **Form Hypotheses** - Rank by likelihood
+3. **Test Systematically** - One variable at a time
+4. **Explain Root Cause** - Not just the fix
+
+---
+
+## Workflow
+
+### Phase 1: Information Gathering
+
+Collect all relevant context:
+
+```markdown
+## 🔍 Debug Session: [Issue Title]
+
+### Symptom
+
+- What is happening?
+- What should happen instead?
+
+### Context
+
+- **Error Message**: `[exact error]`
+- **File(s) Affected**: `[file paths]`
+- **Line Number(s)**: [if known]
+- **Recent Changes**: [what changed before issue appeared]
+- **Reproduction Steps**: [how to reproduce]
+```
+
+If user provides incomplete info, ask:
+
+```markdown
+I need more information to debug effectively:
+
+1. What is the exact error message?
+2. How do you reproduce this issue?
+3. What was working before?
+```
+
+### Phase 2: Hypothesis Formation
+
+Create ranked list of possible causes:
+
+```markdown
+### Hypotheses (Ranked by Likelihood)
+
+1. ❓ **High**: [Most likely cause based on symptoms]
+2. ❓ **Medium**: [Second possibility]
+3. ❓ **Low**: [Less likely cause]
+```
+
+### Phase 3: Systematic Investigation
+
+Test each hypothesis:
+
+```markdown
+### Investigation
+
+**Testing Hypothesis 1: [Name]**
+
+- Action: [What I checked]
+- Result: ✅ Confirmed / ❌ Ruled Out
+- Evidence: [Specific finding]
+
+**Testing Hypothesis 2: [Name]**
+
+- Action: [What I checked]
+- Result: ✅ Confirmed / ❌ Ruled Out
+- Evidence: [Specific finding]
+```
+
+Tools to use:
+
+- Add console logs / breakpoints
+- Check network requests
+- Verify data flow
+- Compare with working state
+
+### Phase 4: Fix & Prevent
+
+Apply fix and document:
+
+```markdown
+### 🎯 Root Cause
+
+[Clear explanation of WHY this happened]
+
+### Fix Applied
+
+\`\`\`[language]
+// Before (broken)
+[old code]
+
+// After (fixed)
+[new code]
+\`\`\`
+
+### Prevention
+
+🛡️ To prevent this in the future:
+
+- [ ] [Specific prevention measure]
+- [ ] [Add test case]
+- [ ] [Update documentation]
+```
+
+### Phase 5: Report
+
+Summarize the debugging session:
+
+```markdown
+✅ **Debug Complete**
+
+**Issue:** [Brief description]
+**Root Cause:** [One sentence explanation]
+**Fix:** [What was changed]
+
+**Files Modified:**
+
+- `[file1]` - [change description]
+- `[file2]` - [change description]
+
+**Next Steps:**
+
+- Run tests to verify fix
+- Consider adding regression test
+```
+
+---
+
+## Output Format Template
+
+```markdown
+## 🔍 Debug: [Issue Summary]
+
+### 1. Symptom
+
+[What's happening]
+
+### 2. Information Gathered
+
+| Item  | Value       |
+| ----- | ----------- |
+| Error | `[message]` |
+| File  | `[path]`    |
+| Line  | [number]    |
+
+### 3. Hypotheses
+
+1. ❓ [Most likely]
+2. ❓ [Second option]
+3. ❓ [Less likely]
+
+### 4. Investigation
+
+Testing each hypothesis with evidence...
+
+### 5. Root Cause
+
+🎯 **[Explanation]**
+
+### 6. Fix
+
+[Code changes]
+
+### 7. Prevention
+
+🛡️ [Future safeguards]
+```
+
+---
+
+## Exit Conditions
+
+- ✅ **Success:** Root cause identified, fix applied, verified working
+- ❌ **Failure:** Unable to reproduce issue or requires external support
+- ⚠️ **Warning:** Workaround applied but root cause unclear
+
+---
+
+## Usage Examples
+
+```
+/debug login not working
+/debug API returns 500 error
+/debug form doesn't submit
+/debug dữ liệu không lưu được
+/debug component not rendering
+```
+
+---
+
+## Key Principles
+
+| Principle              | Description                                 |
+| ---------------------- | ------------------------------------------- |
+| **Ask First**          | Get full error context before investigating |
+| **Test Hypotheses**    | Don't guess randomly, be systematic         |
+| **Explain Why**        | Document root cause, not just fix           |
+| **Prevent Recurrence** | Add tests or validation                     |

package/kits/coder/workflows/deploy.md

@@ -0,0 +1,283 @@
+---
+description: Deployment command for production releases. Pre-flight checks and deployment execution.
+---
+
+# /deploy - Production Deployment Workflow
+
+$ARGUMENTS
+
+---
+
+## Trigger
+
+Use when user says: "deploy", "release", "ship", "triển khai", or `/deploy`
+
+## Agent
+
+Route to `devops-engineer` agent
+
+---
+
+## Sub-commands
+
+| Command              | Description                    |
+| -------------------- | ------------------------------ |
+| `/deploy`            | Interactive deployment wizard  |
+| `/deploy check`      | Run pre-deployment checks only |
+| `/deploy preview`    | Deploy to preview/staging      |
+| `/deploy production` | Deploy to production           |
+| `/deploy rollback`   | Rollback to previous version   |
+
+---
+
+## 🔴 Critical Rules
+
+1. **Pre-flight Checks** - Never deploy without passing all checks
+2. **No Hardcoded Secrets** - All secrets in environment variables
+3. **Health Check After Deploy** - Verify application is running
+4. **Rollback Plan Ready** - Always have a way back
+
+---
+
+## Workflow
+
+### Phase 1: Pre-Deployment Checks
+
+Run all checks before deployment:
+
+```markdown
+## 🚀 Pre-Deploy Checklist
+
+### Code Quality
+
+- [ ] No TypeScript errors (`pnpm tsc --noEmit`)
+- [ ] ESLint passing (`pnpm lint`)
+- [ ] All tests passing (`pnpm test`)
+
+### Security
+
+- [ ] No hardcoded secrets
+- [ ] Environment variables documented
+- [ ] Dependencies audited (`pnpm audit`)
+
+### Performance
+
+- [ ] Bundle size acceptable
+- [ ] No console.log statements
+- [ ] Images optimized
+
+### Documentation
+
+- [ ] README updated
+- [ ] CHANGELOG updated
+- [ ] API docs current
+```
+
+If any check fails, stop and fix before proceeding.
+
+### Phase 2: Build Application
+
+Build for production:
+
+```bash
+# Build the application
+pnpm build
+
+# Verify build output
+ls -la dist/
+```
+
+Check for build errors or warnings.
+
+### Phase 3: Deploy
+
+Deploy to target platform:
+
+```markdown
+## Deployment Execution
+
+### Platform: [Detected/Specified]
+
+### Environment: [preview/production]
+
+### Version: [Auto-generated or specified]
+```
+
+Platform-specific commands:
+
+| Platform | Command                | Auto-detect        |
+| -------- | ---------------------- | ------------------ |
+| Vercel   | `vercel --prod`        | Next.js            |
+| Railway  | `railway up`           | Node.js            |
+| Fly.io   | `fly deploy`           | Dockerfile         |
+| Docker   | `docker compose up -d` | docker-compose.yml |
+| AWS      | `aws s3 sync`          | AWS CLI            |
+
+### Phase 4: Health Check
+
+Verify deployment success:
+
+```markdown
+## Health Check
+
+### Endpoints
+
+- [ ] Main URL responding (200 OK)
+- [ ] API health endpoint (`/api/health`)
+- [ ] Database connected
+
+### Services
+
+- [ ] All containers running
+- [ ] No error logs in last 5 minutes
+- [ ] Memory/CPU within limits
+```
+
+### Phase 5: Report
+
+Present deployment summary:
+
+```markdown
+## 🚀 Deployment Complete
+
+### Summary
+
+| Item        | Value      |
+| ----------- | ---------- |
+| Version     | v1.2.3     |
+| Environment | production |
+| Duration    | 47 seconds |
+| Platform    | Vercel     |
+
+### URLs
+
+- 🌐 **Production:** https://app.example.com
+- 📊 **Dashboard:** https://vercel.com/project
+
+### What Changed
+
+- Added user profile feature
+- Fixed login bug
+- Updated dependencies
+
+### Health Check
+
+✅ API responding (200 OK)
+✅ Database connected
+✅ All services healthy
+
+### Rollback
+
+If issues occur, run: `/deploy rollback`
+```
+
+---
+
+## Deployment Flow Diagram
+
+```
+┌─────────────────┐
+│  /deploy        │
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────┐
+│  Pre-flight     │
+│  checks         │
+└────────┬────────┘
+         │
+    Pass? ──No──► Fix issues
+         │
+        Yes
+         │
+         ▼
+┌─────────────────┐
+│  Build          │
+│  application    │
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────┐
+│  Deploy to      │
+│  platform       │
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────┐
+│  Health check   │
+│  & verify       │
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────┐
+│  ✅ Complete    │
+└─────────────────┘
+```
+
+---
+
+## Rollback Procedure
+
+If deployment fails or issues are detected:
+
+````markdown
+## 🔄 Rollback Procedure
+
+### Step 1: Identify Issue
+
+- What symptom?
+- When did it start?
+- Which version?
+
+### Step 2: Execute Rollback
+
+```bash
+# Vercel
+vercel rollback
+
+# Railway
+railway rollback
+
+# Docker
+docker compose down
+docker compose -f docker-compose.previous.yml up -d
+```
+````
+
+### Step 3: Verify Rollback
+
+- [ ] Previous version running
+- [ ] Health checks passing
+- [ ] User-facing error resolved
+
+### Step 4: Document
+
+- Record what failed
+- Create fix plan
+- Schedule proper deployment
+
+```
+
+---
+
+## Exit Conditions
+
+- ✅ **Success:** Deployed, health check passing, URLs accessible
+- ❌ **Failure:** Build failed, deployment error, health check failed
+- ⚠️ **Warning:** Deployed but with warnings (deprecations, high memory)
+
+---
+
+## Usage Examples
+
+```
+
+/deploy
+/deploy check
+/deploy preview
+/deploy production
+/deploy rollback
+
+```
+
+```