ui-modern-2026
Skill0 starsChanged 3 months agoMITView on GitHub
Use when evaluating or adopting modern web UI capabilities such as contemporary CSS layout, container queries, relational selectors, native dialogs/popovers, view transitions, newer color functions, or progressive enhancement while preserving compatibility and accessibility.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use modern platform capabilities when they simplify the interface or improve experience, with explicit compatibility and fallback reasoning.
- Very specific: line 14
Do not activate merely to make a UI visually “modern.” Visual direction belongs to frontend-aesthetics.
- Distinctive: line 19
Prefer stable platform features when they remove complexity, but do not chase novelty for its own sake.
- Distinctive: line 20
Verify current browser/toolchain support for any capability that is version-sensitive.
- Distinctive: line 23
Do not force a CSS color-space migration or a component-library migration as collateral work.
- Distinctive: line 32
Add the modern enhancement behind natural CSS feature behavior or capability detection where necessary.
- Distinctive: line 33
Test keyboard, focus, reduced motion, responsive layout, and supported browsers.
- Distinctive: line 34
Run normal repository checks.
- Very specific: line 36
Read references/modern-css.md for capability categories and references/effects-catalog.md when selecting restrained visual effects.
- Distinctive: line 38
Use the static scanner to find modern CSS features already present:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Modern UI 2026
Use modern platform capabilities when they simplify the interface or improve experience, with explicit compatibility and fallback reasoning.
Use when
Activate for requests to modernize CSS/UI implementation, replace JavaScript with capable platform primitives, evaluate newer CSS features, adopt progressive enhancement, or review whether newer browser APIs can simplify an interface.
Do not activate merely to make a UI visually “modern.” Visual direction belongs to frontend-aesthetics. Color-system work belongs to chromatic-design.
Rules
- Detect the project's browser support policy, framework, CSS tooling, component library, and existing progressive-enhancement strategy first.
- Prefer stable platform features when they remove complexity, but do not chase novelty for its own sake.
- Verify current browser/toolchain support for any capability that is version-sensitive.
- Preserve accessibility semantics and keyboard/focus behavior when replacing scripted components with native primitives.
- Provide a fallback when absence of the feature would break core functionality; enhancement-only features may degrade gracefully.
- Do not force a CSS color-space migration or a component-library migration as collateral work.
Workflow
- Identify the current implementation pain: excess JS, brittle viewport media queries, complex DOM targeting, animation plumbing, custom overlay behavior, or duplicated responsive variants.
- Inspect declared browser targets and actual deployment audience if available.
- Choose the smallest platform capability that addresses the pain.
- Separate required behavior from enhancement.
- Implement a safe baseline first when compatibility requires it.
- Add the modern enhancement behind natural CSS feature behavior or capability detection where necessary.
- Test keyboard, focus, reduced motion, responsive layout, and supported browsers.
- Run normal repository checks.
Read references/modern-css.md for capability categories and references/effects-catalog.md when selecting restrained visual effects. Read references/component-library-integration.md before changing behavior owned by a component library.
Use the static scanner to find modern CSS features already present:
python scripts/scan_modern_css.py <project-root> --jsonExamples of appropriate capabilities
Depending on current support and project policy: container queries, :has(), logical properties, subgrid, cascade layers, @supports, modern color functions, native dialog/popover behaviors, scroll-driven/view-transition enhancements, and reduced-motion-aware transitions.
This list is illustrative, not a requirement. Verify current support rather than relying on the skill's publication year.
Avoid
- Adding a polyfill for an enhancement that can simply degrade.
- Replacing a mature accessible component with a native primitive without checking missing behavior.
- Using experimental APIs in critical paths without explicit product acceptance.
- Large visual effect stacks that reduce readability/performance.
- Assuming desktop Chrome support equals project support.
- Shipping motion without reduced-motion consideration.
Output
State the current implementation, capability selected, compatibility evidence/policy, baseline/fallback, accessibility implications, files changed, and tests actually performed.
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
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.

