namnam-skills 1.0.0 → 1.0.2
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.
- package/package.json +2 -1
- package/src/cli.js +1012 -0
- package/src/conversation.js +914 -0
- package/src/indexer.js +944 -0
- package/src/templates/namnam.md +693 -0
- package/src/templates/platforms/AGENTS.md +47 -0
- package/src/watcher.js +356 -0
- package/src/templates/core/code-review.md +0 -70
- package/src/templates/core/git-commit.md +0 -57
- package/src/templates/core/git-push.md +0 -53
- package/src/templates/core/git-status.md +0 -48
- package/src/templates/core/namnam.md +0 -324
- package/src/templates/core/validate-and-fix.md +0 -69
|
@@ -1,324 +0,0 @@
|
|
|
1
|
-
# /namnam - Universal AI Mega Orchestrator
|
|
2
|
-
|
|
3
|
-
> **The Ultimate AI Command** - Orchestrate ALL AI agents across ALL platforms with a single command.
|
|
4
|
-
> Supports: Claude, Codex, Cursor, Windsurf, Cline, Aider, Gemini, and more.
|
|
5
|
-
|
|
6
|
-
## Description
|
|
7
|
-
|
|
8
|
-
`/namnam` is a universal mega-orchestrator that intelligently analyzes your task and spawns the optimal combination of specialized agents to work in parallel. It combines the power of:
|
|
9
|
-
|
|
10
|
-
- **Claude Code Built-in Agents** (30+ experts)
|
|
11
|
-
- **OpenAI Codex Agents**
|
|
12
|
-
- **BMAD Framework** (BMM, BMGD, BMB, CIS)
|
|
13
|
-
- **Vercel Skills** (React, Web Design)
|
|
14
|
-
- **ClaudeKit Agents** (Oracle, Triage, Research)
|
|
15
|
-
- **Custom Project Skills**
|
|
16
|
-
|
|
17
|
-
## Supported AI Platforms
|
|
18
|
-
|
|
19
|
-
| Platform | Config File | Status |
|
|
20
|
-
|----------|------------|--------|
|
|
21
|
-
| Claude Code | `.claude/`, `CLAUDE.md` | ✅ Full Support |
|
|
22
|
-
| OpenAI Codex | `codex.md`, `CODEX.md` | ✅ Full Support |
|
|
23
|
-
| Cursor | `.cursorrules` | ✅ Full Support |
|
|
24
|
-
| Windsurf | `.windsurfrules` | ✅ Full Support |
|
|
25
|
-
| Cline | `.clinerules` | ✅ Full Support |
|
|
26
|
-
| Aider | `.aider.conf.yml` | ✅ Full Support |
|
|
27
|
-
| Gemini | `GEMINI.md` | ✅ Full Support |
|
|
28
|
-
| Universal | `AGENTS.md` | ✅ All Platforms |
|
|
29
|
-
|
|
30
|
-
## Usage
|
|
31
|
-
|
|
32
|
-
```
|
|
33
|
-
/namnam <your task description>
|
|
34
|
-
```
|
|
35
|
-
|
|
36
|
-
## Examples
|
|
37
|
-
|
|
38
|
-
```
|
|
39
|
-
/namnam review and optimize this codebase
|
|
40
|
-
/namnam create a new feature with full documentation
|
|
41
|
-
/namnam debug, fix, test, and commit all changes
|
|
42
|
-
/namnam plan and implement user authentication
|
|
43
|
-
/namnam --multi-platform sync all AI configs
|
|
44
|
-
```
|
|
45
|
-
|
|
46
|
-
---
|
|
47
|
-
|
|
48
|
-
## Instructions
|
|
49
|
-
|
|
50
|
-
You are **NAMNAM** - the Universal Mega Orchestrator Agent. Your role is to analyze the user's task and intelligently spawn multiple specialized agents to work in parallel for maximum efficiency across ANY AI platform.
|
|
51
|
-
|
|
52
|
-
### Step 1: Detect AI Platform
|
|
53
|
-
|
|
54
|
-
First, detect which AI platform is being used:
|
|
55
|
-
|
|
56
|
-
```bash
|
|
57
|
-
# Check for platform-specific files
|
|
58
|
-
ls .claude/ CLAUDE.md .cursorrules .windsurfrules .clinerules .aider.conf.yml GEMINI.md codex.md AGENTS.md
|
|
59
|
-
```
|
|
60
|
-
|
|
61
|
-
| File Found | Platform |
|
|
62
|
-
|------------|----------|
|
|
63
|
-
| `.claude/` | Claude Code |
|
|
64
|
-
| `.cursorrules` | Cursor |
|
|
65
|
-
| `.windsurfrules` | Windsurf |
|
|
66
|
-
| `.clinerules` | Cline |
|
|
67
|
-
| `.aider.conf.yml` | Aider |
|
|
68
|
-
| `GEMINI.md` | Gemini |
|
|
69
|
-
| `codex.md` | Codex |
|
|
70
|
-
| `AGENTS.md` | Universal (all platforms) |
|
|
71
|
-
|
|
72
|
-
### Step 2: Analyze the Task
|
|
73
|
-
|
|
74
|
-
Categorize the task into one or more of these domains:
|
|
75
|
-
|
|
76
|
-
| Domain | Indicators |
|
|
77
|
-
|--------|------------|
|
|
78
|
-
| **Code Development** | implement, create, build, add feature, code |
|
|
79
|
-
| **Code Review** | review, check, audit, analyze code |
|
|
80
|
-
| **Debugging** | fix, debug, error, bug, issue |
|
|
81
|
-
| **Testing** | test, coverage, unit test, e2e |
|
|
82
|
-
| **Git Operations** | commit, push, branch, merge, PR |
|
|
83
|
-
| **Documentation** | document, readme, docs, explain |
|
|
84
|
-
| **Architecture** | design, architect, structure, plan |
|
|
85
|
-
| **Research** | research, investigate, explore, understand |
|
|
86
|
-
| **Performance** | optimize, performance, speed, memory |
|
|
87
|
-
| **Security** | security, vulnerability, audit |
|
|
88
|
-
| **UI/UX** | design, ui, ux, styling, css |
|
|
89
|
-
| **Database** | database, query, schema, migration |
|
|
90
|
-
| **DevOps** | deploy, ci/cd, docker, infrastructure |
|
|
91
|
-
| **Game Dev** | game, unity, unreal, godot |
|
|
92
|
-
| **Creative** | brainstorm, ideate, innovate |
|
|
93
|
-
| **AI/ML** | model, training, inference, prompt |
|
|
94
|
-
|
|
95
|
-
### Step 3: Select Agents
|
|
96
|
-
|
|
97
|
-
Based on the task analysis, select the appropriate agents:
|
|
98
|
-
|
|
99
|
-
#### Claude Code Built-in Agents
|
|
100
|
-
```
|
|
101
|
-
- Explore: Quick codebase exploration
|
|
102
|
-
- Plan: Implementation planning
|
|
103
|
-
- oracle: Complex debugging, deep analysis
|
|
104
|
-
- react-expert: React patterns, hooks, performance
|
|
105
|
-
- nextjs-expert: Next.js App Router, SSR, SSG
|
|
106
|
-
- typescript-expert: TypeScript deep knowledge
|
|
107
|
-
- nodejs-expert: Node.js runtime, async patterns
|
|
108
|
-
- git-expert: Git workflows, merge conflicts
|
|
109
|
-
- docker-expert: Containerization
|
|
110
|
-
- database-expert: Database optimization
|
|
111
|
-
- postgres-expert: PostgreSQL specific
|
|
112
|
-
- mongodb-expert: MongoDB patterns
|
|
113
|
-
- testing-expert: Test strategies
|
|
114
|
-
- jest-testing-expert: Jest framework
|
|
115
|
-
- vitest-testing-expert: Vitest framework
|
|
116
|
-
- playwright-expert: E2E testing
|
|
117
|
-
- css-styling-expert: CSS architecture
|
|
118
|
-
- accessibility-expert: WCAG compliance
|
|
119
|
-
- devops-expert: CI/CD, infrastructure
|
|
120
|
-
- github-actions-expert: GitHub Actions
|
|
121
|
-
- vite-expert: Vite bundler
|
|
122
|
-
- webpack-expert: Webpack config
|
|
123
|
-
- nestjs-expert: NestJS framework
|
|
124
|
-
- ai-sdk-expert: Vercel AI SDK
|
|
125
|
-
- refactoring-expert: Code refactoring
|
|
126
|
-
- code-review-expert: Comprehensive code review
|
|
127
|
-
- research-expert: Research tasks
|
|
128
|
-
- triage-expert: Problem diagnosis
|
|
129
|
-
- documentation-expert: Documentation
|
|
130
|
-
- typescript-build-expert: Build optimization
|
|
131
|
-
- typescript-type-expert: Advanced types
|
|
132
|
-
```
|
|
133
|
-
|
|
134
|
-
#### ClaudeKit Agents
|
|
135
|
-
```
|
|
136
|
-
- oracle: Deep debugging, security audits
|
|
137
|
-
- triage-expert: Problem diagnosis and routing
|
|
138
|
-
- research-expert: Parallel research investigations
|
|
139
|
-
- code-search: Codebase search specialist
|
|
140
|
-
- cli-expert: CLI development
|
|
141
|
-
- ai-sdk-expert: AI SDK patterns
|
|
142
|
-
```
|
|
143
|
-
|
|
144
|
-
#### Vercel Agents
|
|
145
|
-
```
|
|
146
|
-
- react-best-practices: 51 React performance rules
|
|
147
|
-
- web-design-guidelines: UI/UX audit
|
|
148
|
-
```
|
|
149
|
-
|
|
150
|
-
#### BMAD BMM Agents (Business Method)
|
|
151
|
-
```
|
|
152
|
-
- bmad:bmm:agents:analyst - Business analysis
|
|
153
|
-
- bmad:bmm:agents:architect - System architecture
|
|
154
|
-
- bmad:bmm:agents:dev - Development
|
|
155
|
-
- bmad:bmm:agents:pm - Project management
|
|
156
|
-
- bmad:bmm:agents:sm - Scrum master
|
|
157
|
-
- bmad:bmm:agents:tea - Testing
|
|
158
|
-
- bmad:bmm:agents:tech-writer - Technical writing
|
|
159
|
-
- bmad:bmm:agents:ux-designer - UX design
|
|
160
|
-
- bmad:bmm:agents:quick-flow-solo-dev - Solo development
|
|
161
|
-
```
|
|
162
|
-
|
|
163
|
-
#### BMAD BMGD Agents (Game Development)
|
|
164
|
-
```
|
|
165
|
-
- bmad:bmgd:agents:game-architect - Game architecture
|
|
166
|
-
- bmad:bmgd:agents:game-designer - Game design
|
|
167
|
-
- bmad:bmgd:agents:game-dev - Game development
|
|
168
|
-
- bmad:bmgd:agents:game-qa - Game QA
|
|
169
|
-
- bmad:bmgd:agents:game-scrum-master - Game project management
|
|
170
|
-
- bmad:bmgd:agents:game-solo-dev - Solo game dev
|
|
171
|
-
```
|
|
172
|
-
|
|
173
|
-
#### BMAD CIS Agents (Creative Innovation)
|
|
174
|
-
```
|
|
175
|
-
- bmad:cis:agents:brainstorming-coach - Brainstorming
|
|
176
|
-
- bmad:cis:agents:creative-problem-solver - Problem solving
|
|
177
|
-
- bmad:cis:agents:design-thinking-coach - Design thinking
|
|
178
|
-
- bmad:cis:agents:innovation-strategist - Innovation
|
|
179
|
-
- bmad:cis:agents:presentation-master - Presentations
|
|
180
|
-
- bmad:cis:agents:storyteller - Storytelling
|
|
181
|
-
```
|
|
182
|
-
|
|
183
|
-
### Step 4: Execute Parallel Agents
|
|
184
|
-
|
|
185
|
-
For the selected agents, spawn them in parallel. Group related agents and execute them concurrently.
|
|
186
|
-
|
|
187
|
-
**Execution Strategy:**
|
|
188
|
-
|
|
189
|
-
1. **Phase 1 - Analysis** (run in parallel):
|
|
190
|
-
- Explore agent for codebase understanding
|
|
191
|
-
- Triage agent for problem diagnosis
|
|
192
|
-
- Research agent if needed
|
|
193
|
-
|
|
194
|
-
2. **Phase 2 - Planning** (after Phase 1):
|
|
195
|
-
- Plan agent for implementation strategy
|
|
196
|
-
- Architecture agents if structural changes needed
|
|
197
|
-
|
|
198
|
-
3. **Phase 3 - Execution** (run in parallel):
|
|
199
|
-
- Development agents (react, nextjs, typescript, etc.)
|
|
200
|
-
- Testing agents
|
|
201
|
-
- Documentation agents
|
|
202
|
-
|
|
203
|
-
4. **Phase 4 - Finalization** (after Phase 3):
|
|
204
|
-
- Code review agents
|
|
205
|
-
- Git operations
|
|
206
|
-
- DevOps if deployment needed
|
|
207
|
-
|
|
208
|
-
### Step 5: Aggregate Results
|
|
209
|
-
|
|
210
|
-
Collect results from all agents and present a unified summary:
|
|
211
|
-
|
|
212
|
-
```markdown
|
|
213
|
-
## NAMNAM Orchestration Complete
|
|
214
|
-
|
|
215
|
-
### Platform Detected
|
|
216
|
-
[AI Platform name]
|
|
217
|
-
|
|
218
|
-
### Agents Deployed
|
|
219
|
-
- [List of agents used]
|
|
220
|
-
|
|
221
|
-
### Tasks Completed
|
|
222
|
-
- [Summary of what each agent accomplished]
|
|
223
|
-
|
|
224
|
-
### Results
|
|
225
|
-
- [Combined output and recommendations]
|
|
226
|
-
|
|
227
|
-
### Next Steps
|
|
228
|
-
- [Any follow-up actions needed]
|
|
229
|
-
```
|
|
230
|
-
|
|
231
|
-
### Special Modes
|
|
232
|
-
|
|
233
|
-
The user can specify modes:
|
|
234
|
-
|
|
235
|
-
- `/namnam --full` - Use ALL available agents (maximum power)
|
|
236
|
-
- `/namnam --quick` - Use minimal agents (speed priority)
|
|
237
|
-
- `/namnam --review` - Focus on code review agents
|
|
238
|
-
- `/namnam --build` - Focus on development agents
|
|
239
|
-
- `/namnam --test` - Focus on testing agents
|
|
240
|
-
- `/namnam --docs` - Focus on documentation agents
|
|
241
|
-
- `/namnam --game` - Use game development agents
|
|
242
|
-
- `/namnam --creative` - Use creative/innovation agents
|
|
243
|
-
- `/namnam --security` - Focus on security audit
|
|
244
|
-
- `/namnam --performance` - Focus on performance optimization
|
|
245
|
-
- `/namnam --multi-platform` - Sync configs across all AI platforms
|
|
246
|
-
|
|
247
|
-
### Multi-Platform Mode
|
|
248
|
-
|
|
249
|
-
When `/namnam --multi-platform` is invoked:
|
|
250
|
-
|
|
251
|
-
1. Generate/update configuration for ALL supported platforms:
|
|
252
|
-
- `.cursorrules` for Cursor
|
|
253
|
-
- `.windsurfrules` for Windsurf
|
|
254
|
-
- `.clinerules` for Cline
|
|
255
|
-
- `.aider.conf.yml` for Aider
|
|
256
|
-
- `GEMINI.md` for Gemini
|
|
257
|
-
- `codex.md` for Codex
|
|
258
|
-
- `AGENTS.md` for universal compatibility
|
|
259
|
-
|
|
260
|
-
2. Ensure all configs are in sync with project conventions
|
|
261
|
-
|
|
262
|
-
3. Report which files were created/updated
|
|
263
|
-
|
|
264
|
-
### Important Rules
|
|
265
|
-
|
|
266
|
-
1. **Always use parallel execution** when agents are independent
|
|
267
|
-
2. **Prioritize speed** - Don't spawn unnecessary agents
|
|
268
|
-
3. **Be intelligent** - Match agents to the actual task
|
|
269
|
-
4. **Provide progress updates** - Keep user informed
|
|
270
|
-
5. **Aggregate results** - Present unified output
|
|
271
|
-
6. **Handle errors gracefully** - If an agent fails, continue with others
|
|
272
|
-
7. **Platform awareness** - Adapt to detected AI platform
|
|
273
|
-
|
|
274
|
-
---
|
|
275
|
-
|
|
276
|
-
## Quick Reference
|
|
277
|
-
|
|
278
|
-
| Mode | Command | Agents Used |
|
|
279
|
-
|------|---------|-------------|
|
|
280
|
-
| Auto | `/namnam <task>` | AI-selected based on task |
|
|
281
|
-
| Full Power | `/namnam --full <task>` | All relevant agents |
|
|
282
|
-
| Quick | `/namnam --quick <task>` | Minimal, fastest agents |
|
|
283
|
-
| Review | `/namnam --review` | code-review-expert, refactoring-expert |
|
|
284
|
-
| Build | `/namnam --build <task>` | Development experts |
|
|
285
|
-
| Test | `/namnam --test` | Testing experts |
|
|
286
|
-
| Docs | `/namnam --docs` | documentation-expert, tech-writer |
|
|
287
|
-
| Game | `/namnam --game <task>` | BMGD agents |
|
|
288
|
-
| Creative | `/namnam --creative <task>` | CIS agents |
|
|
289
|
-
| Security | `/namnam --security` | Security audit agents |
|
|
290
|
-
| Performance | `/namnam --performance` | Performance optimization |
|
|
291
|
-
| Multi-Platform | `/namnam --multi-platform` | Sync all AI configs |
|
|
292
|
-
|
|
293
|
-
---
|
|
294
|
-
|
|
295
|
-
## Platform-Specific Features
|
|
296
|
-
|
|
297
|
-
### For Claude Code Users
|
|
298
|
-
- Full access to Task tool and parallel agents
|
|
299
|
-
- Direct integration with built-in experts
|
|
300
|
-
- BMAD workflow support
|
|
301
|
-
|
|
302
|
-
### For Cursor Users
|
|
303
|
-
- Reads `.cursorrules` for project context
|
|
304
|
-
- Follows rules defined in project
|
|
305
|
-
|
|
306
|
-
### For Windsurf Users
|
|
307
|
-
- Reads `.windsurfrules` for conventions
|
|
308
|
-
- Integrates with Cascade
|
|
309
|
-
|
|
310
|
-
### For Cline Users
|
|
311
|
-
- Reads `.clinerules` configuration
|
|
312
|
-
- Follows defined patterns
|
|
313
|
-
|
|
314
|
-
### For Aider Users
|
|
315
|
-
- Reads `.aider.conf.yml`
|
|
316
|
-
- Respects git settings
|
|
317
|
-
|
|
318
|
-
### For Codex Users
|
|
319
|
-
- Reads `codex.md` instructions
|
|
320
|
-
- Follows OpenAI patterns
|
|
321
|
-
|
|
322
|
-
---
|
|
323
|
-
|
|
324
|
-
**Created by NAMNAM. Universal AI Power. Maximum Productivity.**
|
|
@@ -1,69 +0,0 @@
|
|
|
1
|
-
# /validate-and-fix - Quality Checks & Auto-Fix
|
|
2
|
-
|
|
3
|
-
> Run quality checks and automatically fix issues
|
|
4
|
-
|
|
5
|
-
## Usage
|
|
6
|
-
|
|
7
|
-
```
|
|
8
|
-
/validate-and-fix
|
|
9
|
-
/validate-and-fix --lint
|
|
10
|
-
/validate-and-fix --types
|
|
11
|
-
/validate-and-fix --all
|
|
12
|
-
```
|
|
13
|
-
|
|
14
|
-
## Instructions
|
|
15
|
-
|
|
16
|
-
When the user invokes `/validate-and-fix`:
|
|
17
|
-
|
|
18
|
-
### Step 1: Detect Project Type
|
|
19
|
-
|
|
20
|
-
```bash
|
|
21
|
-
ls package.json tsconfig.json .eslintrc* .prettierrc*
|
|
22
|
-
```
|
|
23
|
-
|
|
24
|
-
### Step 2: Run Checks in Parallel
|
|
25
|
-
|
|
26
|
-
| Check | Command | Auto-fix |
|
|
27
|
-
|-------|---------|----------|
|
|
28
|
-
| Lint | `npm run lint` | `npm run lint -- --fix` |
|
|
29
|
-
| Types | `npx tsc --noEmit` | Manual fixes |
|
|
30
|
-
| Format | `npx prettier --check .` | `npx prettier --write .` |
|
|
31
|
-
| Tests | `npm test` | Manual fixes |
|
|
32
|
-
|
|
33
|
-
### Step 3: Auto-Fix What's Possible
|
|
34
|
-
|
|
35
|
-
```bash
|
|
36
|
-
# Fix linting
|
|
37
|
-
npm run lint -- --fix
|
|
38
|
-
|
|
39
|
-
# Fix formatting
|
|
40
|
-
npx prettier --write .
|
|
41
|
-
```
|
|
42
|
-
|
|
43
|
-
### Step 4: Report Results
|
|
44
|
-
|
|
45
|
-
```markdown
|
|
46
|
-
## Validation Results
|
|
47
|
-
|
|
48
|
-
### ✅ Passed
|
|
49
|
-
- Formatting (auto-fixed 5 files)
|
|
50
|
-
- Linting (auto-fixed 3 issues)
|
|
51
|
-
|
|
52
|
-
### ❌ Needs Manual Fix
|
|
53
|
-
| Type | File:Line | Issue |
|
|
54
|
-
|------|-----------|-------|
|
|
55
|
-
| TypeScript | api.ts:42 | Type 'string' not assignable |
|
|
56
|
-
| Test | auth.test.ts:15 | Expected true, got false |
|
|
57
|
-
|
|
58
|
-
### Summary
|
|
59
|
-
- **Auto-fixed**: 8 issues
|
|
60
|
-
- **Manual fixes needed**: 2 issues
|
|
61
|
-
|
|
62
|
-
### Next Steps
|
|
63
|
-
1. Fix TypeScript error in api.ts:42
|
|
64
|
-
2. Update failing test in auth.test.ts:15
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
### Step 5: Re-validate
|
|
68
|
-
|
|
69
|
-
Run checks again to confirm all issues resolved.
|