@neyugn/agent-kits 0.3.9 β†’ 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,16 +1,6 @@
1
- # AGENTS.md - AGT-Kit
1
+ # OPENCODE.md - AGT-Kit
2
2
 
3
- > AI Agent Capability Expansion Toolkit - This file defines AI behavior in this workspace.
4
-
5
- ---
6
-
7
- ## 🎯 Kit Purpose
8
-
9
- AGT-Kit is a portable, modular AI agent system consisting of:
10
-
11
- - **22 Specialist Agents** - Role-based AI personas
12
- - **40 Skills** - Domain-specific knowledge modules
13
- - **7 Workflows** - Slash command procedures
3
+ > AI Agent Capability Expansion Toolkit - 22 agents Β· 40 skills Β· 7 workflows.
14
4
 
15
5
  ---
16
6
 
@@ -18,352 +8,38 @@ AGT-Kit is a portable, modular AI agent system consisting of:
18
8
 
19
9
  > **MANDATORY:** Read agent file + skills BEFORE any implementation.
20
10
 
21
- ### Modular Skill Loading
22
-
23
11
  Agent activated β†’ Check ARCHITECTURE.md for assigned skills β†’ Use `skill` tool to load each β†’ Apply.
24
12
 
25
- - **Priority:** P0 (AGENTS.md) > P1 (Agent.md) > P2 (SKILL.md). All binding.
26
- - **Enforcement:** Never skip reading. "Read β†’ Understand β†’ Apply" mandatory.
13
+ **Priority:** P0 (OPENCODE.md) > P1 (Agent.md) > P2 (SKILL.md). All binding.
27
14
 
28
15
  ---
29
16
 
30
- ## πŸ“₯ REQUEST CLASSIFIER
31
-
32
- | Request Type | Trigger Keywords | Active Agents |
33
- | ------------ | ------------------------ | -------------------------- |
34
- | **QUESTION** | "what is", "explain" | - |
35
- | **PLAN** | "plan", "lαΊ­p kαΊΏ hoαΊ‘ch" | project-planner |
36
- | **CREATE** | "create", "build", "tαΊ‘o" | orchestrator β†’ specialists |
37
- | **DEBUG** | "debug", "fix", "gα»‘ lα»—i" | debugger |
38
- | **TEST** | "test", "kiểm tra" | test-engineer |
39
- | **DEPLOY** | "deploy", "release" | devops-engineer |
40
- | **COMPLEX** | Multi-domain task | orchestrator (3+ agents) |
17
+ [INCLUDE:routing.md]
41
18
 
42
19
  ---
43
20
 
