meisijiya-frontend-taste
version: 0.1.0
meisijiya-frontend-taste
Attribution. This skill is a meisijiya adaptation of Leonxlnx/taste-skill's
taste-skill(now v2), originally written by Leon Linnx and released under MIT License. Core anti-slop rules are preserved; structure has been rewritten to fit the meisijiya 6-section skill-anatomy format and the OMO collaboration model.
Overview
LLM-written marketing frontend collapses into a small number of recognizable defaults: centered hero on dark mesh with AI-purple glow, three equal feature cards, generic glassmorphism everywhere, Inter + slate-900, Inter Display + Geist emoji micro-labels, fake screenshot previews. This skill enforces hard non-default rules at the moment the frontend agent begins writing UI code, so the output reads as designed, not generated.
Two layers of design contract stack: designer-handoff provides the project-specific design spec (colors / type / component); this skill provides the second-layer anti-slop rules (anti-default commitments, anti-tell discipline, pre-flight gate).
When to Use
Use when:
- Frontend agent is about to write UI code for landing pages / portfolios / marketing sites / redesigns
- Brief is for a "marketing-grade" frontend (a v1 SaaS landing, a designer portfolio, an editorial site, an agency site, a premium consumer product page)
- You want hard, named, mechanical enforcement against the LLM-default look (inter-purple-centered-glass slop)
- Working with React / Next.js / Vue / Svelte and Tailwind v4 (or vanilla CSS, shadcn/ui, Radix Themes)
- The brief is ambiguous but you trust the agent to declare a
Design Readrather than be told by you