modern-web-guidance
Skill1 starsChanged 49 days agoApache-2.0View on GitHub
Human-grade modern web architecture & UI/UX guidance. Enforces zero-slop design, native HTML/CSS/JS capabilities, soft drop shadow depth over heavy strokes (stroke max 1px), sharp border-radius, context-aware typography, and zero-comment code.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- ManatoYamashita/skillstheir own version, first seen Nov 1, 2026
- anis-dr/skillstheir own version, first seen Oct 15, 2026
- GoogleChrome/modern-web-guidancetheir own version, first seen Oct 8, 2026
- JameMy0001/antigravity-skills-hubtheir own version, first seen Oct 2, 2026
- lintangknitto/agent-skillstheir own version, first seen Sep 23, 2026
Used with
Projects with it also use chrome-extensions, code-review-and-quality and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
thistleknotSkillchrome-extensions
Build, install and verify a personal Chrome extension that does something on the local machine (write a file, run a script) when its toolbar button is clicked. Covers the Manifest V3 extension + native-messaging host pattern, pinning the extension ID with a "key", registering the host under HKCU (no admin), the one manual "Load unpacked" step and why automation cannot do it, and how to test the real Chrome round trip yourself without clicking the toolbar. Trigger on "chrome extension", "browser button that saves to a file", "native messaging", "clip the page to a file", "load unpacked", "extension shows a red !".
Also in 4 projects that use this
LLl0k0laDSkillcode-review-and-quality
Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Also in 3 projects that use this
VercelSkillfind-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- GoogleChrome/modern-web-guidance★ 2.6ksame name
- JetBrains/skills★ 386same name
- anis-dr/skills★ 3same name
- yuusakuri/agent-skills★ 2same name
- JameMy0001/antigravity-skills-hub★ 1same name
- ManatoYamashita/skills★ 1same name
- dmarafetti/ai-writer-extension★ 0same name
- ethosure/coding_ethos★ 0same name
- lintangknitto/agent-skills★ 0same name
- patterson-agents/skills★ 0same name
1 more not listed
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 repository21 other files it gives its agents.
- min-tokSkill
- academic-scholarSkill
- agent-mcp-craftSkill
- anti-overengineeringSkill
- api-security-reviewerSkill
- data-verifySkill
- deep-researcherSkill
- design-no-slopSkill
- enterprise-teamSkill
- git-craftSkill
- human-codingSkill
- laravel-architectSkill
- markdown-docSkill
- modern-stack-horizonSkill
- omni-pilotSkill
- perf-benchmarkSkill
- python-bug-fixerSkill
- react-ui-architectSkill
- reverse-engineer-anythingSkill
- typescript-nodeSkill
- tyw-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 3 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use subtle, natural shadows for card elevation, floating navigation, popovers, and containers.
- Very specific: line 25
Avoid heavy borders (border-2, border-4) or high-contrast dark outlines that trap content.
- Very specific: line 26
If a stroke is necessary for boundary definition, it MUST be 1px maximum (border / border-[1px]).
- Very specific: line 27
Always use soft, low-contrast, harmonious border colors: border-zinc-200/70, border-stone-200/80, or border-zinc-800/60 in dark mode.
- Very specific: line 31
STRICTLY BANNED: Never use pill shapes (rounded-full) for containers, cards, buttons, or eyebrow divs.
- Very specific: line 41
Option 1 (Typographic Lead): Start directly with the <h1> with strong visual hierarchy and proportional line height.
- Very specific: line 42
Option 2 (Unboxed Editorial Kicker): If a category is needed, use plain text with letter-spacing: <p class="text-xs uppercase …
- Very specific: line 48
HUMAN STANDARD: Always use crisp inline vector <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5" ...> with …
- Very specific: line 51
Never blindly default to generic Inter for every use case:
- Very specific: line 67
Use the native HTML <dialog> element instead of custom overlay libraries:
- Distinctive: line 82
CSS Grid & Bento Layouts: Prefer asymmetric, intentional grid layouts over repetitive 3-column identical cards.
- Very specific: line 94
LCP Image Prioritization: Always add fetchpriority="high" and omit loading="lazy" on above-the-fold hero images.
- Very specific: line 95
Offscreen Content Optimization: Use content-visibility: auto.
- Very specific: line 96
Smooth Native Transitions: Use native View Transitions API (document.startViewTransition) where applicable for seamless state changes.
- Distinctive: line 105
Ensure zero comments in generated markup and styles.
“Common” is measured: kept by at least 6 in 10 of the 11 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.
Files
Modern Web Guidance (Human-Grade Web & Zero-Slop Architecture)
This skill guides the agent to build clean, modern, high-performance web applications using native Web Platform standards and senior human-grade UI/UX principles—eliminating AI slop, heavy strokes, and redundant third-party package dependencies.
1. Visual Elevation: Ambient Drop Shadows over Heavy Strokes
A. The Hierarchy of Depth: Shadow > Stroke
Real modern UI achieves depth, contrast, and visual hierarchy through diffuse, ambient lighting and soft drop shadows, rather than boxing every element in harsh borders.
- PREFERRED (Ambient Soft Drop Shadows):
- Use subtle, natural shadows for card elevation, floating navigation, popovers, and containers.
- Tailwind examples:
shadow-sm,shadow,shadow-md(with gentle diffuse blurs). - Vanilla CSS:
box-shadow: 0 1px 3px rgba(0, 0, 0, 0.06), 0 4px 12px rgba(0, 0, 0, 0.03); - Elevate interactive elements on hover: transition smoothly to
shadow-mdorshadow-lg.
- RESTRICTED: Stroke & Border Limit (1px Maximum):
- Avoid heavy borders (
border-2,border-4) or high-contrast dark outlines that trap content. - If a stroke is necessary for boundary definition, it MUST be 1px maximum (
border/border-[1px]). - Always use soft, low-contrast, harmonious border colors:
border-zinc-200/70,border-stone-200/80, orborder-zinc-800/60in dark mode.
- Avoid heavy borders (
- Sharp Border Radius (1px to 3px /
rounded-sm):- In accordance with sharp-edge design standards, maximum border-radius is 1px to 3px (
rounded-sm). - STRICTLY BANNED: Never use pill shapes (
rounded-full) for containers, cards, buttons, or eyebrow divs.
- In accordance with sharp-edge design standards, maximum border-radius is 1px to 3px (
2. Anti-AI Design Slop (Strict UI Standards)
A. Absolute Ban on the "Floating Pill Badge" Div
AI models habitually dump a colored pill capsule above every hero heading:
- BANNED:
<div class="rounded-full border border-red-200 bg-red-50 text-red-700 px-3 py-1 text-xs mb-4">...</div> - THE HUMAN WAY:
- Option 1 (Typographic Lead): Start directly with the
<h1>with strong visual hierarchy and proportional line height. - Option 2 (Unboxed Editorial Kicker): If a category is needed, use plain text with letter-spacing:
<p class="text-xs uppercase tracking-[0.2em] font-semibold text-zinc-500 mb-4">CATEGORY · STATUS</p>.
- Option 1 (Typographic Lead): Start directly with the
B. Clean Inline Vector SVGs Only (Zero Emojis & Zero Script Icons)
- BANNED:
- Emojis in buttons and headers (
🚀 Mulai,⚡ Fitur,🔥 Populer). - Script-injected runtime icons (
<i data-lucide="send"></i>).
- Emojis in buttons and headers (
- HUMAN STANDARD: Always use crisp inline vector
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5" ...>witharia-hidden="true".
C. Context-Aware Typography
Never blindly default to generic Inter for every use case:
- Editorial / Literary / Heritage:
Playfair Display,Instrument Serif, orFraunces(Headings) +LoraorSource Serif 4(Body). - SaaS / Tech / Dev Tools:
Plus Jakarta Sans,Cabinet Grotesk, orSatoshi(Headings) +DM Sans(Body) +JetBrains Mono(Data/Tables). - Creative Studio / Modern Agency:
Bricolage GrotesqueorSyne(Headings) +Outfit(Body).
D. Zero-Comment Markup
- BANNED:
<!-- ================= NAVBAR ================= -->,<!-- Hero Section -->,/* Modern card styling */. - HUMAN STANDARD: Zero HTML and CSS comments. Semantic tags (
<nav>,<header>,<main>,<section id="hero">,<footer>) speak for themselves.
3. Modern Web Platform Standards (Native First)
Eliminate heavy JavaScript dependencies by utilizing modern, native Web Platform features:
A. Modals & Dialogs
Use the native HTML <dialog> element instead of custom overlay libraries:
<dialog id="confirm-modal" class="rounded-sm shadow-xl border border-zinc-200/80 p-6 backdrop:bg-zinc-950/40 backdrop:backdrop-blur-sm">
<form method="dialog">
<h3 class="text-lg font-semibold text-zinc-900">Konfirmasi Tindakan</h3>
<p class="text-sm text-zinc-600 mt-2">Apakah Anda yakin ingin melanjutkan proses ini?</p>
<div class="mt-6 flex justify-end gap-3">
<button value="cancel" class="px-4 py-2 text-sm text-zinc-700 hover:bg-zinc-100 rounded-sm">Batal</button>
<button value="confirm" class="px-4 py-2 text-sm bg-zinc-900 text-white rounded-sm shadow-sm">Lanjutkan</button>
</div>
</form>
</dialog>B. Modern CSS Layout & Selectors
- CSS Grid & Bento Layouts: Prefer asymmetric, intentional grid layouts over repetitive 3-column identical cards.
- Parent & State Selection with
:has(): Target parent cards based on child states without extra JS event listeners:.card:has(input:checked) { box-shadow: 0 4px 16px rgba(0, 0, 0, 0.08); border-color: rgb(39 39 42 / 0.8); } - Container Queries (
@container): Style components based on container width rather than viewport width. - Form Validation State with
:user-valid/:user-invalid: Provide immediate, non-annoying validation styling that only triggers after user interaction.
C. Performance & Core Web Vitals (CWV)
- LCP Image Prioritization: Always add
fetchpriority="high"and omitloading="lazy"on above-the-fold hero images. - Offscreen Content Optimization: Use
content-visibility: auto; contain-intrinsic-size: 1px 500px;on long scrollable sections to drastically reduce initial rendering work. - Smooth Native Transitions: Use native View Transitions API (
document.startViewTransition) where applicable for seamless state changes.
4. Execution Interlock
Whenever working on Web, UI components, HTML, CSS, or frontend layouts:
- Prioritize ambient drop shadow depth over heavy strokes (borders maximum 1px).
- Maintain sharp border radius (1px - 3px /
rounded-sm). - Ensure zero comments in generated markup and styles.
- Deliver 100% working, responsive, self-documenting code.
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.

