agentleFS
devdotfastdevdotfast/whiteboard/.agents/skills/deslop-ui/SKILL.md

deslop-ui

Skill3.4k starsChanged 39 days agoMITView on GitHub

Clean up canvas UI code generated by AI in packages/review/app. Use after writing or changing canvas components or styles, before review.

  • Reads credentials

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Hand-rolled controls: Search the kit before keeping any of these, and swap in the kit piece:

    line 23
  2. Very specific:

    Every animation stills under reduced motion: Check each animationName and transition has a stylex.env.reducedMotion branch.

    line 51
  3. Very specific:

    Focus: Look for anything that sets disabled on the button that was just pressed (Send, Retry, an opener while it loads).

    line 52
  4. Distinctive:

    Slop in styles: Delete:

    line 56
  5. Distinctive:

    Tests: Don't add tests that assert class names, CSS text or style objects.

    line 62
  6. Very specific:

    Run pnpm format, pnpm lint and pnpm -w exec tsc --noEmit -p packages/review/app from the repo root.

    line 67
  7. Distinctive:

    Run the canvas tests for the files you touched.

    line 68
  8. Very specific:

    Check the changed surfaces in an isolated Desktop (DEV_FAST_REVIEW_DESKTOP_BACKGROUND=1): dark, light, a narrow width, keyboard focus and …

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review every canvas file the branch changed (git diff origin/main --stat -- packages/review/app). Assume each new style or component is a copy of something the kit already has, and prove otherwise before you keep it.

The kit

Everything below lives in packages/review/app/src/ui/ unless a path says otherwise. Kit modules never import app code.

  • Controls: Button (variant, tone; buttonLook for an anchor drawn as a button), IconButton (aria-pressed for toggles), SegmentedControl, Checkbox, Radio, CheckboxMark (a row that is itself the checkbox), Switch, TextField, TextArea, Select, fieldStyles.bare, Kbd/Shortcut.
  • Overlays: Popover (placed with menuStyles.popover or shellStyles.topbarPopover), useDismissOnOutside, Dialog, OptionMenu in src/option-menu.tsx. Menu rows use menuStyles.item, groups split with menuStyles.separator, arrows move with moveMenuFocus. Disclosures use DisclosureChevron with disclosureStyles.toggle and chevronMarker on the toggle.
  • Feedback: Spinner (spinStyles.turning for a turning icon), ProgressRing, EmptyState, StatusBanner, StatusDot, useCopy/CopyButton, useTooltip, useNotify in src/notify.ts.
  • Glyphs: icons.tsx (24 grid, sized with iconStyles), board and PR-state marks in board-icons.tsx, agent marks through AgentLogo in brand-icons.tsx. Icons are SVG, never Unicode characters.
  • Fragments: textStyles (truncate, clamp2, error, eyebrow, sectionTitle, count), focusStyles.ring/ringInset, buttonStyles.reset, dividerStyles.vertical, surfaceStyles (card, popover, dialog), listRowStyles for sidebar rows, pillStyles/Chip, CrumbSeparator, OverlayScrollbar.
  • Settings use Section/Row from src/settings-section.tsx. Times, durations and counts use src/format.ts.

Checklist

