AGENT SKILL

clean-minimal-beige-light-mode

Create a clean minimal beige light-mode design system with warm neutral shells, quiet process grids, restrained accent color, and elegant low-contrast structure.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 13
Forks
4

01 前言 Front Matter

name
clean-minimal-beige-light-mode
license
MIT
description
Create a clean minimal beige light-mode design system with warm neutral shells, quiet process grids, restrained accent color, and elegant low-contrast structure.

02 资源文件 2

03 SKILL.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.

04 同仓库更多 Skills

LiamVisionary
LiamVisionary/hivemindos

tailscale-generation-skill-authoring

This skill should be used when the user asks to "create a Tailscale generation skill", "add a local generation skill", "document a generation endpoint", "add an image generation provider", "add a TTS provider", "add video generation", "add 3D generation", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.

★ 13
LiamVisionary
LiamVisionary/hivemindos

localtts

This skill should be used when the user asks to "generate local TTS", "use local text to speech", "use remote TTS over Tailscale", "make speech audio", "add a TTS provider", "use Qwen3-TTS", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.

★ 13
LiamVisionary
LiamVisionary/hivemindos

karpathy-guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

★ 13
LiamVisionary
LiamVisionary/hivemindos

comfyui-image-generation

This skill should be used when the user asks to "generate images", "generate images with ComfyUI", "use local ComfyUI", "use remote ComfyUI", "use Z-Image", "add an image generation provider", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.

★ 13
LiamVisionary
LiamVisionary/hivemindos

wrangler

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 13
LiamVisionary
LiamVisionary/hivemindos

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 13