Skip to content

feat(skill/frontend-design): ban emojis, enforce icon system in frontend-design #978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Juan-Severiano wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −0
Open

feat(skill/frontend-design): ban emojis, enforce icon system in frontend-design #978

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions skills/frontend-design/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ Focus on:
- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
- **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. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
- **Icons, not Emojis**: NEVER use emojis anywhere in the UI or in code comments/documentation. Always use a proper icon system instead. When working on an existing codebase, check for an already-imported icon library (Lucide, Heroicons, React Icons, Font Awesome, Bootstrap Icons, Material Icons, Phosphor, etc.) and reuse it. If no icon library exists, introduce one — prefer libraries that are tree-shakeable and stylistically consistent with the design aesthetic. Icons must be sized, colored, and spaced as first-class design elements, not afterthoughts.

NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.

Expand Down
Loading