Agent and developer resources

When to use

• Core Web Vitals in the field
  Diagnosing LCP, INP or CLS on a real site — what to measure, which panel to open, and why lab numbers and field data disagree.
• Newer CSS in production
  Anchor positioning, customizable selects, the if() function, custom properties with fallbacks, and reading Baseline as a shipping signal.
• Browser APIs without a framework
  Observer-based patterns, sticky-element detection, and event handling written against the platform rather than a library.
• Next.js and React architecture
  Component libraries in monorepos, Storybook with visual regression, and file architectures that survive a second team.
• Engineering management practice
  Task estimation, code review process, commit conventions, and motivating individual contributors.
• Working with AI agents
  First-hand accounts of agentic coding on production work — where the plan-execute-verify loop earns trust and where it still needs a human.

When not to

• Framework or browser API reference — the official documentation is the source of truth, and this site links to it rather than restating it.
• Breaking news or release notes. Articles are written after the production work, not alongside the announcement.
• Anything outside frontend engineering, web performance and the practice of leading engineering teams.

Fetching

• Content negotiation
  Send `Accept: text/markdown` to any canonical URL. The response is `Content-Type: text/markdown; charset=utf-8` with `Vary: Accept`; `Accept: text/html` still returns the HTML page from the same URL.
• Explicit .md URLs
  Append `.md` to any path — https://www.dainemawer.com/index.md, https://www.dainemawer.com/about.md, https://www.dainemawer.com/<article-slug>.md. Useful for clients that send no Accept header at all.
• Whole-site text
  https://www.dainemawer.com/llms-full.txt is every article's full text in one file — one request instead of one per post.
• Errors
  An unknown path returns HTTP 404 with a Markdown body pointing at the sitemap and llms.txt. A client that accepts neither HTML nor Markdown gets HTTP 406.

Endpoints

• llms.txt
  Structured index of every article, topic and feed.
• llms-full.txt
  The index plus the full text of every article.
• agents.md
  This page, as Markdown.
• index.md
  The homepage article index, as Markdown.
• sitemap.xml
  Every canonical URL, with last-modified dates.
• rss.xml
  RSS 2.0 feed of new articles.
• feed.json
  JSON Feed 1.1 equivalent of the RSS feed.
• robots.txt
  Crawl rules, plus a Content-Signal header: search=yes, ai-input=yes, ai-train=no.

Attribution