agentleFS
ccheneyccheney/robust-skills/skills/modern-css/SKILL.md

modern-css

Skill60 starsChanged 2 months agoMITView on GitHub

Implement or debug CSS layouts, responsive styles, themes, and motion. Use when choosing native CSS features or replacing legacy styling with browser-compatible CSS; not for unrelated frontend logic.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the affected markup/styles, desired appearance or interaction, and browser targets as input.

    line 12
  2. Distinctive:

    Use modern CSS as an option, not a mandate to remove JavaScript or rebuild working controls.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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

Modern CSS

Choose native CSS features that fit the requested behavior and supported browsers. The user's explicit instructions take precedence over this skill's guidelines. Preserve the project's framework, preprocessor, tokens, and styling conventions unless changing them is part of the request.

Resolve the styling problem

Use the affected markup/styles, desired appearance or interaction, and browser targets as input. Infer targets from project configuration when available. If missing support information changes the implementation, ask for it or state a conservative fallback.

Bundled support tables are dated research snapshots, not a current compatibility guarantee. Check MDN compatibility data or Web Platform Status for the particular feature when support matters.

NeedStarting point
Rows and columns, or aligned nested tracksGrid / Subgrid
One-dimensional arrangementFlexbox
Layout based on a component's available spaceContainer queries
Cascading overrides or specificity conflictLayers, scope, selector specificity
Themes and derived colorsCustom properties, color functions, color-scheme
Motion, popovers, or scroll effectsFeature-specific reference and fallback

Keep the result usable

  • Preserve layout and interaction in supported browsers. Use progressive enhancement or feature detection where a feature is unavailable.
  • Match cascade changes to the existing origin, importance, and layer ordering; adding a layer can change precedence.
  • Respect reduced-motion preferences and preserve focus/keyboard behavior when changing interactive components.
  • Use modern CSS as an option, not a mandate to remove JavaScript or rebuild working controls. Support and equivalent behavior determine whether a replacement fits.
  • Scope resets and stylesheet reorganization to the task; a component edit does not require a global reset.

Deliver the requested style change or explanation and verify affected layout/states when implementing. State unverified browser limitations rather than treating an example as proof of support.

References

Load only the relevant area, using its contents to find specific features.

TaskReference
Layers, scope, nesting, specificityCASCADE.md
Grid, Flexbox, containers, intrinsic sizingLAYOUT.md
Relational selectors, focus, pseudo-elementsSELECTORS.md
Color spaces, palettes, dark modeCOLOR.md
Custom properties, functions, design tokensTOKENS.md
Transitions, keyframes, entry/exit, view transitionsANIMATION.md
Scroll timelines, sticky states, carouselsSCROLL.md
Dialogs, popovers, anchors, selects, field sizingCOMPONENTS.md
Rendering performance, typography, writing modesPERFORMANCE.md
Compact syntax or feature-detection lookupCHEATSHEET.md

Download now (ZIP)

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.