zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-04-04 16:23:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: harden install planning and sync tracked catalogs

Browse Source
This commit is contained in:
Affaan Mustafa
2026-03-31 22:57:48 -07:00
parent 03c4a90ffa
commit e1bc08fa6e
19 changed files with 970 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
agents/gan-generator.md
View File

@@ -98,21 +98,21 @@ Write to `gan-harness/generator-state.md` after each iteration:
The Evaluator will specifically penalize these patterns. **Avoid them:**
- ❌ Generic gradient backgrounds (#667eea → #764ba2 is an instant tell)
- ❌ Excessive rounded corners on everything
- ❌ Stock hero sections with "Welcome to [App Name]"
- ❌ Default Material UI / Shadcn themes without customization
- ❌ Placeholder images from unsplash/placeholder services
- ❌ Generic card grids with identical layouts
- ❌ "AI-generated" decorative SVG patterns
- Avoid generic gradient backgrounds (#667eea -> #764ba2 is an instant tell)
- Avoid excessive rounded corners on everything
- Avoid stock hero sections with "Welcome to [App Name]"
- Avoid default Material UI / Shadcn themes without customization
- Avoid placeholder images from unsplash/placeholder services
- Avoid generic card grids with identical layouts
- Avoid "AI-generated" decorative SVG patterns
**Instead, aim for:**
- ✅ A specific, opinionated color palette (follow the spec)
- ✅ Thoughtful typography hierarchy (different weights, sizes for different content)
- ✅ Custom layouts that match the content (not generic grids)
- ✅ Meaningful animations tied to user actions (not decoration)
- ✅ Real empty states with personality
- ✅ Error states that help the user (not just "Something went wrong")
- Use a specific, opinionated color palette (follow the spec)
- Use thoughtful typography hierarchy (different weights, sizes for different content)
- Use custom layouts that match the content (not generic grids)
- Use meaningful animations tied to user actions (not decoration)
- Use real empty states with personality
- Use error states that help the user (not just "Something went wrong")
## Interaction with Evaluator