Create a clean minimal beige light-mode design system with warm neutral shells, quiet process grids, restrained accent color, and elegant low-contrast structure.
Install
npx skills add https://github.com/mengto/skills --skill clean-minimal-beige-light-modeSKILL.md
Clean Minimal Beige Light Mode Skill
Use When
- Create a clean minimal beige light-mode design system with warm neutral shells, quiet process grids, restrained accent color, and elegant low-contrast structure.
Workflow
Scope
- Apply this as a full design-system direction across page background, hero, shell, grid modules, cards, buttons, and motion.
- Use it when the interface should feel light, calm, premium, and process-oriented, with warm beige neutrals instead of cold white enterprise UI.
- This is not generic bright SaaS and not an ornate paper system. It should stay clean, minimal, and quietly operational.
Visual target
- Build the page on layered beige, stone, cream, and off-white surfaces with very low-contrast borders and subtle tonal separation.
- Use a centered master container or framed application shell that holds the experience together in a precise but understated way.
- Pair a simple centered hero with a modular lower information grid or process layout made of evenly divided blocks.
- Keep accent color sparse and purposeful, used only for key badges, active indicators, progress, or primary action states.
- Let the design feel highly organized and premium without relying on strong shadows, loud gradients, or heavy decorative effects.
Implementation guidance
- Prefer warm neutral backgrounds with a gentle radial or painted wash behind the main UI rather than flat plain white.
- Use thin borders, soft dividers, and restrained panel contrast to create hierarchy between sections and cards.
- Organize lower content into a rigid modular grid with equal columns, calm labels, short descriptions, and simple functional mock components.
- Buttons and pills should feel light, refined, and understated, using soft fills, tiny radius or low-radius corners, and subtle border treatment.
- Typography should remain modern and readable: clean sans-serif, modest weight contrast, quiet tracking, and balanced spacing.
- Motion should be subtle and clean: masked text reveals, mild fade-ins, and gentle background drift are enough.
Recommended patterns
- Large warm neutral hero with centered heading, small badge, and minimal CTA stack.
- Framed app shell or product block using light beige backgrounds and thin internal dividers.
- Process columns or modular info panels with consistent heights and restrained descriptive content.
- Small dark or tinted inset cards used sparingly as contrast moments within a mostly light composition.
- Tiny status dots, low-key progress bars, and minimal approval or routing cards that communicate process without clutter.
Tuning knobs
- Beige warmth: shift from cooler stone to warmer parchment depending on brand mood.
- Contrast level: keep enough separation between shells and panels to feel crisp, but avoid harsh black-on-white jumps.
- Accent intensity: use the accent as a signal color only, not as a dominant palette driver.
- Grid density: make the modular lower section information-rich but still breathable.
- Surface softness: allow slight softness in shadows and gradients, but keep the overall result disciplined and minimal.
Avoid
- Stark white SaaS layouts with cold gray borders and no warmth.
- Overdecorated paper textures, vintage distressing, or ornate editorial flourishes.
- Heavy shadows, high-saturation accents, or thick cards that break the quiet minimal tone.
- Filling every module with too much content until the process grid feels noisy.
- Turning the design into a dashboard-heavy system instead of a calm structured product presentation.
Related skills
frontend-designanthropics932KGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.prototypemattpocock852KBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.hyperframes-animationheygen-com569KAll animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreographyhyperframes-creativeheygen-com539KNon-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.
