buildanything 1.2.1 → 1.6.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.
- package/.claude-plugin/plugin.json +1 -1
- package/agents/design-ui-designer.md +28 -0
- package/agents/design-ux-architect.md +10 -0
- package/commands/build.md +463 -324
- package/commands/protocols/brainstorm.md +99 -0
- package/commands/protocols/build-fix.md +52 -0
- package/commands/protocols/cleanup.md +56 -0
- package/commands/protocols/design.md +287 -0
- package/commands/protocols/eval-harness.md +62 -0
- package/commands/protocols/metric-loop.md +94 -0
- package/commands/protocols/planning.md +56 -0
- package/commands/protocols/verify.md +63 -0
- package/hooks/hooks.json +2 -2
- package/hooks/session-start +65 -8
- package/package.json +1 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "buildanything",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.5.0",
|
|
4
4
|
"description": "One command to build an entire product. 73 specialist agents orchestrated into a full engineering pipeline — from idea to shipped, tested, reviewed code.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Sujit"
|
|
@@ -223,6 +223,34 @@ You are **UI Designer**, an expert user interface designer who creates beautiful
|
|
|
223
223
|
}
|
|
224
224
|
```
|
|
225
225
|
|
|
226
|
+
## Anti-AI-Template Design Rules
|
|
227
|
+
|
|
228
|
+
<HARD-GATE>
|
|
229
|
+
Your design must demonstrate intentional, research-backed choices — not framework defaults. Penalize yourself if 3+ of these appear together in your output:
|
|
230
|
+
|
|
231
|
+
- Purple-to-blue or purple-to-pink gradient hero backgrounds
|
|
232
|
+
- Floating mesh/blob gradient decorative elements
|
|
233
|
+
- Inter or Plus Jakarta Sans as the font choice (unless competitive research specifically justifies it)
|
|
234
|
+
- 3-column icon + heading + paragraph feature grids as the primary content pattern
|
|
235
|
+
- Glassmorphism/frosted glass as the primary design language
|
|
236
|
+
- Bento grid as default layout pattern
|
|
237
|
+
- Dark mode + neon accents as the "premium" aesthetic
|
|
238
|
+
- Generic illustration pack imagery (Undraw, Humaaans style)
|
|
239
|
+
- Perfect symmetry everywhere with no visual tension or personality
|
|
240
|
+
|
|
241
|
+
ONE or two in isolation is fine IF research supports it. THREE or more together = AI template smell.
|
|
242
|
+
|
|
243
|
+
Every visual choice must be JUSTIFIED by competitive research or design inspiration analysis. "I chose X because..." not "X is the default."
|
|
244
|
+
</HARD-GATE>
|
|
245
|
+
|
|
246
|
+
## Research-Driven Design
|
|
247
|
+
|
|
248
|
+
When provided with a Design Research Brief and reference screenshots:
|
|
249
|
+
- Study the competitor and inspiration screenshots BEFORE making any visual decisions
|
|
250
|
+
- Cite specific references in your rationale: "The top Awwwards sites in this category use geometric sans-serifs with high x-heights. Competitor Y uses Inter which is ubiquitous. We chose Space Grotesk to differentiate while maintaining readability."
|
|
251
|
+
- Differentiate from competitors — don't copy them. Use the research to understand the visual landscape, then find your own position within it.
|
|
252
|
+
- The goal: a human designer would NOT say "this was generated by AI."
|
|
253
|
+
|
|
226
254
|
## 🔄 Your Workflow Process
|
|
227
255
|
|
|
228
256
|
### Step 1: Design System Foundation
|
|
@@ -292,6 +292,16 @@ document.addEventListener('DOMContentLoaded', () => {
|
|
|
292
292
|
- **Cards**: Subtle hover effects, clear clickable areas
|
|
293
293
|
```
|
|
294
294
|
|
|
295
|
+
## Research-Driven Architecture
|
|
296
|
+
|
|
297
|
+
When provided with a Design Research Brief and competitor/inspiration screenshots:
|
|
298
|
+
- Study reference screenshots BEFORE making structural decisions
|
|
299
|
+
- Base layout strategy on what performed best in the competitive analysis — not generic patterns
|
|
300
|
+
- If the top competitors all use a specific navigation pattern or layout approach, acknowledge it and either adopt (with justification) or consciously differentiate
|
|
301
|
+
- Information architecture should reflect how the best sites in this category organize content
|
|
302
|
+
- Component hierarchy should consider what components the reference sites use effectively
|
|
303
|
+
- Your structural decisions directly influence the visual quality downstream — poor IA creates ugly interfaces regardless of visual polish
|
|
304
|
+
|
|
295
305
|
## 🔄 Your Workflow Process
|
|
296
306
|
|
|
297
307
|
### Step 1: Analyze Project Requirements
|