agentsclimarketplace

Sync design

Skill sahildave/skilltopia/.agents/skills/sync-design

Skilltopia is a desktop and web app for discovering, reviewing, and installing agent skills. It helps developers browse the public skills catalog, inspect skill details and audit metadata, and manage locally installed global skills from one interface.

Install
npx -y skills add sahildave/skilltopia --skill sync-design

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

  • 18 days oldThe repository was created 18 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

Reconcile docs/design/DESIGN.md with the current CSS design implementation after Chrome Inspect or UI changes. Use for design-system updates, token drift, typography changes, spacing changes, component styling changes, or motion changes.

SKILL.md

1.9 KB, as published. Nobody here has run it

Sync Design System

Keep docs/design/DESIGN.md as the single agent-facing design source. Never create a second token file or a reference copy.

Workflow

  1. Read docs/design/DESIGN.md, src/theme-variables.css, src/App.css, src/quick-pane.css, and the changed UI files.
  2. Run npm run design:sync to reconcile frontmatter values that can be derived deterministically from the CSS source.
  3. Update the Markdown prose in DESIGN.md when the change affects visual intent, component behavior, spacing, typography, accessibility, responsive behavior, or motion.
  4. Keep the Stitch YAML frontmatter and prose consistent. Frontmatter is the structured design contract; prose explains how to apply it.
  5. Run npm run design:check and git diff --check.

Guardrails

  • Do not overwrite intentional design decisions just because an unrelated CSS value differs; inspect the change and update the design contract deliberately.
  • Use semantic token names and preserve the existing Tailwind/shadcn patterns.
  • Keep runtime values in src/theme-variables.css; do not add a parallel tokens.json or duplicate design document.
  • If the source change is ambiguous, report the mismatch and ask for a design decision instead of guessing.

Useful commands

  • npm run design:check — fail when derivable CSS tokens drift from DESIGN.md.
  • npm run design:sync — update derivable frontmatter tokens and print the remaining semantic pass.
  • npm run design:watch — watch CSS/design files and sync derivable tokens as they change during Chrome Inspect work.

Gives 0 of the 12 instructions most css styling skills give

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

  • avoid excessive centered layoutsin 55 of 586, across 12 files
  • bundle code into single HTML filein 54 of 586, across 14 files
  • Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
  • avoid purple gradientsin 51 of 586, across 11 files
  • avoid uniform rounded cornersin 51 of 586, across 11 files
  • avoid Inter fontin 51 of 586, across 11 files
  • edit generated files to develop artifactin 50 of 586, across 10 files
  • animate only transform and opacity propertiesin 43 of 586
  • Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
  • Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
  • use tailwind cssin 39 of 586, across 24 files
  • Use SVG icons instead of emojisin 38 of 586, across 11 files

Said here and by no other author read

  • read design and changed CSS files
  • run design sync to reconcile frontmatter
  • update prose for visual or behavioral changes
  • keep frontmatter and prose consistent
  • run design check and git diff check
  • preserve existing Tailwind and shadcn patterns

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

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.