@su-record/vibe 2.6.41 → 2.6.43
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/.env +1 -1
- package/commands/vibe.analyze.md +373 -373
- package/commands/vibe.reason.md +333 -333
- package/commands/vibe.review.md +555 -555
- package/commands/vibe.run.md +1922 -1922
- package/commands/vibe.spec.md +1195 -1195
- package/commands/vibe.trace.md +209 -209
- package/commands/vibe.verify.md +414 -414
- package/dist/cli/postinstall/inline-skills.js +1 -1
- package/dist/cli/postinstall/inline-skills.js.map +1 -1
- package/dist/cli/setup/GlobalInstaller.d.ts +7 -0
- package/dist/cli/setup/GlobalInstaller.d.ts.map +1 -1
- package/dist/cli/setup/GlobalInstaller.js +45 -0
- package/dist/cli/setup/GlobalInstaller.js.map +1 -1
- package/dist/infra/lib/SkillRepository.d.ts.map +1 -1
- package/dist/infra/lib/SkillRepository.js +5 -4
- package/dist/infra/lib/SkillRepository.js.map +1 -1
- package/dist/infra/lib/gpt/constants.d.ts +1 -1
- package/dist/infra/lib/gpt/constants.d.ts.map +1 -1
- package/dist/infra/lib/gpt/constants.js +1 -1
- package/dist/infra/lib/gpt/constants.js.map +1 -1
- package/package.json +2 -2
- package/skills/core-capabilities/SKILL.md +164 -164
- package/skills/parallel-research/SKILL.md +80 -80
|
@@ -1,80 +1,80 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: parallel-research
|
|
3
|
-
description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
|
|
4
|
-
triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
|
|
5
|
-
priority: 60
|
|
6
|
-
---
|
|
7
|
-
# Parallel Research
|
|
8
|
-
|
|
9
|
-
Parallel research patterns for solving complex problems.
|
|
10
|
-
|
|
11
|
-
## When Parallel Research is Needed
|
|
12
|
-
|
|
13
|
-
| Situation | Reason |
|
|
14
|
-
|-----------|--------|
|
|
15
|
-
| New technology adoption | Need best practices |
|
|
16
|
-
| Security-related features | Multi-angle review needed |
|
|
17
|
-
| Architecture design | Multiple perspectives needed |
|
|
18
|
-
| Technology selection | Comparison analysis needed |
|
|
19
|
-
| Complex bugs | Explore multiple causes |
|
|
20
|
-
|
|
21
|
-
## Research Agents (4 Parallel)
|
|
22
|
-
|
|
23
|
-
| Agent | Role | Tools |
|
|
24
|
-
|-------|------|-------|
|
|
25
|
-
| best-practices | Search best practices | Web Search, context7 |
|
|
26
|
-
| framework-docs | Search official docs | context7 |
|
|
27
|
-
| codebase-patterns | Analyze existing code patterns | Grep, Glob |
|
|
28
|
-
| security-advisory | Search security advisories | Web Search |
|
|
29
|
-
|
|
30
|
-
## Usage Methods
|
|
31
|
-
|
|
32
|
-
### Method 1: Direct Orchestrator Call
|
|
33
|
-
|
|
34
|
-
```bash
|
|
35
|
-
node -e "import('
|
|
36
|
-
o.research('passkey authentication', ['React', 'Supabase'])
|
|
37
|
-
.then(r => console.log(r.content[0].text))
|
|
38
|
-
)"
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
### Method 2: Use /vibe.spec
|
|
42
|
-
|
|
43
|
-
```
|
|
44
|
-
/vibe.spec "feature-name"
|
|
45
|
-
→ Parallel research runs automatically after requirements confirmed
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
### Method 3: Parallel Task Tool Execution
|
|
49
|
-
|
|
50
|
-
```
|
|
51
|
-
Task 1: "Search React auth best practices"
|
|
52
|
-
Task 2: "Search Supabase Auth official docs" (concurrent)
|
|
53
|
-
Task 3: "Analyze existing auth code patterns" (concurrent)
|
|
54
|
-
Task 4: "Search auth security vulnerabilities" (concurrent)
|
|
55
|
-
```
|
|
56
|
-
|
|
57
|
-
## Using Research Results
|
|
58
|
-
|
|
59
|
-
```
|
|
60
|
-
Parallel research complete
|
|
61
|
-
↓
|
|
62
|
-
Synthesize results
|
|
63
|
-
↓
|
|
64
|
-
Reflect in SPEC Context section
|
|
65
|
-
OR
|
|
66
|
-
Reference during implementation
|
|
67
|
-
```
|
|
68
|
-
|
|
69
|
-
## When Research is NOT Needed
|
|
70
|
-
|
|
71
|
-
- Simple CRUD operations
|
|
72
|
-
- Already familiar patterns
|
|
73
|
-
- Similar code exists in project
|
|
74
|
-
- Time-critical (supplement with review later)
|
|
75
|
-
|
|
76
|
-
## Notes
|
|
77
|
-
|
|
78
|
-
- Research runs **after requirements confirmed**
|
|
79
|
-
- Split overly broad topics
|
|
80
|
-
- Research results are references, not absolute truth
|
|
1
|
+
---
|
|
2
|
+
name: parallel-research
|
|
3
|
+
description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
|
|
4
|
+
triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
|
|
5
|
+
priority: 60
|
|
6
|
+
---
|
|
7
|
+
# Parallel Research
|
|
8
|
+
|
|
9
|
+
Parallel research patterns for solving complex problems.
|
|
10
|
+
|
|
11
|
+
## When Parallel Research is Needed
|
|
12
|
+
|
|
13
|
+
| Situation | Reason |
|
|
14
|
+
|-----------|--------|
|
|
15
|
+
| New technology adoption | Need best practices |
|
|
16
|
+
| Security-related features | Multi-angle review needed |
|
|
17
|
+
| Architecture design | Multiple perspectives needed |
|
|
18
|
+
| Technology selection | Comparison analysis needed |
|
|
19
|
+
| Complex bugs | Explore multiple causes |
|
|
20
|
+
|
|
21
|
+
## Research Agents (4 Parallel)
|
|
22
|
+
|
|
23
|
+
| Agent | Role | Tools |
|
|
24
|
+
|-------|------|-------|
|
|
25
|
+
| best-practices | Search best practices | Web Search, context7 |
|
|
26
|
+
| framework-docs | Search official docs | context7 |
|
|
27
|
+
| codebase-patterns | Analyze existing code patterns | Grep, Glob |
|
|
28
|
+
| security-advisory | Search security advisories | Web Search |
|
|
29
|
+
|
|
30
|
+
## Usage Methods
|
|
31
|
+
|
|
32
|
+
### Method 1: Direct Orchestrator Call
|
|
33
|
+
|
|
34
|
+
```bash
|
|
35
|
+
node -e "import('{{CORE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').then(o =>
|
|
36
|
+
o.research('passkey authentication', ['React', 'Supabase'])
|
|
37
|
+
.then(r => console.log(r.content[0].text))
|
|
38
|
+
)"
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
### Method 2: Use /vibe.spec
|
|
42
|
+
|
|
43
|
+
```
|
|
44
|
+
/vibe.spec "feature-name"
|
|
45
|
+
→ Parallel research runs automatically after requirements confirmed
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
### Method 3: Parallel Task Tool Execution
|
|
49
|
+
|
|
50
|
+
```
|
|
51
|
+
Task 1: "Search React auth best practices"
|
|
52
|
+
Task 2: "Search Supabase Auth official docs" (concurrent)
|
|
53
|
+
Task 3: "Analyze existing auth code patterns" (concurrent)
|
|
54
|
+
Task 4: "Search auth security vulnerabilities" (concurrent)
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
## Using Research Results
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
Parallel research complete
|
|
61
|
+
↓
|
|
62
|
+
Synthesize results
|
|
63
|
+
↓
|
|
64
|
+
Reflect in SPEC Context section
|
|
65
|
+
OR
|
|
66
|
+
Reference during implementation
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
## When Research is NOT Needed
|
|
70
|
+
|
|
71
|
+
- Simple CRUD operations
|
|
72
|
+
- Already familiar patterns
|
|
73
|
+
- Similar code exists in project
|
|
74
|
+
- Time-critical (supplement with review later)
|
|
75
|
+
|
|
76
|
+
## Notes
|
|
77
|
+
|
|
78
|
+
- Research runs **after requirements confirmed**
|
|
79
|
+
- Split overly broad topics
|
|
80
|
+
- Research results are references, not absolute truth
|