Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aws-samples avatar

Ui Css Patterns

  • 1 installs
  • 84 repo stars
  • Updated August 4, 2026
  • aws-samples/review-and-assessment-powered-by-intelligent-documentation

ui-css-patterns is a frontend design-reference skill defining button variants, color semantics, badge colors, and component rules for the RAPID frontend.

About

This skill is a UI and CSS pattern reference for the RAPID frontend. It defines an action hierarchy mapping button variants to actions, color semantics with named Tailwind tokens, status and result badge colors, spacing and typography conventions, and dark-mode pairings. A developer uses it when implementing UI components, choosing button variants or colors, or checking which shared components already exist. It also lists component rules such as using the Button component instead of native buttons.

  • Reference for RAPID frontend UI: button variants, color semantics, and status badge colors
  • Includes a 5-step color decision process and named anti-patterns for buttons
  • Component quick-reference table and rules like never using native button or alert()

Ui Css Patterns by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #1,609 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

ui-css-patterns capabilities & compatibility

Capabilities
ui design · design system reference · component styling
Use cases
ui design · frontend · web design
From the docs

What ui-css-patterns says it does

**Key Pattern**: Outlined primary = cancel/dismiss. Filled primary = submit/create.
SKILL.md
Never use native `<button>` -> use `Button` component
SKILL.md
npx skills add https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation --skill ui-css-patterns

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars84
Last updatedAugust 4, 2026
Repositoryaws-samples/review-and-assessment-powered-by-intelligent-documentation

What it does

Apply RAPID frontend UI and CSS conventions for buttons, colors, badges, and shared components.

Who is it for?

Choosing button variants and colors and reusing shared components while styling the RAPID frontend with Tailwind.

When should I use this skill?

When implementing UI components, choosing button variants or colors, or styling with Tailwind CSS.

By the numbers

  • Includes a 5-step color decision process

Files

SKILL.mdMarkdownGitHub ↗

Frontend UI/CSS Design Patterns

Quick reference for maintaining visual consistency across the RAPID frontend.

Action Hierarchy & Color Semantics

Action TypeButton VariantOutlineExamples
Submit/Createprimaryfalse"Create", "Save", "Compare"
Cancel/Backprimary`true`"Cancel", "Back"
Delete/Removedangerfalse (strong) / true (soft)"Delete Checklist" / inline delete
Alternativesecondaryfalse"Duplicate", "Retry"
UI Toggletextn/a"Show More", "Expand Tree"
Inline Actiontext + size="sm"n/aEdit/Delete in tree nodes
Table Actionvaries`true`"View", "Download"

Key Pattern: Outlined primary = cancel/dismiss. Filled primary = submit/create.

Color Mappings:

  • Primary: aws-sea-blue-light / aws-sea-blue-dark
  • Secondary: aws-aqua
  • Success: aws-lab (brand green), green-500 (icons), green-100/800 (badges)
  • Danger: red (buttons), red-500 (icons), red-100/800 (badges)
  • Warning: yellow-400 (borders), yellow-100/800 (badges)
  • Info: aws-font-color-blue (links), blue-100/800 (badges)

5-Step Color Decision Process

1. Identify Action Context: Completing -> Primary, Abandoning -> Cancel (outlined), Destroying -> Danger 2. Assess Visual Hierarchy: One main action = filled primary, others = outlined/secondary 3. Consider Consequences: Irreversible -> Danger, Mutation -> Primary, Reversible -> Secondary 4. Follow Existing Patterns: grep -r "variant=" frontend/src/features/{similar-feature}/ 5. Validate: "Is this the ONE thing users came here to do?" -> Filled primary

Anti-Patterns:

  • Multiple filled primary buttons in same view
  • Filled danger for reversible actions
  • Primary for cancel/dismiss

Status & Feedback Colors

Toasts: Success -> "success", Error -> "error"

Status Badges: PENDING=Yellow, PROCESSING=Blue, DETECTING=Purple, COMPLETED=Green, FAILED=Red

Review Results: UNDER_REVIEW=Blue, PASS=Green, NOT_PASS=Red, LOW_CONFIDENCE=Yellow, USER_OVERRIDE=AWS Blue

Spacing & Typography

  • Spacing: 8px base (gap-2, gap-4, p-4, p-6)
  • Page containers: max-w-7xl mx-auto px-4 py-8
  • Titles: text-3xl font-bold, Sections: text-xl/text-2xl, Body: text-sm/text-base
  • Dark mode pairs: bg-white dark:bg-aws-squid-ink-dark, text-aws-font-color-light dark:text-aws-font-color-dark

Component Placement Principles

Logical Grouping

Rule: Actions near their context, not right-aligned from unrelated labels.

{/* Vertical: Label -> Content -> Action */}
<div>
  <span className="text-sm font-medium mb-3 block">{t("filter.label")}</span>
  <div className="flex flex-wrap gap-2">{items}</div>
  <div className="mt-3">
    <Button variant="text" size="sm" onClick={handleClear}>{t("filter.clear")}</Button>
  </div>
</div>

Interactive Element Affordance

Critical: cursor-pointer alone is NOT enough. Elements must LOOK interactive before hovering.

<button className="
  cursor-pointer border-2 transition-all
  border-light-gray dark:border-aws-ui-color-dark
  hover:border-aws-sea-blue-light dark:hover:border-aws-sea-blue-dark
  bg-aws-paper-light dark:bg-aws-paper-dark
">
  Interactive Tag
</button>

Smooth Transitions for Conditional UI

<div className={`transition-all duration-300 ${
  isVisible ? 'opacity-100 max-h-10' : 'opacity-0 max-h-0 pointer-events-none'
}`}>

Component Rules

  • Check src/components/ before creating new components
  • Never use native <button> -> use Button component
  • Never use native alert()/confirm() -> use useAlert hook
  • Always use react-icons (SVG prohibited)
  • Always pair color with icon/text for accessibility

Component Quick Reference

Use CaseComponentKey Props
ActionsButtonvariant outline size
Text inputFormTextFieldlabel error required
TextareaFormTextArealabel rows
File uploadFormFileUploadonFilesSelected accept
ModalsModalisOpen onClose title
ConfirmationsuseAlert hookshowAlert showConfirm
Page headerPageHeadertitle description actions
Data tablesTablecolumns data loading
Status badgesStatusBadgestatus
LoadingSkeletoncount height
PaginationPaginationcurrentPage totalPages
ErrorsErrorAlerterror title
InfoInfoAlertmessage variant
BreadcrumbsBreadcrumbitems
Segmented controlSegmentedControloptions value onChange
TooltipsTooltipcontent position

For common layout implementations (page layout, grids, forms, modals, toasts), see references/LAYOUT-PATTERNS.md.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.