Files
ssmithxandClaude Opus 5.5 590456a020 docs: require maintainer UI/UX UAT approval on PRs that touch UI
Every contributor and AI agent opening a PR that changes UI starts the
description with "Requires UI/UX UAT approval from the maintainer" and lists
the screens and flows to review. The PR is not merged until the maintainer
approves. Added to AGENTS.md (full rule), CLAUDE.md (Claude Code reads only
that file), the archipelago-design skill and the PR template.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 12:12:55 +00:00

2.2 KiB

name, description, metadata
name description metadata
archipelago-design Create or change Archipelago UI using the shared semantic tokens, components, responsive patterns, accessibility states, and embedded/standalone host contract.
short-description
Keep Archipelago UI consistent

Archipelago design system

Use this skill for any new or changed Archipelago UI, including app screens, Terminal, setup flows, dialogs, dashboards, and app wrappers. Read design-contract.md before implementation.

Rules

  • A PR with any UI change starts its description with Requires UI/UX UAT approval from the maintainer, then lists the screens and flows to review (see AGENTS.md). It is not merged before the maintainer approves.
  • Find and reuse the closest shared component and pattern before creating one.
  • Use semantic --archy-* tokens and the pinned kit version. A bespoke color, font, radius, shadow, or z-index needs a documented reason.
  • Preserve the dark baseline, readable surfaces, 4px spacing rhythm, bottom action placement, 44px touch targets, visible focus, and safe-area behavior.
  • Keep terminal/editor/tmux keys inside the terminal focus boundary; generic modal Escape/arrow handlers must not consume them.
  • Implement loading, empty, offline, denied, validation-error, retry, disabled, and confirmed-success states. Status color must have text or icon support.
  • Test standalone and embedded modes. Embedded apps do not duplicate the host wallpaper or navigation and must work without a host handshake.

Workflow

  1. Read the reference screen and source; choose the matching component/pattern.
  2. Build with the shared kit and local assets, not runtime dashboard CSS or CDN fonts. Keep host RPC, signer, and credential bridges behind typed adapters.
  3. Render the gallery/preview at required viewports and inspect screenshots and keyboard behavior. Check contrast on the real composited surface.
  4. Record deliberate exceptions and update the kit only when a reusable need is demonstrated. Do not silently accept visual-diff changes.

References