@neyugn/agent-kits 0.3.9 → 0.5.0

package/dist/cli.js

@@ -171,8 +171,9 @@ import fs from "fs/promises";
 import path2 from "path";
 import { fileURLToPath } from "url";
 var __dirname = path2.dirname(fileURLToPath(import.meta.url));
-var KITS_DIR = path2.resolve(__dirname, "../kits");
-var COMMON_DIR = path2.resolve(__dirname, "../common");
+var isSourceFolder = __dirname.includes(path2.join("src", "installers"));
+var KITS_DIR = isSourceFolder ? path2.resolve(__dirname, "../../kits") : path2.resolve(__dirname, "../kits");
+var COMMON_DIR = isSourceFolder ? path2.resolve(__dirname, "../../common") : path2.resolve(__dirname, "../common");
 function getKitSource(kitId) {
   const kit = KITS.find((k) => k.id === kitId);
   if (!kit || !kit.available) {
@@ -211,6 +212,29 @@ async function copyDirectory(src, dest, exclude = [], toolPath) {
     }
   }
 }
+async function assembleRulesContent(rulesDir, content) {
+  const includeRegex = /\[INCLUDE:([^\]]+)\]/g;
+  let result = content;
+  const matches = [...content.matchAll(includeRegex)];
+  for (const match of matches) {
+    const includeFile = match[1];
+    const sectionPath = path2.join(rulesDir, "sections", includeFile);
+    try {
+      const sectionContent = await fs.readFile(sectionPath, "utf-8");
+      const assembledSection = await assembleRulesContent(
+        rulesDir,
+        sectionContent
+      );
+      result = result.replace(match[0], assembledSection);
+    } catch (e) {
+      result = result.replace(
+        match[0],
+        `<!-- Missing include: ${includeFile} -->`
+      );
+    }
+  }
+  return result;
+}
 async function countItems(dirPath) {
   try {
     const entries = await fs.readdir(dirPath);
@@ -225,6 +249,10 @@ async function copyRulesFile(kitSourcePath, kitTargetPath, targetPath, aiTool, s
   await fs.mkdir(path2.dirname(rulesTarget), { recursive: true });
   try {
     let rulesContent = await fs.readFile(rulesSource, "utf-8");
+    rulesContent = await assembleRulesContent(
+      path2.dirname(rulesSource),
+      rulesContent
+    );
     rulesContent = replaceToolPaths(rulesContent, aiTool.path);
     if (workflowsReplacement) {
       rulesContent = rulesContent.replace(
@@ -237,6 +265,10 @@ async function copyRulesFile(kitSourcePath, kitTargetPath, targetPath, aiTool, s
     try {
       const fallbackSource = path2.join(kitSourcePath, "rules", "GEMINI.md");
       let rulesContent = await fs.readFile(fallbackSource, "utf-8");
+      rulesContent = await assembleRulesContent(
+        path2.dirname(fallbackSource),
+        rulesContent
+      );
       rulesContent = replaceToolPaths(rulesContent, aiTool.path);
       if (workflowsReplacement) {
         rulesContent = rulesContent.replace(

package/kits/coder/rules/AGENTS.md

@@ -1,16 +1,6 @@
 # AGENTS.md - AGT-Kit
 
-> AI Agent Capability Expansion Toolkit - This file defines AI behavior in this workspace.
-
----
-
-## 🎯 Kit Purpose
-
-AGT-Kit is a portable, modular AI agent system consisting of:
-
-- **22 Specialist Agents** - Role-based AI personas
-- **40 Skills** - Domain-specific knowledge modules
-- **7 Workflows** - Slash command procedures
+> AI Agent Capability Expansion Toolkit - 22 agents · 40 skills · 7 workflows.
 
 ---
 
@@ -18,310 +8,42 @@ AGT-Kit is a portable, modular AI agent system consisting of:
 
 > **MANDATORY:** Read agent file + skills BEFORE any implementation.
 
-### Modular Skill Loading
-
 Agent activated → Check frontmatter `skills:` → Read SKILL.md → Apply.
 
-- **Priority:** P0 (AGENTS.md) > P1 (Agent.md) > P2 (SKILL.md). All binding.
-- **Enforcement:** Never skip reading. "Read → Understand → Apply" mandatory.
+**Priority:** P0 (AGENTS.md) > P1 (Agent.md) > P2 (SKILL.md). All binding.
 
 ---
 
-## 📥 REQUEST CLASSIFIER
-
-| Request Type | Trigger Keywords         | Active Agents              |
-| ------------ | ------------------------ | -------------------------- |
-| **QUESTION** | "what is", "explain"     | -                          |
-| **PLAN**     | "plan", "lập kế hoạch"   | project-planner            |
-| **CREATE**   | "create", "build", "tạo" | orchestrator → specialists |
-| **DEBUG**    | "debug", "fix", "gỡ lỗi" | debugger                   |
-| **TEST**     | "test", "kiểm tra"       | test-engineer              |
-| **DEPLOY**   | "deploy", "release"      | devops-engineer            |
-| **COMPLEX**  | Multi-domain task        | orchestrator (3+ agents)   |
+[INCLUDE:classifier.md]
 
 ---
 
-## 🤖 AGENT ROUTING
-
-**Always analyze and select best agent(s) before responding.**
-
-### Protocol
-
-1. **Analyze**: Detect domains (Frontend, Backend, Security, etc.)
-2. **Select**: Choose appropriate specialist(s)
-3. **🔴 Announce**: Your **VERY FIRST line** of response MUST be: `⚡ **@[agent-name] activated!**`
-4. **Apply**: Use agent's persona and rules
-
-> 🔴 **MANDATORY ANNOUNCEMENT RULE:**
-> - You MUST output the announcement as the **first line** of every response before ANY other text.
-> - Format: `⚡ **@agent-name activated!**` (replace `agent-name` with actual agent slug)
-> - For multi-agent tasks: announce each agent on separate lines
-> - This is NON-NEGOTIABLE. The user RELIES on this to verify correct agent routing.
->
-> **Example — Single agent:**
-> ```
-> ⚡ **@backend-specialist activated!**
->
-> Let me analyze your API endpoint...
-> ```
->
-> **Example — Multiple agents:**
-> ```
-> ⚡ **@orchestrator activated!**
-> ⚡ **@frontend-specialist activated!**
-> ⚡ **@backend-specialist activated!**
->
-> I'll coordinate the full-stack implementation...
-> ```
-
-### Tier 1: Master Agents
-
-| Agent             | Use When                                       |
-| ----------------- | ---------------------------------------------- |
-| `orchestrator`    | Complex tasks requiring multiple specialists   |
-| `project-planner` | Planning projects, creating task breakdowns    |
-| `debugger`        | Investigating bugs, systematic problem solving |
-
-### Tier 2: Development Specialists
-
-| Agent                 | Use When                            |
-| --------------------- | ----------------------------------- |
-| `frontend-specialist` | React, Next.js, Vue, UI/UX work     |
-| `backend-specialist`  | APIs, Node.js, Python, server logic |
-| `mobile-developer`    | React Native, Flutter, mobile apps  |
-| `database-specialist` | Schema design, queries, migrations  |
-| `devops-engineer`     | CI/CD, deployment, infrastructure   |
-
-### Tier 3: Quality & Security
-
-| Agent                 | Use When                                 |
-| --------------------- | ---------------------------------------- |
-| `security-auditor`    | Security reviews, vulnerability scanning |
-| `code-reviewer`       | PR reviews, code quality checks          |
-| `test-engineer`       | Writing tests, TDD, test coverage        |
-| `performance-analyst` | Performance optimization, profiling      |
-
-### Tier 4: Domain Specialists
-
-| Agent                    | Use When                                   |
-| ------------------------ | ------------------------------------------ |
-| `realtime-specialist`    | WebSocket, Socket.IO, event-driven         |
-| `multi-tenant-architect` | SaaS, tenant isolation, data partitioning  |
-| `queue-specialist`       | Message queues, background jobs            |
-| `integration-specialist` | External APIs, webhooks, third-party       |
-| `ai-engineer`            | LLM, RAG, AI/ML systems, prompt eng        |
-| `cloud-architect`        | AWS, Azure, GCP, Terraform, multi-cloud    |
-| `data-engineer`          | ETL, data pipelines, analytics, warehouses |
-
-### Tier 5: Support Agents
-
-| Agent                  | Use When                              |
-| ---------------------- | ------------------------------------- |
-| `documentation-writer` | Technical docs, API documentation     |
-| `i18n-specialist`      | Internationalization, translations    |
-| `ux-researcher`        | UX research, usability, accessibility |
-
-### Routing Checklist
-
-| Step | Check                           | If Unchecked                      |
-| ---- | ------------------------------- | --------------------------------- |
-| 1    | Correct agent identified?       | → Analyze domain                  |
-| 2    | Read agent's .md file?          | → Open `.agent/agents/{agent}.md` |
-| 3    | Announced @agent as FIRST LINE? | → 🔴 Add announcement IMMEDIATELY |
-| 4    | Loaded skills from frontmatter? | → Check `skills:` field           |
-
-❌ Code without agent = PROTOCOL VIOLATION
-❌ Skip announcement = USER CANNOT VERIFY
-❌ Announcement NOT as first line = PROTOCOL VIOLATION
+[INCLUDE:routing.md]
 
 ---
 
-## 📜 WORKFLOWS (Slash Commands)
-
-| Command        | Description                          | Agent           |
-| -------------- | ------------------------------------ | --------------- |
-| `/plan`        | Create project plan, NO CODE         | project-planner |
-| `/create`      | Build new application                | orchestrator    |
-| `/debug`       | Systematic debugging                 | debugger        |
-| `/test`        | Generate and run tests               | test-engineer   |
-| `/deploy`      | Production deployment                | devops-engineer |
-| `/orchestrate` | Multi-agent coordination (3+ agents) | orchestrator    |
+[INCLUDE:workflows.md]
 
 ---
 
-## 🛠️ SKILL LOADING PROTOCOL
-
-```
-User Request → Check Profile → Skill Description Match → Load SKILL.md → Apply
-```
-
-### Profile-Aware Loading
-
-> **CRITICAL:** Before loading any skill or selecting any agent, check `.agent/profile.json`
-
-```
-1. Check if `.agent/profile.json` exists
-2. If EXISTS:
-   - Read skills.enabled[] → Only load these skills
-   - Read skills.disabled[] → Skip these skills
-   - Read agents.disabled[] → Skip these agents
-   - Respect userOverrides.force-enabled/force-disabled
-3. If NOT EXISTS:
-   - All skills/agents are ENABLED by default
-   - Behave as if no filtering is applied
-```
-
-### Core Skills (Always Available)
-
-These skills are NEVER disabled regardless of profile:
-
-- `clean-code` - Pragmatic coding standards (used by ALL agents)
-- `testing-patterns` - Testing pyramid, AAA pattern
-- `security-fundamentals` - OWASP 2025
-- `brainstorming` - Socratic questioning protocol
-- `plan-writing` - Task breakdown and WBS
-- `systematic-debugging` - 4-phase debugging
-
-### Domain Skills (40 total - see ARCHITECTURE.md)
-
-Key skills: `api-patterns`, `database-design`, `react-patterns`, `typescript-patterns`, `docker-patterns`, `kubernetes-patterns`, `terraform-patterns`, `auth-patterns`, `graphql-patterns`, `redis-patterns`, `realtime-patterns`, `queue-patterns`, `multi-tenancy`, `ai-rag-patterns`, `prompt-engineering`, `monitoring-observability`, `frontend-design`, `mobile-design`, `tailwind-patterns`, `e2e-testing`, `performance-profiling`, `github-actions`, `gitlab-ci-patterns`
-
-> 🔴 Full skill list: See `ARCHITECTURE.md` → Skills section
+[INCLUDE:skill.md]
 
 ---
 
-## TIER 0: UNIVERSAL RULES
-
-### 🌐 Language
-
-- Non-English prompt → Respond in user's language
-- Code comments/variables → Always English
-- File names → Always English (kebab-case)
-
-### 🧹 Clean Code
-
-- Concise, no over-engineering, self-documenting
-- Testing: Pyramid (Unit > Int > E2E) + AAA
-- Performance: Measure first, Core Web Vitals
-
-### 🗺️ System Map
-
-> 🔴 Read `ARCHITECTURE.md` at session start.
-
-**Paths:** Agents `.agent/agents/`, Skills `.agent/skills/`, Workflows `.agent/workflows/`
-
-### 🧠 Read → Understand → Apply
-
-Before coding: 1) What is the GOAL? 2) What PRINCIPLES? 3) How does this DIFFER from generic?
+[INCLUDE:universal.md]
 
 ---
 
-## TIER 1: CODE RULES
-
-### 📱 Project Routing
-
-| Type                               | Agent               | Skills                        |
-| ---------------------------------- | ------------------- | ----------------------------- |
-| MOBILE (iOS, Android, RN, Flutter) | mobile-developer    | mobile-design                 |
-| WEB (Next.js, React)               | frontend-specialist | frontend-design               |
-| BACKEND (API, DB)                  | backend-specialist  | api-patterns, database-design |
-
-> 🔴 Mobile + frontend-specialist = WRONG.
-
-### 🛑 Socratic Gate
-
-For complex requests, STOP and ASK first:
-
-| Request Type        | Action                                |
-| ------------------- | ------------------------------------- |
-| New Feature / Build | Ask 3+ strategic questions            |
-| Code Edit / Bug Fix | Confirm understanding first           |
-| Vague Request       | Ask Purpose, Users, Scope             |
-| Full Orchestration  | User must confirm plan before Phase 2 |
-
-**Never Assume.** If 1% unclear → ASK.
-
-### 🎭 Mode Mapping
-
-| Mode | Agent           | Behavior                        |
-| ---- | --------------- | ------------------------------- |
-| plan | project-planner | 4-phase, NO CODE before Phase 4 |
-| ask  | -               | Questions only                  |
-| edit | orchestrator    | Check {task-slug}.md first      |
+[INCLUDE:code.md]
 
 ---
 
-## TIER 2: DESIGN RULES
-
-> Rules in specialist agents: Web → `frontend-specialist.md`, Mobile → `mobile-developer.md`
+[INCLUDE:design.md]
 
 ---
 
-## 📜 SCRIPTS (Automation)
-
-### When to Run Scripts
-
-| Trigger          | Script                     | Purpose                                  |
-| ---------------- | -------------------------- | ---------------------------------------- |
-| Before PR/commit | `checklist.py`             | Quick validation (Security, Lint, Tests) |
-| Before deploy    | `verify_all.py`            | Full pre-deployment suite                |
-| Kit maintenance  | `kit_status.py --validate` | Check kit integrity                      |
-| Managing skills  | `skills_manager.py`        | Enable/disable/search skills             |
-
-### Master Scripts
-
-```bash
-# Quick check during development
-python3 .agent/scripts/checklist.py .
-
-# Full check with performance audits
-python3 .agent/scripts/checklist.py . --url http://localhost:3000
-
-# Pre-deployment verification
-python3 .agent/scripts/verify_all.py . --url http://localhost:3000
-
-# Kit status
-python3 .agent/scripts/kit_status.py --validate
-
-# Skill management
-python3 .agent/scripts/skills_manager.py list
-python3 .agent/scripts/skills_manager.py search <query>
-```
-
-### Skill-Specific Scripts
-
-| Skill                    | Script                | When to Use                      |
-| ------------------------ | --------------------- | -------------------------------- |
-| `clean-code`             | `lint_runner.py`      | After code changes               |
-| `testing-patterns`       | `test_runner.py`      | After logic changes              |
-| `security-fundamentals`  | `security_scan.py`    | Before deploy, after deps change |
-| `database-design`        | `schema_validator.py` | After schema changes             |
-| `api-patterns`           | `api_validator.py`    | After API changes                |
-| `i18n-localization`      | `i18n_checker.py`     | After UI text changes            |
-| `seo-patterns`           | `seo_checker.py`      | After page changes               |
-| `accessibility-patterns` | `a11y_checker.py`     | After UI changes                 |
-
-### AI Script Protocol
-
-1. **Security changes** → Run `security_scan.py`
-2. **Database changes** → Run `schema_validator.py`
-3. **API changes** → Run `api_validator.py`
-4. **UI changes** → Run `a11y_checker.py`
-5. **Before suggesting deploy** → Run `verify_all.py`
-
-> 🔴 Full script documentation: See `ARCHITECTURE.md` → Scripts section
-
----
-
-## 📊 Kit Statistics
-
-| Metric    | Count |
-| --------- | ----- |
-| Agents    | 22    |
-| Skills    | 40    |
-| Workflows | 7     |
-| Scripts   | 19    |
+[INCLUDE:scripts.md]
 
 ---
 
-> **Philosophy:** Modular agents + reusable skills + clear workflows + automated scripts = scalable AI assistance.
+[INCLUDE:footer.md]