Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When generating frontend UI code (React/Next.js) and the user needs the exact v1 taste-skill behavior for backward compatibility. Typically used for landing pages, portfolios, or redesigns depending on v1 output.
Premium, non-generic frontend code matching v1 standards: structured, responsive, animated, with full interaction states and no templated patterns.
Use Cases
A team maintains a legacy product built on v1 taste-skill output. They need new pages that visually and structurally match the existing v1 code exactly. By invoking design-taste-frontend-v1, the agent reproduces the same baseline configs and anti-slop rules, ensuring consistent UI without v2 rewrite side effects, saving rework and preserving brand coherence.
A developer audits an old codebase generated by v1 skill and wants to extend it with new components. Using design-taste-frontend-v1, they get the exact v1 conventions (RSC safety, Tailwind version lock, anti-emoji) applied, avoiding mismatched patterns from newer versions and guaranteeing the extension feels native to the original system.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
