lavish-design
GitHub用于生成Lavish品牌风格的界面和资产。提供设计指南、色彩字体规范及UI组件,支持快速原型或生产代码开发。遵循严格的设计规则,如深色墨水配奶油色文字、特定字体搭配及颜色语义,确保品牌一致性。
Trigger Scenarios
Install
npx skills add kunchenguid/lavish-axi --skill lavish-design -g -y
SKILL.md
Frontmatter
{
"name": "lavish-design",
"metadata": {
"internal": true
},
"description": "Use this skill to generate well-branded interfaces and assets for Lavish, either for production or throwaway prototypes\/mocks\/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.",
"user-invocable": true
}
Read the README.md file within this skill, and explore the other available files. If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view. If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand. If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need.
Where things live
README.md— product context, content fundamentals, visual foundations, iconography, caveatscolors_and_type.css— drop-in CSS custom properties for the full token system (ink, brass, sage, amber, rust, steel, cream + type + spacing + radii + shadows)assets/— wordmark, lavish-mark icon, flow diagram SVGpreview/— Design-System-tab specimen cards (one concept per card)ui_kits/editor/— clickable React recreation of the Lavish Editor chrome
Quick rules of thumb
- Dark ink + cream type + one brass accent. No second accent, no gradient, no glassmorphism.
- Serif for prose and brand moments (EB Garamond italic). Sans for chrome (Geist). Mono for technical (Geist Mono).
- No emoji. No exclamation marks. No "🚀 powerful seamless" copy. Read the on-brand/off-brand examples in README's Content Fundamentals.
- The element annotation outline = the focus outline: 2px brass, 2px offset. Text range annotations use a translucent brass highlight instead; both mean "attention is here."
- Shadows only on floating surfaces (tooltip, annotation card). Never on buttons or in-panel cards.
- Sage = agent. Amber = user. Rust = danger. Don't mix.
- Words first, icons second. When you must reach for an icon, use Lucide (stroke, 1.5, currentColor).
To produce a new HTML artifact
@import "../colors_and_type.css";in your stylesheet (or copy the tokens block inline if standalone).- Build with the semantic vars (
--bg,--fg,--accent, etc.) — never hard-code hex. - Set
font-family: var(--font-sans)on the body; reach forvar(--font-serif)on headlines and pull-quotes. - Reference
assets/lavish-wordmark.svgfor the brand mark; do not redraw it. - If you need a component (button, pill, bubble, annotation card, top bar), open the matching JSX file in
ui_kits/editor/and copy the styles object — they're already token-driven.
Version History
- 50b0fac Current 2026-07-24 12:22


