Bento
- 110 installs
- 2.2k repo stars
- Updated June 28, 2026
- bergside/awesome-design-md-skills
bento is a design-system skill that authors UI guidelines for a modular bento-grid layout of card-like blocks in varying sizes for scannable interfaces.
About
This skill makes the agent a design-system guideline author for the Bento style, a modular grid layout of card-like blocks in varying sizes for organized, scannable interfaces. It supplies concrete tokens (Inter typography, a #FAD4C0 primary, an #FFF5E6 surface, a 4/8/12/16/24/32 spacing scale), WCAG 2.2 AA accessibility rules, and a required output structure with component rules and a QA checklist. A developer uses it to build clean, scannable bento-grid layouts consistently.
- Authors design-system guidance for a modular bento-grid layout style
- Ships concrete tokens: Inter type, #FAD4C0 primary, #FFF5E6 surface
- Enforces WCAG 2.2 AA and a code-review QA checklist
Bento by the numbers
- 110 all-time installs (skills.sh)
- Ranked #1,091 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
bento capabilities & compatibility
- Capabilities
- design system · ui design · design tokens
- Use cases
- ui design · web design
What bento says it does
Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.
The bento box style is an innovative design approach that uses a grid layout to present content in visually appealing blocks of varying sizes.
Tokens: primary=#FAD4C0, secondary=#80A1C1, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFF5E6, text=#111827
npx skills add https://github.com/bergside/awesome-design-md-skills --skill bentoAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 110 |
|---|---|
| repo stars | ★ 2.2k |
| Last updated | June 28, 2026 |
| Repository | bergside/awesome-design-md-skills ↗ |
What it does
Generate design-system guidance for a modular bento-grid layout style of card-like blocks.
Who is it for?
Building organized, scannable interfaces with a modular grid of card-like blocks using defined tokens.
When should I use this skill?
You need design-system rules or tokens for a bento-grid, card-block layout.
What you get
A token-driven, WCAG 2.2 AA guideline for a clean, scannable bento-grid interface.
- Design-system guidance covering tokens, component rules, accessibility criteria, and a QA checklist
By the numbers
- Typography scale 12/14/16/20/24/32
- Spacing scale 4/8/12/16/24/32
Files
<!-- TYPEUI_SH_MANAGED_START -->
Bento Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Bento. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
The bento box style is an innovative design approach that uses a grid layout to present content in visually appealing blocks of varying sizes.
Style Foundations
- Visual style: modern, clean
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#FAD4C0, secondary=#80A1C1, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFF5E6, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules. 2. Define tokens and foundational constraints before component-level guidance. 3. Specify component anatomy, states, variants, and interaction behavior. 4. Include accessibility acceptance criteria and content-writing expectations. 5. Add anti-patterns and migration notes for existing inconsistent UI. 6. End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
<!-- TYPEUI_SH_MANAGED_END -->
Overview
Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.
Style Foundations
- Visual style: modern, clean
- Typography scale: 12/14/16/20/24/32
- Typography fonts: primary=Inter, display=Inter, mono=JetBrains Mono
- Typography weights: 100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger
- Spacing scale: 4/8/12/16/24/32
Colors
- Primary (#FAD4C0): Token from style foundations.
- Secondary (#80A1C1): Token from style foundations.
- Success (#16A34A): Token from style foundations.
- Warning (#D97706): Token from style foundations.
- Danger (#DC2626): Token from style foundations.
- Surface (#FFF5E6): Token from style foundations.
- Text (#111827): Token from style foundations.
- Neutral (#FFF5E6): Derived from the surface token for official format compatibility.
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.716k165k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.498k29.6k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst389k16k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k476
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.301k69.4k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.290k112kFAQ
What is the bento style?
A modular grid layout that presents content in visually appealing blocks of varying sizes, with clear hierarchy, soft spacing, and subtle contrast, using Inter type and a #FAD4C0 primary.
What surface color does it use?
A warm #FFF5E6 surface with a 4/8/12/16/24/32 spacing scale.