21f32add68
* feat: bump ollama version to 0.14.3 + misc fixes (#1148) * bump node version * bump node version * fixes * improve wording when removing inbox * bump app version * update linux ollama * fix: streamdown plugins, mermaid, update ollama models (#1149) * fix: streamdown plugins * fix mermaid syntax * fix streamdown plugins * update ollama models * chore: remove unused packages, metadata editor fixes (#1150) * chore: remove unused packages * fix npm audit * fix: regenerate metadata editor * feat: delete multiple chats (#1151) * feat: delete multiple chats * improvements * misc improvements * fix * chore: update ollama to 0.12.3 (#1152) * chore: update OLLAMA_VERSION to 0.12.3 * chore: update packages * chore: bump node version and npm audit fixes (#1153) * bump node * chore: update tar and lodash-es versions * fix: minor UI (#1154) * ui fixes * fixes * Merge upstream dcSpark/shinkai-local-ai-agents latest Merges 7 upstream commits: - feat: delete multiple chats (useRemoveJobs, manage-chats-dialog) - feat: bump ollama version to 0.14.3 + misc fixes - fix: streamdown plugins, mermaid, update ollama models - chore: remove unused packages, metadata editor fixes - chore: update ollama to 0.12.3 - chore: bump node version and npm audit fixes - fix: minor UI improvements All new upstream code rebranded to Hanzo naming: - @shinkai_network → @hanzo_network in new components - New removeMultipleJobs mutation created in hanzo-node-state - Removed stale libs/shinkai-node-state directory - READMEs use HANZO_NODE_VERSION with bumped version --------- Co-authored-by: Paul Ccari <[email protected]>
3.0 KiB
name, description, source, license
| name | description | source | license |
|---|---|---|---|
| frontend-design | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics. | anthropics/skills | Apache-2.0 |
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
Design Thinking
Before coding, understand the context and commit to a BOLD aesthetic direction:
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc.
- Constraints: Technical requirements (framework, performance, accessibility).
- Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
Frontend Aesthetics Guidelines
Focus on:
- Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics.
- Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
- Motion: Use animations for effects and micro-interactions. Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.
- Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
- Backgrounds & Visual Details: Create atmosphere and depth rather than defaulting to solid colors.
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial), cliched color schemes (purple gradients on white), predictable layouts and component patterns.
Interpret creatively and make unexpected choices that feel genuinely designed for the context.