high-contrast-skeuomorphic-clean
Create a high-contrast clean skeuomorphic design system with molded dark surfaces, crisp light separation, tactile inset depth, and restrained signal accents.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 13
- Forks
- 4
01 前言 Front Matter
- name
- high-contrast-skeuomorphic-clean
- license
- MIT
- description
- Create a high-contrast clean skeuomorphic design system with molded dark surfaces, crisp light separation, tactile inset depth, and restrained signal accents.
02 资源文件 2
- 参考文档.hivemind-skill-source.json1.1 KB
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
High Contrast Skeuomorphic Clean Skill
Use When
- Create a high-contrast clean skeuomorphic design system with molded dark surfaces, crisp light separation, tactile inset depth, and restrained signal accents.
Workflow
Scope
- Apply this as a full design-system direction across page shell, hero, cards, controls, supporting modules, and micro-visualizations.
- Use it when the interface should feel tactile, premium, and industrial-clean, with real surface depth and contrast rather than flat minimal cards.
- This is not playful neumorphism and not glossy consumer skeuomorphism. The result should stay sharp, modern, and system-like.
Visual target
- Build the experience around a strong contrast relationship: a light or neutral outer page framing a deep black or charcoal primary application shell.
- Use dark premium surfaces with subtle vertical or radial gradients so panels feel molded and dimensional instead of flat.
- Add true skeuomorphic depth through inset highlights, soft inner shadows, reflective edge cues, and nested object-like modules, but keep everything clean and controlled.
- Let one restrained signal accent color derived from the design or brand drive status lights, active markers, tiny progress details, and focal emphasis.
- Pair clean sans-serif typography with occasional mono labels or utility text so the system feels precise, not ornamental.
Implementation guidance
- Prefer one dominant rounded or softly chamfered master container that holds the whole interface inside a darker, premium shell.
- Build cards and modules with one-pixel wrappers, top-edge highlights, dark-to-darker fills, inset shadow stacks, and soft outer shadow falloff to create tactile hierarchy.
- Keep contrast high: white or near-white text on black shells, muted gray support copy, and clear separation between interactive and passive surfaces.
- Use skeuomorphic objects selectively inside the system, such as browser-like windows, search fields, progress bars, orbit widgets, document tiles, or instrument modules that feel physically assembled.
- Buttons, inputs, and chips should look touchable: layered fill, subtle bevel or inset edge, clean rounded geometry, and measured hover brightness rather than loud glow.
- Add fine structural framing with quiet border lines, corner markers, or interior guide rails so the tactile surfaces still sit inside a disciplined layout.
- Motion should support the material feel: masked reveals, gentle object lift, slow orbiting details, subtle shimmer on highlights, and calm particle drift are appropriate.
Recommended patterns
- Large dark industrial shell placed on a lighter background with generous radius and premium shadow weight.
- Rounded cards wrapped in thin white-to-transparent gradient borders with dark inner fills and soft inset lighting.
- Micro visual modules such as orbit diagrams, search plates, document chrome, or status widgets built as tactile objects rather than flat illustrations.
- Accent signal dots, progress slivers, or active labels using the chosen brand accent sparingly against a mostly monochrome system.
- Split compositions where one side carries bold editorial copy and the other side stacks molded product or system modules.
- Canvas or particle background texture inside the main shell kept faint so it adds atmosphere without weakening the clean surface hierarchy.
Tuning knobs
- Contrast level: keep the shell dark enough and the text bright enough that the system reads immediately, even when gradients and shadows are subtle.
- Skeuomorphic depth: increase or reduce bevel, inset shadow, and highlight intensity depending on how tactile versus minimal the system should feel.
- Accent intensity: let the brand signal color punctuate the composition, but avoid turning the interface into a neon palette.
- Surface softness: tune radii and shadow blur so components feel premium and manufactured, not puffy or toy-like.
- Structural framing: add or reduce guide lines, separators, and outer rails depending on how technical the presentation should become.
Avoid
- Soft washed-out neumorphism with weak contrast and mushy edges.
- Overly glossy retro skeuomorphism packed with fake materials, leather, or chrome gimmicks.
- Flat monochrome dark UI that ignores the tactile layered-surface character.
- Too many accent colors or bright glows that break the clean industrial mood.
- Overcrowding every module with depth effects until the hierarchy becomes noisy.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.