design-fundamentals
This skill should be used when making UI/UX decisions, designing layouts, choosing colors and typography, writing UI specs, or reviewing visual components. Contains the two-path design flow (existing system vs greenfield discovery), accessibility rules, typography pairing, color palette guidance using Sanzo Wada's Dictionary of Color Combinations, spatial composition, anti-generic rules, and visual quality checklist.
Install
With your agent
Install OMGSkills skill "incubyte/ai-plugins:bee/skills/design-fundamentals" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/incubyte/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/bee/skills/design-fundamentals ~/.claude/skills/design-fundamentalsFrom README
Design Fundamentals Reference principles for any Bee agent producing, evaluating, or documenting UI work. These apply universally — the target project's design system provides specific values on top of these. --- Two-Path Design Flow Before applying any design principle, determine which path you're on: Path A — Existing Design System: The project has design tokens, Tailwind config, CSS custom properties, or a component library. Follow what exists. Never override. Never suggest alternatives. Extract, document, and ensure new work is consistent with the established system. Path B — Greenfield (No Design System): No design system detected. Run a design discovery with the developer using AskUserQuestion before making any visual decisions. See the Design Discovery section below.
More from this repo
ai-ergonomics
This skill should be used when evaluating how well code supports LLM-assisted development.
ai-workflow
This skill should be used when explaining why Bee follows spec-first TDD workflows, or when teaching mode is on.
architecture-patterns
This skill should be used when evaluating architecture options, checking dependency direction, or deciding between...