Run any Skill in Manus with one click

dev-design-system-keeper

Stars4

Forks0

UpdatedJune 6, 2026 at 04:41

Maintain bord.room V4.1 design-system consistency. Use when changing tokens, primitives, page layouts, accessibility, responsive behavior, visual hierarchy, icons, density, tables, cards, forms, or dashboard surfaces.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

zreed3

zreed3/agentic-development-platform

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

SKILL.md

readonly

name	dev-design-system-keeper
description	Maintain bord.room V4.1 design-system consistency. Use when changing tokens, primitives, page layouts, accessibility, responsive behavior, visual hierarchy, icons, density, tables, cards, forms, or dashboard surfaces.

bord.room Design System Keeper

Use this for UI consistency and visual QA.

Check

Existing tokens in apps/web/src/styles/globals.css.
Existing primitives in packages/ui/src/primitives.
Existing domain layouts before adding new composition.
Responsive constraints for fixed-format UI.
Accessibility labels, focus rings, contrast, keyboard order, and reduced-motion behavior.

Rules

Use the smallest existing primitive that fits.
Avoid nested cards and marketing-style shells for operational tools.
Keep text fitted at mobile and desktop widths.
Use icons for familiar tool actions where available.
Add screenshots or browser checks for risky visual changes.

More from this repository

same repository

adg-backlog-decompose

zreed3/agentic-development-platform

Decompose a feature or intent into small, context-bound backlog items in the SQL backlog, for a planning model (Opus or Sonnet). Use before a swarm of workers: turn one feature into tightly scoped, logged items, each with a write scope and a context profile, so cheaper sub-agents can each work one item in isolation and total token use drops.

2026-06-154

adg-backlog-swarm

zreed3/agentic-development-platform

Orchestrate a context-bound, backlog-logged multi-agent swarm to cut token use. Use to run a feature as a planner (Opus or Sonnet) that logs small backlog items, then cheaper workers (Sonnet or Haiku) that each implement one item under its bounded context packet, while the parent keeps integration, the SQL backlog, the audit log, and verification.

2026-06-154

adg-evidence-curator

zreed3/agentic-development-platform

Select, record, and validate ADG evidence. Use when choosing targeted checks, recording failed commands, linking tests to requirements, writing audit events, registering advisory gaps, or preparing feature/release evidence.

2026-06-154

adg-feature-elicitation

zreed3/agentic-development-platform

Elicit generic ADG feature intent into a normalized requirements graph. Use when naming a feature, defining how it fits the platform, deriving RBAC-aligned stories and use cases, or creating success, anti-success, scenario, and gap evidence in config/agentic/elicitation.json.

2026-06-154

adg-item-worker

zreed3/agentic-development-platform

Work a single backlog item under a bounded context packet, for a context-cheap sub-agent (Sonnet or Haiku). Use when an orchestrator hands you one item id to implement in isolation: claim it, load only its context:item packet, edit only its write scope, record evidence, and complete it. Keeps token use low and work traceable.

2026-06-154

adg-quick-ui-fix

zreed3/agentic-development-platform

Use for small UI, copy, docs, styling, or visual polish fixes that should avoid full governance unless risk increases.

2026-06-154

Run any Skill with one click