pnpm lint already rejects off-scale literals, !important, bare transparent, raw colors, glyph icons, <select> outside the kit, unused stylex.create keys, Code OSS imports and app imports from src/ui/. The checklist is what lint cannot see.

  • Hand-rolled controls. Search the kit before keeping any of these, and swap in the kit piece:
    • a <button> with its own padding, border, background and font: Button, IconButton or buttonStyles.reset
    • a local <input> or <textarea> look: TextField, TextArea, Checkbox, Radio or Switch
    • a click-outside effect: Popover or useDismissOnOutside
    • a fixed overlay: Dialog
    • a single-choice menu: OptionMenu
    • a rotating chevron: DisclosureChevron with chevronMarker
    • a border-ring spinner: Spinner
    • a copied-state timer: useCopy
    • a sidebar row with its own hover wash: listRowStyles
    • a rounded chip with an inset ring: pillStyles or Chip
    • a notification dot: StatusDot
    • a styled <kbd>: Kbd or Shortcut
    • title= on an icon control: useTooltip
  • Menu and list rows. A row rendered as a <button> stacks focusStyles.ringInset, buttonStyles.reset, then menuStyles.item (or listRowStyles.row + wash). Without the reset the browser's 2px border shows and the row grows.
  • Locked checkboxes. Checkbox dims to half opacity when disabled. A locked-on option (a required item) is checked + disabled with a useTooltip on its wrapper that says why, as onboarding/install-step.tsx does. A dimmed box with no reason reads as broken.
  • Local icons. An inline <svg> belongs in icons.tsx, drawn on its 24 grid and sized with iconStyles. Agent marks go through AgentLogo.
  • Repeated fragments. These become kit fragments:

    • overflow: hidden + textOverflow: ellipsis + whiteSpace: nowrap: textStyles.truncate
    • two-line clamps: textStyles.clamp2
    • error colors: textStyles.error
    • focus outlines: focusStyles.ring / ringInset
    • 1px vertical rules: dividerStyles.vertical
    • bordered figures: surfaceStyles.card
    • hairlines between menu groups: menuStyles.separator

    A pattern that appears a third time goes in the kit.

  • Off-scale values. Don't silence lint with a new step or an inline calc(). Snap to the nearest step, and name a geometry-coupled offset once. Reduced-motion and narrow-width media queries become stylex.env.reducedMotion / stylex.env.narrow; a one-off layout breakpoint may stay local. Replace local spin keyframes and easings with motion.* and spinStyles.
  • Every animation stills under reduced motion. Check each animationName and transition has a stylex.env.reducedMotion branch.
  • Focus. Look for anything that sets disabled on the button that was just pressed (Send, Retry, an opener while it loads). Replace it with a guard in the handler. Popovers and dialogs must close on Escape and give focus back to their trigger.
  • Scrollbars. global.css already styles every native scrollbar in the canvas. Delete local ::-webkit-scrollbar rules. Setting scrollbarWidth or scrollbarColor turns that styling off, and scrollbarColor inherits, so set them only for a scroller that hides its bar on purpose. A main scroller whose bar must not take layout width gets OverlayScrollbar and overlayScrollbarStyles.scroller.
  • Portals. UI portaled outside .review-app needs themeStyles.vars, or kit controls lose their chrome tokens and collapse.
  • Feedback placement. Errors inside a modal render inline with role="alert". Transient success after a surface closes uses useNotify. Don't do both.
  • Slop in styles. Delete:
    • comment-per-property styles
    • descendant selectors (use markers or variants)
    • zIndex literals that stack across surfaces (use layer; order inside one component may stay local)
    • shadows outside elevation
    • duplicate stylex.create blocks that differ by one property (use a variant)
  • Tests. Don't add tests that assert class names, CSS text or style objects. Test behaviour (roles, focus, dismissal) and check the visuals in the Desktop.
  • Style-only refactors. Prove no pixel changed with computed-style diffs before and after, with the pointer moved off the page. Not by eye.

Then:

  1. Run pnpm format, pnpm lint and pnpm -w exec tsc --noEmit -p packages/review/app from the repo root.
  2. Run the canvas tests for the files you touched.
  3. Check the changed surfaces in an isolated Desktop (DEV_FAST_REVIEW_DESKTOP_BACKGROUND=1): dark, light, a narrow width, keyboard focus and reduced motion.
  4. Report what you replaced, and anything you kept local and why.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 16 mentionsOct 2026: 18 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the devdotfast/whiteboard repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about devdotfast/whiteboard

The biggest 5 of 34 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 34

Talked about on GitHub, Bluesky and Hacker News (34 times).

On GitHub · 27

22 more on GitHub

On Bluesky · 6

1 more on Bluesky

On Hacker News · 1

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. KyaniteLabs/tastecheck★ 11same name
    2. samigiman/anti-slop-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.