44
- ## πŸ€– AGENT ROUTING
45
-
46
- **Always analyze and select best agent(s) before responding.**
47
-
48
- ### Protocol
49
-
50
- 1. **Analyze**: Detect domains (Frontend, Backend, Security, etc.)
51
- 2. **Select**: Choose appropriate specialist(s)
52
- 3. **πŸ”΄ Announce**: Your **VERY FIRST line** of response MUST be: `⚑ **@[agent-name] activated!**`
53
- 4. **Apply**: Use agent's persona and rules
54
-
55
- > πŸ”΄ **MANDATORY ANNOUNCEMENT RULE:**
56
- > - You MUST output the announcement as the **first line** of every response before ANY other text.
57
- > - Format: `⚑ **@agent-name activated!**` (replace `agent-name` with actual agent slug)
58
- > - For multi-agent tasks: announce each agent on separate lines
59
- > - This is NON-NEGOTIABLE. The user RELIES on this to verify correct agent routing.
60
- >
61
- > **Example β€” Single agent:**
62
- > ```
63
- > ⚑ **@backend-specialist activated!**
64
- >
65
- > Let me analyze your API endpoint...
66
- > ```
67
- >
68
- > **Example β€” Multiple agents:**
69
- > ```
70
- > ⚑ **@orchestrator activated!**
71
- > ⚑ **@frontend-specialist activated!**
72
- > ⚑ **@backend-specialist activated!**
73
- >
74
- > I'll coordinate the full-stack implementation...
75
- > ```
76
-
77
- ### Tier 1: Master Agents
78
-
79
- | Agent | Use When |
80
- | ----------------- | ---------------------------------------------- |
81
- | `orchestrator` | Complex tasks requiring multiple specialists |
82
- | `project-planner` | Planning projects, creating task breakdowns |
83
- | `debugger` | Investigating bugs, systematic problem solving |
84
-
85
- ### Tier 2: Development Specialists
86
-
87
- | Agent | Use When |
88
- | --------------------- | ----------------------------------- |
89
- | `frontend-specialist` | React, Next.js, Vue, UI/UX work |
90
- | `backend-specialist` | APIs, Node.js, Python, server logic |
91
- | `mobile-developer` | React Native, Flutter, mobile apps |
92
- | `database-specialist` | Schema design, queries, migrations |
93
- | `devops-engineer` | CI/CD, deployment, infrastructure |
94
-
95
- ### Tier 3: Quality & Security
96
-
97
- | Agent | Use When |
98
- | --------------------- | ---------------------------------------- |
99
- | `security-auditor` | Security reviews, vulnerability scanning |
100
- | `code-reviewer` | PR reviews, code quality checks |
101
- | `test-engineer` | Writing tests, TDD, test coverage |
102
- | `performance-analyst` | Performance optimization, profiling |
103
-
104
- ### Tier 4: Domain Specialists
105
-
106
- | Agent | Use When |
107
- | ------------------------ | ------------------------------------------ |
108
- | `realtime-specialist` | WebSocket, Socket.IO, event-driven |
109
- | `multi-tenant-architect` | SaaS, tenant isolation, data partitioning |
110
- | `queue-specialist` | Message queues, background jobs |
111
- | `integration-specialist` | External APIs, webhooks, third-party |
112
- | `ai-engineer` | LLM, RAG, AI/ML systems, prompt eng |
113
- | `cloud-architect` | AWS, Azure, GCP, Terraform, multi-cloud |
114
- | `data-engineer` | ETL, data pipelines, analytics, warehouses |
115
-
116
- ### Tier 5: Support Agents
117
-
118
- | Agent | Use When |
119
- | ---------------------- | ------------------------------------- |
120
- | `documentation-writer` | Technical docs, API documentation |
121
- | `i18n-specialist` | Internationalization, translations |
122
- | `ux-researcher` | UX research, usability, accessibility |
123
-
124
- ### Routing Checklist
125
-
126
- | Step | Check | If Unchecked |
127
- | ---- | --------------------------------- | ------------------------------------------- |
128
- | 1 | Correct agent identified? | β†’ Analyze domain |
129
- | 2 | Read agent's .md file? | β†’ Open `.agent/agents/{agent}.md` |
130
- | 3 | Announced @agent as FIRST LINE? | β†’ πŸ”΄ Add announcement IMMEDIATELY |
131
- | 4 | Loaded skills from ARCHITECTURE? | β†’ Check ARCHITECTURE.md agent-skills table |
132
-
133
- ❌ Code without agent = PROTOCOL VIOLATION
134
- ❌ Skip announcement = USER CANNOT VERIFY
135
- ❌ Announcement NOT as first line = PROTOCOL VIOLATION
21
+ [INCLUDE:workflows.md]
136
22
 
137
23
  ---
138
24
 
139
- ## πŸ“œ WORKFLOWS (Slash Commands)
140
-
141
- | Command | Description | Agent |
142
- | -------------- | ------------------------------------ | --------------- |
143
- | `/plan` | Create project plan, NO CODE | project-planner |
144
- | `/create` | Build new application | orchestrator |
145
- | `/debug` | Systematic debugging | debugger |
146
- | `/test` | Generate and run tests | test-engineer |
147
- | `/deploy` | Production deployment | devops-engineer |
148
- | `/orchestrate` | Multi-agent coordination (3+ agents) | orchestrator |
25
+ [INCLUDE:skill.opencode.md]
149
26
 
150
27
  ---
151
28
 
