design-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
1How It Works & Mechanism
Acts as a "frozen original version": preserves v1's dial-driven philosophy, anti-slop rules, and pattern nomenclature library as-is for legacy projects requiring pinned versions to maintain exact behavior.
The original release. Dial-driven philosophy, anti-slop rules, reference vocabulary of pattern names.
Drives rule branches throughout the entire document using three 1–10 dials (DESIGN_VARIANCE / MOTION_INTENSITY / VISUAL_DENSITY) with fixed baselines at 8/6/4, strictly forbidding users from modifying files and only accepting dynamic overrides via chat dialogue.
The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file.
Mandates dependency governance as an upfront prerequisite: package.json must be read before importing any third-party library, requiring installation commands to be printed first if packages are missing, and strictly prohibiting the assumption of existing libraries.
**DEPENDENCY VERIFICATION [MANDATORY]:** Before importing ANY 3rd party library (e.g. `framer-motion`, `lucide-react`, `zustand`), you MUST check `package.json`.
Framework-level conventions: defaults to React/Next.js and RSC, requiring interactive components to be extracted into leaf components marked with 'use client', while restricting global state to only bypassing deep prop drilling.
* **State Management:** Use local `useState`/`useReducer` for isolated UI.
Anti-AI bias rules are formalized into six actionable design directives (deterministic typography, color calibration, layout decentralization, materiality & decardification, full lifecycle interactive states, form patterns), each accompanied by default class strings.
**ANTI-CENTER BIAS:** Centered Hero/H1 sections are strictly BANNED when `DESIGN_VARIANCE > 4`.
Enforces technical implementation standards for creative autonomy: micro-magnetic physics must use Framer Motion's useMotionValue/useTransform to decouple from the React render cycle, strictly forbidding useState for driving continuous animations.
**CRITICAL:** NEVER use React `useState` for magnetic hover or continuous animations.
Prohibits mixed animation stacks: GSAP/ThreeJS and Framer Motion must not coexist within the same component tree; GSAP/ThreeJS are reserved strictly for full-page scroll-driven narratives and require rigorous useEffect cleanup.
**CRITICAL:** Never mix GSAP/ThreeJS with Framer Motion in the same component tree.
Enumerates an AI tells blacklist across five dimensions (Visual/CSS, Typography, Layout Spacing, Content Data, External Resources & Components), explicitly banning fake names (John Doe/Sarah Chan), fake metrics (99.99%/50%), fake brands (Acme/Nexus/SmartFlow), and generic marketing fluff.
**NO Broken Unsplash Links:** Do not use Unsplash. Use absolute, reliable placeholders like `https://picsum.photos/seed/{random_string}/800/600` or SVG UI Avatars.
§8 establishes an "advanced interaction terminology library" (spanning seven categories: navigation, layout, cards, scroll, gallery, typography, micro-interactions, with dozens of pattern names) for models to source from rather than improvising on the fly.
## 9. THE "MOTION-ENGINE" BENTO PARADIGM
Concludes by institutionalizing pre-delivery verification via a 7-point pre-flight checklist, covering global state, mobile collapsible handling, 100dvh, useEffect cleanup, empty/loading/error states, decardification, and CPU-intensive animation isolation.
- [ ] Do full-height sections safely use `min-h-[100dvh]` instead of the bugged `h-screen`?
2Core Capabilities
3External Dependencies
| Kind | Dependency / Endpoint |
|---|---|
| network | picsum.photos(禁用 Unsplash 后指定的占位图源) |
| package | Framer Motion(默认动效库,含 useMotionValue/useTransform/layout/AnimatePresence) |
| package | @phosphor-icons/react 或 @radix-ui/react-icons(唯一允许的图标包) |
| package | Tailwind CSS v3/v4(90% 样式来源,含版本锁与 v4 postcss 守则) |
| package | shadcn/ui(允许使用但禁止默认态) |
| package | GSAP(ScrollTrigger)与 ThreeJS/WebGL(仅限整页滚动叙事/画布背景,禁与 Framer Motion 混用) |
| package | lucide-react / zustand(被点名作为需先校验是否已安装的示例库) |
4Recommended Governance & Evidence
- 网络端点: Declared external network access: picsum.photos — the skill itself does not initiate network requests, but dictates generated pages to use https://picsum.photos/seed/{random
- 本地工作目录: File I/O and artifact output: the skill instructs the agent to write source files (React/Next components, etc.) inside the user's project—standard file generation for deliverables; additionally requires reading the user's package.json.
5Second-Pass Verification
- [ok] 『保留 v1 兼容』的定位是否有仓库级依据 — CHANGELOG 'The original release. Dial-driven philosophy, anti-slop rules, reference vocabulary of pattern names.' 与 README 'preserved for projects depending on its exact behavior' 双重印证;README 还给出钉版安装命令与 install name。
- [discrepancy] 安装名与目录名不一致(易用性坑) — 目录为 skills/taste-skill-v1,但 frontmatter name 与安装用的 install name 是 design-taste-frontend-v1。README 明确 'Install a single skill by its **install name** (the `name:` field inside the SKILL frontmatter, not the folder name)'——两者不一致是官方设计,但对用户是实际坑点,已记录。
- [ok] 外部依赖清单完整性 — token 扫描命中项全部核实为包名/图片源/工具类,无遗漏的隐藏端点:picsum.photos(§7)、framer-motion/lucide-react/zustand(§2 依赖校验示例)、@phosphor-icons/react 与 @radix-ui/react-icons(§2 Icons)、Tailwind v3/v4 与 @tailwindcss/postcss(§2 版本锁)、shadcn/ui(§7)、GSAP/ThreeJS(§8)。npm install 仅作为『缺包时需输出的命令』示例,非 skill 自行执行。
- [ok] 是否真的会读用户文件(file_writes/读取面) — §2 要求先检查 package.json 与已安装版本(只读),属技能明示的正确性前置;文中无其它文件读写指令。写入面全部是产物源码。
- [ok] 与批1 的 design-taste-frontend(v2)是否重复 — 同一 repo 两个不同 skill:v2 位于 skills/taste-skill(install name design-taste-frontend,brief 推断 + 设计系统映射 + 暗色模式/重设计协议/区块库),v1 位于 skills/taste-skill-v1(三档参数 + 名词库 + Framer Motion 栈)。CHANGELOG 视 v2 为 'substantial rewrite';本次结论只对 pin commit 内的 v1 文件有效,不推广到 v2。
- [ok] 动画栈规定是否前后矛盾 — §4 强制 Framer Motion 用于 UI/Bento,§8 允许 GSAP/ThreeJS 但限定于整页滚动叙事/画布背景且禁止与 Framer Motion 同树混用——两处口径互补,无矛盾(与 gpt-taste 全面 GSAP 路线不同,属版本差异)。
- [ok] 元数据(license / stars / last_push / 路径 / commit) — gh api:MIT、87309 stars、pushed_at 2026-08-24T15:23:56Z;git ls-files 确认 skills/taste-skill-v1/SKILL.md;HEAD == origin/main == ccbc15639c97057cbfcf32ecebc38ef716e4bb37。
6Verdict & Scenarios
470ab18897944ef0…