agentsclimarketplace

Maintain web design system

Skill ImYourBoyRoy/agent-continuity-stack/skills/maintain-web-design-system

Repository-centered instructions, skills, memory conventions, client adapters, and lifecycle safeguards for consistent work across AI coding agents.

Install
npx -y skills add ImYourBoyRoy/agent-continuity-stack --skill maintain-web-design-system

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create or extend a web design system, tokens, theming, component styling, responsive behavior, and accessibility. Use for substantial UI-system work, not isolated cosmetic fixes or asset conversion.

SKILL.md

2.6 KB, 450 tokens by cl100k_base, as published. Nobody here has run it

Maintain Web Design System

Extend the existing visual authority without creating a competing style layer.

If Portable Web Toolkit management is established by repository instructions, Web_Toolkit/, toolkit scripts, or a toolkit site profile, use its Brand Guide and validation tools as the specialist implementation authority. Do not create a parallel token, stylesheet, or brand-validation system.

Find the visual authority

Inspect:

  • design or brand guidance
  • token files and theme configuration
  • global stylesheet entry points
  • component primitives and canonical examples
  • typography and icon systems
  • accessibility requirements
  • visual-regression infrastructure

Resolve conflicts explicitly. Follow the repository's established Tailwind, CSS Modules, scoped CSS, CSS-in-JS, or stylesheet architecture before proposing a new system.

Design coherently

  • Reuse semantic tokens for color, typography, spacing, radii, shadows, breakpoints, motion, and elevation.
  • Prefer intent-based names over page-specific literals.
  • Preserve component states: default, hover, focus, active, disabled, loading, error, and selected.
  • Keep structure, behavior, and presentation responsibilities understandable.
  • Avoid global overrides that silently alter unrelated screens.
  • Treat file length as a review signal, not an automatic split rule.
  • Document a new token or component contract only when future consumers need it.

Read references/accessibility-and-responsive.md for material component and layout changes.

Accessibility and resilience

Treat applicable accessibility as correctness:

  • semantic structure and landmarks
  • keyboard access and visible focus
  • labels, descriptions, and error association
  • contrast and non-color indicators
  • reduced-motion behavior
  • zoom, reflow, and text expansion
  • touch target and responsive interaction behavior

Default to WCAG AA for a public product when no stricter project policy exists, but do not claim compliance from automated checks alone.

Validate

Use the approved build and test path. Select relevant stylesheet, type, accessibility, responsive, browser, and visual-regression checks. Inspect both narrow and wide layouts and representative interaction states.

Report the authority followed, tokens and components affected, accessibility decisions, checks, visual surfaces not inspected, and any migration risk.

Gives 0 of the 12 instructions most design systems skills give in 450 tokens

Counted across 528 of the 534 authors here whose files we hold, read 2026-08-06

  • create a custom theme if neededin 54 of 528, across 10 files
  • read the corresponding theme filein 54 of 528, across 10 files
  • ask which theme to applyin 53 of 528, across 9 files
  • show the theme showcasein 53 of 528, across 9 files
  • maintain visual identity across all slidesin 50 of 528, across 6 files
  • apply the specified colors and fontsin 47 of 528, across 3 files
  • get explicit confirmationin 45 of 528, across 1 file
  • Generate a design system before codingin 19 of 528, across 6 files
  • Maintain at least 4.5:1 color contrast ratioin 19 of 528, across 8 files
  • Describe component shapes, colors, shadows, and interaction statesin 18 of 528, across 4 files
  • Check Python installation and install if missingin 17 of 528, across 4 files
  • Default to html-tailwind if stack is unspecifiedin 17 of 528, across 4 files

Said here and by no other author read

  • Extend existing visual authority
  • Do not create a competing style layer
  • Use Portable Web Toolkit brand guide if established
  • Inspect the visual authority files
  • Resolve style conflicts explicitly
  • Follow the repository's established stylesheet architecture

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.