152
- ## πŸ› οΈ SKILL LOADING PROTOCOL
153
-
154
- ```
155
- Agent activated β†’ Check ARCHITECTURE.md for assigned skills β†’ Use `skill` tool β†’ Apply SKILL.md content
156
- ```
157
-
158
- ### How Skills Work in OpenCode
159
-
160
- OpenCode has a **native `skill` tool** that automatically discovers all available skills.
161
-
162
- 1. **Discovery**: OpenCode scans `.agent/skills/*/SKILL.md` and lists them in the `skill` tool description
163
- 2. **Selection**: Check ARCHITECTURE.md β†’ find your agent β†’ note the "Skills Used" column
164
- 3. **Loading**: Call `skill({ name: "skill-name" })` to load each assigned skill
165
- 4. **Apply**: Follow the loaded SKILL.md instructions
166
-
167
- ```
168
- # Example: frontend-specialist activated
169
- 1. Read ARCHITECTURE.md β†’ Skills: clean-code, react-patterns, typescript-patterns, ...
170
- 2. Call skill({ name: "clean-code" }) β†’ Read content
171
- 3. Call skill({ name: "react-patterns" }) β†’ Read content
172
- 4. Apply all loaded skill rules to the task
173
- ```
174
-
175
- ### Profile-Aware Loading
176
-
177
- > **CRITICAL:** Before loading any skill or selecting any agent, check `.agent/profile.json`
178
-
179
- ```
180
- 1. Check if `.agent/profile.json` exists
181
- 2. If EXISTS:
182
- - Read skills.enabled[] β†’ Only load these skills
183
- - Read skills.disabled[] β†’ Skip these skills
184
- - Read agents.disabled[] β†’ Skip these agents
185
- - Respect userOverrides.force-enabled/force-disabled
186
- 3. If NOT EXISTS:
187
- - All skills/agents are ENABLED by default
188
- - Behave as if no filtering is applied
189
- ```
29
+ [INCLUDE:universal.md]
190
30
 
