the-grid-cc 1.7.23 → 1.7.24
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/agents/grid-upscaler.md +55 -17
- package/commands/grid/VERSION +1 -1
- package/package.json +1 -1
package/agents/grid-upscaler.md
CHANGED
|
@@ -83,16 +83,25 @@ detected_domains:
|
|
|
83
83
|
|
|
84
84
|
### Phase 2: Research Sprint
|
|
85
85
|
|
|
86
|
-
For EACH detected domain,
|
|
86
|
+
For EACH detected domain, research current best practices:
|
|
87
87
|
|
|
88
|
-
**
|
|
88
|
+
**With Exa (preferred):**
|
|
89
|
+
- `mcp__exa__get_code_context_exa` for technical patterns
|
|
90
|
+
- `mcp__exa__web_search_exa` for industry standards
|
|
91
|
+
|
|
92
|
+
**Without Exa (fallback):**
|
|
93
|
+
- `WebSearch` with domain-specific query modifiers
|
|
94
|
+
- Add year (2024-2025) for recency
|
|
95
|
+
- Add authoritative site filters where appropriate
|
|
96
|
+
|
|
97
|
+
**Technical Domains:**
|
|
89
98
|
- Current best practices and patterns (2024-2025)
|
|
90
99
|
- Modern frameworks and libraries
|
|
91
100
|
- Performance considerations
|
|
92
101
|
- Security requirements (OWASP, etc.)
|
|
93
102
|
- Testing approaches
|
|
94
103
|
|
|
95
|
-
**Non-Technical Domains
|
|
104
|
+
**Non-Technical Domains:**
|
|
96
105
|
- Industry standards and guidelines
|
|
97
106
|
- Regulatory requirements
|
|
98
107
|
- Best practices from leaders
|
|
@@ -100,11 +109,14 @@ For EACH detected domain, conduct targeted research:
|
|
|
100
109
|
- Recent developments
|
|
101
110
|
|
|
102
111
|
**Research Protocol:**
|
|
103
|
-
1.
|
|
112
|
+
1. Minimum research per domain:
|
|
113
|
+
- Simple: 2-3 searches
|
|
114
|
+
- Medium: 3-5 searches
|
|
115
|
+
- Complex: 5+ searches
|
|
104
116
|
2. Prioritize authoritative sources (official docs, OWASP, RFC, industry standards)
|
|
105
117
|
3. Look for anti-patterns explicitly
|
|
106
118
|
4. Capture specific, actionable insights
|
|
107
|
-
5. Note the source for each insight
|
|
119
|
+
5. Note the source for each insight (regardless of tool used)
|
|
108
120
|
|
|
109
121
|
### Phase 3: Constraint Decomposition
|
|
110
122
|
|
|
@@ -380,21 +392,46 @@ upscaled_directive:
|
|
|
380
392
|
|
|
381
393
|
## TOOLS
|
|
382
394
|
|
|
383
|
-
###
|
|
395
|
+
### Search Tools (Priority Order)
|
|
396
|
+
|
|
397
|
+
The Upscaler uses the best available search tools, with automatic fallback:
|
|
398
|
+
|
|
399
|
+
| Priority | Tool | Use Case | Fallback |
|
|
400
|
+
|----------|------|----------|----------|
|
|
401
|
+
| 1 | `mcp__exa__get_code_context_exa` | Technical/code patterns | WebSearch |
|
|
402
|
+
| 2 | `mcp__exa__web_search_exa` | Industry best practices | WebSearch |
|
|
403
|
+
| 3 | `WebSearch` | General research | Always available |
|
|
404
|
+
|
|
405
|
+
**Fallback Behavior:**
|
|
406
|
+
- If Exa tools are unavailable (MCP not configured), automatically use WebSearch
|
|
407
|
+
- WebSearch provides equivalent functionality with broader but less specialized results
|
|
408
|
+
- All research phases work with either toolset
|
|
409
|
+
|
|
410
|
+
### Tool Selection Logic
|
|
411
|
+
|
|
412
|
+
```
|
|
413
|
+
IF task involves code/technical patterns:
|
|
414
|
+
TRY mcp__exa__get_code_context_exa
|
|
415
|
+
FALLBACK TO WebSearch with technical query
|
|
416
|
+
|
|
417
|
+
IF task involves industry research:
|
|
418
|
+
TRY mcp__exa__web_search_exa
|
|
419
|
+
FALLBACK TO WebSearch with industry query
|
|
420
|
+
|
|
421
|
+
ALWAYS AVAILABLE:
|
|
422
|
+
WebSearch - works for all research needs
|
|
423
|
+
Read - reference docs
|
|
424
|
+
Glob/Grep - codebase patterns
|
|
425
|
+
```
|
|
384
426
|
|
|
385
|
-
|
|
386
|
-
- Use for: APIs, libraries, frameworks, coding patterns
|
|
387
|
-
- Query format: "[Technology] [specific pattern] best practices 2024"
|
|
388
|
-
- Example: "React authentication patterns best practices 2024"
|
|
427
|
+
### Search Query Adaptation
|
|
389
428
|
|
|
390
|
-
|
|
391
|
-
-
|
|
392
|
-
-
|
|
393
|
-
- Example: "HIPAA compliance healthcare data best practices"
|
|
429
|
+
When falling back to WebSearch, adapt queries:
|
|
430
|
+
- Exa code context: `"React hooks best practices"`
|
|
431
|
+
- WebSearch equivalent: `"React hooks best practices 2024 tutorial site:github.com OR site:dev.to"`
|
|
394
432
|
|
|
395
|
-
|
|
396
|
-
-
|
|
397
|
-
- Good for recent news, updates, announcements
|
|
433
|
+
- Exa industry search: `"HIPAA compliance healthcare AI"`
|
|
434
|
+
- WebSearch equivalent: `"HIPAA compliance healthcare AI guidelines 2024"`
|
|
398
435
|
|
|
399
436
|
### Secondary Tools
|
|
400
437
|
|
|
@@ -439,6 +476,7 @@ upscaled_directive:
|
|
|
439
476
|
9. **STRUCTURED OUTPUT** - Use XML tags for clarity and parseability
|
|
440
477
|
10. **SELF-REFINE** - Max 2 iterations, stop early if quality high
|
|
441
478
|
11. **NO EXECUTION** - You research and enhance. You do NOT build or code
|
|
479
|
+
12. **GRACEFUL FALLBACK** - If Exa unavailable, use WebSearch with adapted queries
|
|
442
480
|
|
|
443
481
|
---
|
|
444
482
|
|
package/commands/grid/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
1.7.
|
|
1
|
+
1.7.24
|