recursica-skill-badges-chips

Applies house rules for choosing and placing badges versus chips in enterprise web interfaces.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/borderux/recursica-knowledge --skill recursica-skill-badges-chips-borderux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recursica-skill-badges-chips
Source: https://github.com/borderux/recursica-knowledge/tree/main/skills/design-rules/recursica-skill-badges-chips
Command: npx skills add https://github.com/borderux/recursica-knowledge --skill recursica-skill-badges-chips-borderux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designers and AI agents often misuse badges and chips — making status interactive, stacking multiple badges on one object, or scattering heavy badges across dense screens. This Skill encodes opinionated house rules so every status, count, tag, and filter element uses the right component in the right position. ## Core Features & Use Cases - Badge vs. chip decision rules: Interactivity and cardinality determine the component — badges are read-only status, chips handle selection, and one object carries at most one badge. - Placement guidance: Covers table columns, cards, tabs, headings, and sidebar navigation, including the sentence rule (object first, status immediately after). - Density, error, and keyboard constraints: Prefers badges in data-dense views, forbids chips for errors, and defines focus behavior for static badges versus interactive chips. - Use Case: When building a filter bar or labeling table rows with account status, consult this Skill to decide whether each element is a badge, a chip, or just an icon — and where it belongs. ## Quick Start Ask the agent to review your screen design and decide whether each status label, tag, or filter element should be a badge, a chip, or an icon.

Frequently Asked Questions about recursica-skill-badges-chips

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between a badge and a chip in UI design?▼

Use interactivity and cardinality: a badge displays read-only status or metadata and is never interactive, while a chip handles selection or dismissal. One value on an object is a badge; multiple values are chips.

When should a status get its own table column?▼

A status earns its own column only when most rows carry one. Place it in the second or third column, immediately beside the object's identifying information, leaving the first column for bulk-selection checkboxes.

Can a badge be clickable or dismissible?▼

No. Badges must never be interactive, selectable, or dismissible — they are read-only text updated by the system. Dismissible chips are allowed only when the user added them, and toggled chips behave like checkboxes.

Should I use a badge or an icon for status indicators?▼

Prefer an icon by default because a badge is cognitively heavy. Spend a badge only on the object's one primary status where the reader's next decision depends on it; rare exceptions and counts belong to icons or plain text.

What are the limits of using chips for error states?▼

Chips must never indicate errors, and badges for errors are an exception at best since they can read as positive markers. Use a purpose-built treatment such as an icon or another emphasis mechanism instead.