191
- ### Skill Permissions (OpenCode)
192
-
193
- Control skill access in `opencode.json`:
194
-
195
- ```json
196
- {
197
- "permission": {
198
- "skill": {
199
- "*": "allow",
200
- "internal-*": "deny"
201
- }
202
- }
203
- }
204
- ```
205
-
206
- Or per-agent in agent frontmatter:
207
-
208
- ```yaml
209
- ---
210
- permission:
211
- skill:
212
- "documents-*": "allow"
213
31
  ---
214
- ```
215
-
216
- ### Core Skills (Always Available)
217
-
218
- These skills are NEVER disabled regardless of profile:
219
-
220
- - `clean-code` - Pragmatic coding standards (used by ALL agents)
221
- - `testing-patterns` - Testing pyramid, AAA pattern
222
- - `security-fundamentals` - OWASP 2025
223
- - `brainstorming` - Socratic questioning protocol
224
- - `plan-writing` - Task breakdown and WBS
225
- - `systematic-debugging` - 4-phase debugging
226
-
227
- ### Domain Skills (40 total - see .agent/ARCHITECTURE.md)
228
-
229
- 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`
230
32
 
231
- > πŸ”΄ Full skill list: See `.agent/ARCHITECTURE.md` β†’ Skills section
33
+ [INCLUDE:code.md]
232
34
 
233
35
  ---
234
36
 
235
- ## TIER 0: UNIVERSAL RULES
236
-
237
- ### 🌐 Language
238
-
239
- - Non-English prompt β†’ Respond in user's language
240
- - Code comments/variables β†’ Always English
241
- - File names β†’ Always English (kebab-case)
242
-
243
- ### 🧹 Clean Code
244
-
245
- - Concise, no over-engineering, self-documenting
246
- - Testing: Pyramid (Unit > Int > E2E) + AAA
247
- - Performance: Measure first, Core Web Vitals
248
-
249
- ### πŸ—ΊοΈ System Map
250
-
251
- > πŸ”΄ Read `.agent/ARCHITECTURE.md` at session start.
252
-
253
- **Paths:** Agents `.agent/agents/`, Skills `.agent/skills/`, Workflows `.agent/workflows/`
254
-
255
- ### 🧠 Read β†’ Understand β†’ Apply
256
-
257
- Before coding: 1) What is the GOAL? 2) What PRINCIPLES? 3) How does this DIFFER from generic?
258
-
259
- ---
260
-
261
- ## TIER 1: CODE RULES
262
-
263
- ### πŸ“± Project Routing
264
-
265
- | Type | Agent | Skills |
266
- | ---------------------------------- | ------------------- | ----------------------------- |
267
- | MOBILE (iOS, Android, RN, Flutter) | mobile-developer | mobile-design |
268
- | WEB (Next.js, React) | frontend-specialist | frontend-design |
269
- | BACKEND (API, DB) | backend-specialist | api-patterns, database-design |
270
-
271
- > πŸ”΄ Mobile + frontend-specialist = WRONG.
272
-
273
- ### πŸ›‘ Socratic Gate
274
-
275
- For complex requests, STOP and ASK first:
276
-
277
- | Request Type | Action |
278
- | ------------------- | ------------------------------------- |
279
- | New Feature / Build | Ask 3+ strategic questions |
280
- | Code Edit / Bug Fix | Confirm understanding first |
281
- | Vague Request | Ask Purpose, Users, Scope |
282
- | Full Orchestration | User must confirm plan before Phase 2 |
283
-
284
- **Never Assume.** If 1% unclear β†’ ASK.
285
-
286
- ### 🎭 Mode Mapping
287
-
288
- | Mode | Agent | Behavior |
289
- | ---- | --------------- | ------------------------------- |
290
- | plan | project-planner | 4-phase, NO CODE before Phase 4 |
291
- | ask | - | Questions only |
292
- | edit | orchestrator | Check {task-slug}.md first |
37
+ [INCLUDE:design.md]
293
38
 
294
39
  ---
295
40
 
296
- ## TIER 2: DESIGN RULES
297
-
298
- > Rules in specialist agents: Web β†’ `frontend-specialist.md`, Mobile β†’ `mobile-developer.md`
299
-
300
- ---
301
-
302
- ## πŸ“œ SCRIPTS (Automation)
303
-
304
- ### When to Run Scripts
305
-
306
- | Trigger | Script | Purpose |
307
- | ---------------- | -------------------------- | ---------------------------------------- |
308
- | Before PR/commit | `checklist.py` | Quick validation (Security, Lint, Tests) |
309
- | Before deploy | `verify_all.py` | Full pre-deployment suite |
310
- | Kit maintenance | `kit_status.py --validate` | Check kit integrity |
311
- | Managing skills | `skills_manager.py` | Enable/disable/search skills |
312
-
313
- ### Master Scripts
314
-
315
- ```bash
316
- # Quick check during development
317
- python3 .agent/scripts/checklist.py .
318
-
319
- # Full check with performance audits
320
- python3 .agent/scripts/checklist.py . --url http://localhost:3000
321
-
322
- # Pre-deployment verification
323
- python3 .agent/scripts/verify_all.py . --url http://localhost:3000
324
-
325
- # Kit status
326
- python3 .agent/scripts/kit_status.py --validate
327
-
328
- # Skill management
329
- python3 .agent/scripts/skills_manager.py list
330
- python3 .agent/scripts/skills_manager.py search <query>
331
- ```
332
-
333
- ### Skill-Specific Scripts
334
-
335
- | Skill | Script | When to Use |
336
- | ------------------------ | --------------------- | -------------------------------- |
337
- | `clean-code` | `lint_runner.py` | After code changes |
338
- | `testing-patterns` | `test_runner.py` | After logic changes |
339
- | `security-fundamentals` | `security_scan.py` | Before deploy, after deps change |
340
- | `database-design` | `schema_validator.py` | After schema changes |
341
- | `api-patterns` | `api_validator.py` | After API changes |
342
- | `i18n-localization` | `i18n_checker.py` | After UI text changes |
343
- | `seo-patterns` | `seo_checker.py` | After page changes |
344
- | `accessibility-patterns` | `a11y_checker.py` | After UI changes |
345
-
346
- ### AI Script Protocol
347
-
348
- 1. **Security changes** β†’ Run `security_scan.py`
349
- 2. **Database changes** β†’ Run `schema_validator.py`
350
- 3. **API changes** β†’ Run `api_validator.py`
351
- 4. **UI changes** β†’ Run `a11y_checker.py`
352
- 5. **Before suggesting deploy** β†’ Run `verify_all.py`
353
-
354
- > πŸ”΄ Full script documentation: See `.agent/ARCHITECTURE.md` β†’ Scripts section
355
-
356
- ---
357
-
358
- ## πŸ“Š Kit Statistics
359
-
360
- | Metric | Count |
361
- | --------- | ----- |
362
- | Agents | 22 |
363
- | Skills | 40 |
364
- | Workflows | 7 |
365
- | Scripts | 19 |
41
+ [INCLUDE:scripts.md]
366
42
 
367
43
  ---
368
44
 
369
- > **Philosophy:** Modular agents + reusable skills + clear workflows + automated scripts = scalable AI assistance.
45
+ [INCLUDE:footer.md]
@@ -0,0 +1,9 @@
1
+ ## πŸ“₯ REQUEST CLASSIFIER
2
+
3
+ - QUESTION ("what is", "explain") β†’ no agent
4
+ - PLAN ("plan", "lαΊ­p kαΊΏ hoαΊ‘ch") β†’ `project-planner`
5
+ - CREATE ("create", "build", "tαΊ‘o") β†’ `orchestrator` β†’ specialists
6
+ - DEBUG ("debug", "fix", "gα»‘ lα»—i") β†’ `debugger`
7
+ - TEST ("test", "kiểm tra") β†’ `test-engineer`
8
+ - DEPLOY ("deploy", "release") β†’ `devops-engineer`
9
+ - COMPLEX (multi-domain) β†’ `orchestrator` (3+ agents)
@@ -0,0 +1,20 @@
1
+ ## TIER 1: CODE RULES
2
+
3
+ **Project Routing:**
4
+ - MOBILE (iOS/Android/RN/Flutter) β†’ `mobile-developer` + `mobile-design` skill
5
+ - WEB (Next.js/React) β†’ `frontend-specialist` + `frontend-design` skill
6
+ - BACKEND (API/DB) β†’ `backend-specialist` + `api-patterns`, `database-design` skills
7
+
8
+ > πŸ”΄ Mobile + frontend-specialist = WRONG.
9
+
10
+ **Socratic Gate β€” STOP and ASK first when:**
11
+ - New Feature/Build β†’ ask 3+ strategic questions
12
+ - Vague Request β†’ ask Purpose, Users, Scope
13
+ - Full Orchestration β†’ user must confirm plan before Phase 2
14
+
15
+ **Never Assume.** If 1% unclear β†’ ASK.
16
+
17
+ **Mode Mapping:**
18
+ - `plan` β†’ project-planner (4-phase, NO CODE before Phase 4)
19
+ - `ask` β†’ questions only
20
+ - `edit` β†’ orchestrator (check `{task-slug}.md` first)
@@ -0,0 +1,3 @@
1
+ ## TIER 2: DESIGN RULES
2
+
3
+ > Rules in specialist agents: Web β†’ `frontend-specialist.md`, Mobile β†’ `mobile-developer.md`
@@ -0,0 +1 @@
1
+ > **Philosophy:** Modular agents + reusable skills + clear workflows = scalable AI assistance.
@@ -0,0 +1,20 @@
1
+ ## πŸ€– AGENT ROUTING & CLASSIFICATION
2
+
3
+ Protocol: Analyze Request β†’ Select Specialist β†’ Announce (Only on change/start) β†’ Execute.
4
+
5
+ ### πŸ“’ Announcement Protocol
6
+ - Announce only when you **switch** to a different agent or start a **new task context**.
7
+ - If you are already active as an agent, do **NOT** repeat the activation line in every message.
8
+ - Format: `πŸ€– **@agent-name activated!**` (localized to conversation language).
9
+
10
+ ### 🏷️ Request Classification
11
+ [INCLUDE:classifier.md]
12
+
13
+ ### πŸ‘₯ Specialist Tiers
14
+ - **T1-Master:** `orchestrator` (complex) Β· `project-planner` (plans) Β· `debugger` (fixes)
15
+ - **T2-Dev:** `frontend-specialist`, `backend-specialist`, `mobile-developer`, `database-specialist`, `devops-engineer`
16
+ - **T3-Quality:** `security-auditor`, `code-reviewer`, `test-engineer`, `performance-analyst`
17
+ - **T4-Support:** `documentation-writer`, `i18n-specialist`, `ux-researcher`
18
+ - **Domain:** `realtime-specialist`, `multi-tenant-architect`, `ai-engineer`, `cloud-architect`
19
+
20
+ **Routing Checklist:** β‘  Identify specialist β‘‘ Announce IF change/start β‘’ Load agent-specific skills.
@@ -0,0 +1,11 @@
1
+ ## πŸ“œ SCRIPTS (Automation)
2
+
3
+ **When to run:**
4
+ - Before PR/commit β†’ `checklist.py` (Security, Lint, Tests)
5
+ - Before deploy β†’ `verify_all.py`
6
+ - Security changes β†’ `security_scan.py`
7
+ - DB changes β†’ `schema_validator.py`
8
+ - API changes β†’ `api_validator.py`
9
+ - UI changes β†’ `a11y_checker.py`
10
+
11
+ > Full script docs: `ARCHITECTURE.md` β†’ Scripts section
@@ -0,0 +1,11 @@
1
+ ## πŸ› οΈ SKILL LOADING PROTOCOL
2
+
3
+ `User Request β†’ Check Profile β†’ Match Skill β†’ Read SKILL.md β†’ Apply`
4
+
5
+ Check `.agent/profile.json` first:
6
+ - EXISTS β†’ respect `skills.enabled[]`, `skills.disabled[]`, `agents.disabled[]`
7
+ - NOT EXISTS β†’ all skills/agents enabled by default
8
+
9
+ **Core Skills (never disabled):** `clean-code` Β· `testing-patterns` Β· `security-fundamentals` Β· `brainstorming` Β· `plan-writing` Β· `systematic-debugging`
10
+
11
+ > Full skill list: `ARCHITECTURE.md` β†’ Skills section
@@ -0,0 +1,23 @@
1
+ ## πŸ› οΈ SKILL LOADING PROTOCOL (OpenCode)
2
+
3
+ `Agent activated β†’ Check ARCHITECTURE.md for assigned skills β†’ Call skill({ name }) β†’ Apply`
4
+
5
+ OpenCode has a **native `skill` tool** that auto-discovers all available skills from `.agent/skills/*/SKILL.md`.
6
+
7
+ **Steps:**
8
+ 1. Read ARCHITECTURE.md β†’ find your agent β†’ note "Skills Used" column
9
+ 2. Call `skill({ name: "skill-name" })` for each assigned skill
10
+ 3. Apply all loaded skill rules
11
+
12
+ **Skill Permissions** (in `opencode.json`):
13
+ ```json
14
+ { "permission": { "skill": { "*": "allow" } } }
15
+ ```
16
+
17
+ Check `.agent/profile.json` first:
18
+ - EXISTS β†’ respect `skills.enabled[]`, `skills.disabled[]`, `agents.disabled[]`
19
+ - NOT EXISTS β†’ all skills/agents enabled by default
20
+
21
+ **Core Skills (never disabled):** `clean-code` Β· `testing-patterns` Β· `security-fundamentals` Β· `brainstorming` Β· `plan-writing` Β· `systematic-debugging`
22
+
23
+ > Full skill list: `.agent/ARCHITECTURE.md` β†’ Skills section
@@ -0,0 +1,9 @@
1
+ ## TIER 0: UNIVERSAL RULES
2
+
3
+ **Language:** Non-English prompt β†’ respond in user's language. Code/vars/filenames β†’ always English (kebab-case).
4
+
5
+ **Clean Code:** Concise, self-documenting, no over-engineering. Testing: Pyramid (Unit > Int > E2E) + AAA. Performance: measure first.
6
+
7
+ **System Map:** Agents `.agent/agents/` Β· Skills `.agent/skills/` Β· Workflows `.agent/workflows/`
8
+
9
+ > Read `ARCHITECTURE.md` only when you need full agent/skill details.
@@ -0,0 +1,5 @@
1
+ ## πŸ“œ COMMANDS (Slash Commands)
2
+
3
+ > In Cursor, workflows are called "commands" and stored in `.cursor/commands/`
4
+
5
+ `/plan` β†’ project-planner Β· `/create` β†’ orchestrator Β· `/debug` β†’ debugger Β· `/test` β†’ test-engineer Β· `/deploy` β†’ devops-engineer Β· `/orchestrate` β†’ orchestrator (3+ agents)
@@ -0,0 +1,3 @@
1
+ ## πŸ“œ WORKFLOWS (Slash Commands)
2
+
3
+ `/plan` β†’ project-planner Β· `/create` β†’ orchestrator Β· `/debug` β†’ debugger Β· `/test` β†’ test-engineer Β· `/deploy` β†’ devops-engineer Β· `/orchestrate` β†’ orchestrator (3+ agents)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@neyugn/agent-kits",
3
- "version": "0.3.9",
3
+ "version": "0.5.0",
4
4
  "description": "Universal AI Agent Toolkit - Skills, Agents, and Workflows for any AI coding assistant",
5
5
  "type": "module",
6
6
  "bin": {