Vecbase review
The most complete design skill in this group. It is equally useful before implementation and during the final ten percent, where hierarchy, rhythm, copy, and edge cases usually drift apart. The required product context is a feature, not ceremony.
What stands out
- Separates brand surfaces from product interfaces before making visual choices
- Offers a precise vocabulary for making a page bolder, quieter, clearer, or more disciplined
- Combines visual critique with accessibility, responsive, and production checks
What to prepare
- It works best after PRODUCT.md and DESIGN.md describe the actual company and interface
- Its many commands reward deliberate use; invoking everything at once can overwork a page
- Some visual rules are intentionally opinionated and should yield to an established design system
What it can do
- Shape product and brand interfaces
- Critique hierarchy and visual coherence
- Detect recurring AI design anti-patterns
- Polish responsive implementation
What it needs
- Product and audience context
- Existing code or implementation target
- Browser runtime for live iteration
What it returns
- Design direction
- Implemented interface changes
- Prioritized critique and audit findings
Ask it to work
“Critique and refine this Store detail page.”
“Distill this dashboard without losing operational density.”