uv-suite 0.3.0 → 0.3.1
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 +1 -1
- package/personas/professional.json +1 -1
- package/personas/spike.json +1 -1
- package/settings.json +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "uv-suite",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"description": "Portable framework for AI-assisted software development. 10 agents, 9 skills, 5 hooks, 4 personas. Works with Claude Code, Cursor, and Codex.",
|
|
5
5
|
"author": "Utsav Anand",
|
|
6
6
|
"license": "MIT",
|
|
@@ -85,7 +85,7 @@
|
|
|
85
85
|
{
|
|
86
86
|
"type": "prompt",
|
|
87
87
|
"prompt": "Quickly scan the code that was just written or edited for the most obvious AI slop patterns: (1) comments that restate the code like '// Initialize the database' above initDatabase(), (2) try/catch around code that can't throw, (3) single-implementation interfaces or factories, (4) toBeTruthy()/toBeDefined() in tests. If you find any of these specific patterns, respond with {\"ok\": false, \"reason\": \"Slop detected: [specific finding with line reference]. Fix: [specific fix].\"} If the code is clean, respond with {\"ok\": true}. Only flag the most obvious violations — do not be overly strict.",
|
|
88
|
-
"model": "claude-haiku",
|
|
88
|
+
"model": "claude-haiku-4-5",
|
|
89
89
|
"timeout": 15,
|
|
90
90
|
"statusMessage": "Checking for AI slop..."
|
|
91
91
|
}
|
package/personas/spike.json
CHANGED
|
@@ -43,7 +43,7 @@
|
|
|
43
43
|
{
|
|
44
44
|
"type": "prompt",
|
|
45
45
|
"prompt": "The agent just wrote a documentation or analysis file. Check for documentation slop: (1) vague adjectives like 'robust', 'scalable', 'comprehensive', 'leverages', 'facilitates', (2) feature lists that could describe any system, (3) overview sections that don't say what the system actually does, (4) claims without specifics ('industry-standard best practices'). If you find slop, respond {\"ok\": false, \"reason\": \"Doc slop: [finding]. Fix: replace with specific facts.\"}. If clean, respond {\"ok\": true}.",
|
|
46
|
-
"model": "claude-haiku",
|
|
46
|
+
"model": "claude-haiku-4-5",
|
|
47
47
|
"timeout": 15,
|
|
48
48
|
"statusMessage": "Checking documentation quality..."
|
|
49
49
|
}
|
package/settings.json
CHANGED
|
@@ -84,7 +84,7 @@
|
|
|
84
84
|
{
|
|
85
85
|
"type": "prompt",
|
|
86
86
|
"prompt": "Quickly scan the code that was just written or edited for the most obvious AI slop patterns: (1) comments that restate the code like '// Initialize the database' above initDatabase(), (2) try/catch around code that can't throw, (3) single-implementation interfaces or factories, (4) toBeTruthy()/toBeDefined() in tests. If you find any of these specific patterns, respond with {\"ok\": false, \"reason\": \"Slop detected: [specific finding with line reference]. Fix: [specific fix].\"} If the code is clean, respond with {\"ok\": true}. Only flag the most obvious violations — do not be overly strict.",
|
|
87
|
-
"model": "claude-haiku",
|
|
87
|
+
"model": "claude-haiku-4-5",
|
|
88
88
|
"timeout": 15,
|
|
89
89
|
"statusMessage": "Checking for AI slop..."
|
|
90
90
|
}
|