content

Imported from wyattowalsh/wild-web-wrap-up (content/AGENTS.md). Install upstream with npx skills add wyattowalsh/wild-web-wrap-up --skill content. Copyright stays with the author.

Content Agent Instructions

These instructions apply to content/.

Source Of Truth

• content/issues/<slug>/index.mdx is the canonical editorial source.
• Store issue-specific assets in the same slug directory and reference them from issue bodies with ./asset-name.ext.
• content/buttondown/ is the canonical source for email templates and snippet content.
• Use w4w’s Wild Web Wrap-Up for reader-facing newsletter copy. Keep w4w shorthand for compact labels, logo shorthand, and internal workflow names.
• Do not edit generated buttondown/ files as the primary source of a change; update content/ and run pnpm run content:buttondown.

Validation

• Run pnpm run content:validate after changing issue files, templates, or snippets.
• Run pnpm run content:buttondown after changing content that affects Buttondown output.
• Inspect the generated diff after regeneration, but treat content/ as the source to edit when output is wrong.
• Keep content safe for both the web archive and email export.
• Keep Buttondown output aligned with content/buttondown/DESIGN.md and the free-plan-safe export contract.
• pnpm run content:validate also enforces the Buttondown snippet microsurface contract for outer tables, image alt text, meaningful text size, button tap targets, literal-color contrast, canonical/generated attribute names, the plaintext marker boundary, and catalog drift.
• After changing snippets or templates/base.html, inspect the Buttondown Studio in Storybook or run pnpm run storybook:build when a browser review is not part of the task.
• Prove generator convergence with two consecutive pnpm run content:buttondown runs and no second-run managed-output change. Do not treat that as Next, Storybook, live Buttondown, or publication proof.

Writing

• Prefer clear issue prose over marketing copy.
• Keep examples and placeholders easy to replace.
• Use React-safe className and tabIndex in canonical MDX. The exporter emits class and tabindex only for opening-tag attribute tokens in generated email.
• Do not place <!-- buttondown-editor-mode: plaintext --> in canonical MDX; the exporter inserts exactly one marker at the first generated-email body boundary.
• Do not include secrets, private subscriber data, or unpublished credentials in content files.