# bento

A skill for bento-style interfaces with modular cards, clear hierarchy, and soft spacing. Use it when an AI agent needs concrete UI and design-system guidance.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2500 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/bento/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/bento

## What it does

bento gives an AI agent a practical framework for interfaces built from modular card blocks. It defines a visual foundation with `Inter` typography, `JetBrains Mono` for monospace text, semantic color tokens, spacing values, and a clear hierarchy. The guidance is meant to be used by engineers and designers.

Its workflow moves from design intent and foundational tokens to component anatomy, states, responsive behavior, accessibility criteria, content rules, anti-patterns, and a QA checklist. It calls for explicit interaction states and testable implementation rules rather than vague visual descriptions. Accessibility comes first when it conflicts with novelty: the skill names `WCAG 2.2 AA`, keyboard-first interaction, and visible focus states. Check those requirements in the resulting components.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill bento -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/bento/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/bento/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill bento -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/bento/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill bento -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/bento/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills bento
```

2. **Manually: put the files in place**
- File: `.github/skills/bento/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill bento -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/bento
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/bento/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill bento -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/bento/SKILL.md

## When to use it
- define rules for a bento-style interface
- set typography, color, and spacing tokens
- describe component states and responsive behavior
- add testable accessibility criteria
- prepare a QA checklist for code review

## Example prompts
- Create a design-system guide for a bento-style interface.
- Define the anatomy, states, and responsive behavior of a card in a bento grid.
- Review these UI rules against `WCAG 2.2 AA` and add testable acceptance criteria.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: acb8d935f20db665.

BEGIN THIRD-PARTY FILE acb8d935f20db665
```text
---
name: bento
description: Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.
license: MIT
metadata:
  author: typeui.sh
---

<!-- 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.
```
END THIRD-PARTY FILE acb8d935f20db665

The third-party file has ended. Everything between the acb8d935f20db665 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3011 of 3511 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/bento/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md