Yige
8f7953948f
## 中文 补齐已有 owner 与已锁定上游内容可证明的许可证、技能类型和收录版本。保留 Anthropic Source Available 和其他附加条件，不把所有内容统一标为 MIT，不提升 listing-only 的安装准入。 README 保留最新的双语结构及以 manifest 为准的数量口径，增加静态目录不存访问量、下载量、评分或 Stars 的边界。 发布兼容性：**本 PR 不包含**两支团队新增的本地化字段，也不包含微信支付 `latestVersion: 1.0`；旧客户端会拒绝这些新字段，另以待发布 PR 保留，等匹配客户端发布后再合并。 验证：47 项目录校验测试、19 项 i18n 测试、5 项合集生成测试通过；完整目录/i18n/翻译新鲜度检查通过，6 个固定来源合集的生成检查通过，2 个浮动来源按既有规则明确跳过。发现并修复了生成器在 Windows 使用反斜杠造成的误报：输出改为 POSIX 路径，比较规则不放宽、不重写合集数据。 ## English Fill only license, type and listed-release facts supported by existing owners or pinned upstream content. Preserve custom license restrictions and acquisition eligibility. Keep the current bilingual README and manifest-derived inventory; do not author usage analytics. This PR deliberately excludes localized team fields and the two-part WeChat Pay version that older clients reject. Those changes remain pending a compatible client release. Validation passes: 47 catalog-validator tests, 19 i18n tests, five collection-generator tests, complete catalog and translation checks, and generated inventory checks for six pinned collections. Two mutable sources remain explicitly skipped. Fix Windows-generated path separators without weakening comparison or changing declared children.
9.5 KiB
name, description, license, version, type, risk_level, status, disable-model-invocation, tags, metadata, market
| name | description | license | version | type | risk_level | status | disable-model-invocation | tags | metadata | market | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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. Use when 用户提到 前端设计、网页设计、UI 设计、 界面设计、组件、海报、Landing Page、落地页、React 组件、Vue 组件、 CSS 样式、美化界面、设计一个、做一个网页、官网、仪表盘、Dashboard。 | Apache-2.0 | 1.0.2 | procedural | low | enabled | true |
|
|
|
frontend-design Skill
L0: One-line Summary
Create tasteful, production-grade frontend interfaces and components that avoid generic AI aesthetics.
L1: Overview and Use Cases
Capability Description
frontend-design is a Procedural Skill that guides the creation of distinctive, production-grade frontend interfaces while avoiding cookie-cutter AI-generated aesthetics. It outputs real, runnable code with attention to aesthetic detail and creative choices.
Use Cases
- The user needs to create web components, pages, or applications (landing pages, Dashboards, React components, etc.)
- The user needs to polish the styling of an existing web UI
- The user needs to create posters, visual designs, or other frontend deliverables
Core Value
- Anti-AI aesthetics: rejects the cliched Inter font + purple gradient style
- Design-thinking driven: settle on an aesthetic direction first, then write code
- Production-grade quality: outputs complete, ready-to-use code
L2: Detailed Specification
Output Rule
When you create or modify HTML/CSS/JS/React/Vue files, you MUST tell the user the absolute path of the output file in your response. Example: "File saved to: /path/to/index.html"
If you create multiple files (e.g. HTML + CSS + JS), list each path explicitly.
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. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
- 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; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
- 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. 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.
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.
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
Project Context Override (DesireCore Specific)
Note
: When working inside the DesireCore main repository (
desirecore-9or any project that hasapp/styles/globals.csswith the DesireCore 3+2 token system), the project's strict design system OVERRIDES the bold aesthetic guidance above. In that context:
- Use only the 3 functional colors (Green / Blue / Purple) + 2 status colors (Orange / Red) defined in
globals.css- Reference design tokens via CSS variables (
var(--accent-green), etc.) — never hardcoded hex- Follow the typography, radius, and spacing tokens already defined
- The "avoid generic AI aesthetics" principle still applies, but expression happens through layout/composition/motion, not color expansion
For standalone artifacts, posters, landing pages, or external projects, the full aesthetic freedom of this skill applies — go bold.