← ClaudeAtlas

design-taste-litelisted

Condensed anti-template frontend design guide for websites, landing pages, portfolios and blogs. Load before writing HTML/CSS so the page does not look AI-generated.
YasefDogan/local-llm-lite-skills · ★ 0 · Web & Frontend · score 62
Install: claude install-skill YasefDogan/local-llm-lite-skills
# Design Taste Lite For landing pages, portfolios, blogs, redesigns. Not dashboards or data tables. Rules are contextual: read the brief first, apply what fits. "Banned" means banned unless the brief explicitly asks for it. ## 1. Read the Brief First Check these signals before writing code: 1. Page kind: landing (SaaS / consumer / agency / event), portfolio, blog/editorial, redesign. 2. Vibe words the user used: minimalist, premium, playful, brutalist, editorial, dark tech, trust-first. 3. References: linked sites, screenshots, named brands. 4. Audience: the audience picks the look, not your taste. 5. Existing brand assets (logo, colors, fonts): use them. 6. Quiet constraints (public sector, regulated, kids, accessibility-first) override aesthetics. Before any code, write ONE line: "Reading this as: <page kind> for <audience>, with a <vibe> language, leaning toward <aesthetic>." If the brief is truly ambiguous, ask exactly ONE question. Otherwise do not ask; proceed. Set three dials (1-10) and let them drive layout, motion and spacing: - VARIANCE (symmetry 1 to asymmetry 10) - MOTION (static 1 to cinematic 10) - DENSITY (airy 1 to packed 10) Presets (V/M/D): SaaS landing 7/6/4. Agency/creative 9/8/3. Premium consumer 7/6/3. Designer portfolio 8/7/3. Developer portfolio 6/5/4. Blog/editorial 6/4/3. Public sector 3/2/5. Minimalist/calm 5/3/2. Stack note: plain HTML + CSS + vanilla JS is fine. Use CSS variables for tokens, CSS Grid for layout, no framework required. One i