What problem it solves

Coding agents often default to legacy patterns because their training data contains substantial amounts of legacy code, which can produce bloated JavaScript where native web platform solutions are available. They may also know that a modern API exists without having enough real-world implementation patterns to apply it correctly in production-ready code.

Key features

• Context-targeted guidance — A CLI returns targeted, expert-curated guidelines directly into an agent's context window. Guides can be searched and retrieved by identifier.

  Source: README

• Modern browser API patterns — The guidance helps coding agents correctly structure modern browser APIs that are frequently misused and steer implementation away from legacy approaches.

  Source: README

• Legacy pattern scanning — The CLI can scan a codebase for legacy patterns to modernize without requiring a separate installation step.

  Source: README

• Broad modern web coverage — The guides cover recent and emerging web platform features across user experience, CSS layout, performance, forms and UI, accessibility, and built-in AI.

  Source: README

• Compatibility-aware guidance — Guidance incorporates browser compatibility data and responsible fallback practices, including lightweight fallbacks instead of heavy polyfills or legacy libraries.

  Source: README, features

Quick start

Copied verbatim from the project's README.

npx modern-web-guidance@latest install

# Search for relevant guides
npx modern-web-guidance@latest search "animate a dialog modal backdrop"

# Retrieve a guide by ID
npx modern-web-guidance@latest retrieve "animate-to-from-top-layer"

# Scan a codebase for legacy patterns to modernize
npx modern-web-guidance@latest legacy-scan .

Who it may suit

This may suit developers who use coding agents to build web interfaces and want guidance grounded in modern platform capabilities. It may also suit maintainers of agent instructions who need curated, compatibility-aware web development guidance.

Topics to discuss

• Which modern web features should receive more detailed implementation guidance?

• How should browser compatibility information be incorporated into agent-facing guides?

• What criteria should guide the pruning of token-efficient guidance content?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/GoogleChrome/modern-web-guidance-src#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.