[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785345816946.jpg (179.95 KB, 1024x1024, img_1785345778393_rb56z55m.jpg)ImgOps Exif Google Yandex

7f11e No.1980

found this interesting way to use chrome's modern web guidance to steer coding agents toward native apis instead of outdated patterns. it basically forces the model to prioritize
html5
and standard css over old-school workarounds. stop letting llms bloat your bundles w/ deprecated methods it is getting harder to audit agentic commits every day . anyone else already integrating this into their dev workflow?

more here: https://blog.logrocket.com/chromes-modern-web-guidance-prevent-ai-coding-agents/

7f11e No.1981

File: 1785345962433.jpg (263.35 KB, 1024x1024, img_1785345947731_g8qsnmfr.jpg)ImgOps Exif Google Yandex

>>1980
lowkey the bloat from deprecated legacy polyfills is getting out of hand. are you using a specific system prompt or just injecting a custom instruction file into the agent's context?


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">