From d4a9f8b16fd28e3d213675f7d8afe53d98834e26 Mon Sep 17 00:00:00 2001 From: Ken Date: Wed, 27 May 2026 01:01:53 +0000 Subject: [PATCH] docs: plan visuals upfront, not as afterthought; note Remotion for animations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Content pipeline now starts with visual planning before drafting: - What diagrams does this piece need? - Static SVG? Animated (Remotion)? Interactive (d3-graphviz)? - Plan alongside the outline, not as a decoration pass at the end Cleaned up duplicate Project Context section in AGENTS.md. 🤖 Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com> --- .amplifier/AGENTS.md | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) diff --git a/.amplifier/AGENTS.md b/.amplifier/AGENTS.md index 13104d1..af4e1ab 100644 --- a/.amplifier/AGENTS.md +++ b/.amplifier/AGENTS.md @@ -69,16 +69,6 @@ Ken's real writing uses 0-2 em-dashes per 1000 words. Claude defaults to When you find yourself typing an em-dash, stop and ask: would a period work here? It almost always does. -## Project Context - -- **Site:** Crash Test Dev (Astro blog at blog.ampbox.io / kenotron.github.io/crashtestdev) -- **Author:** Ken Chau (kenotron on GitHub, @kenneth_chau on Twitter) -- **Content types:** Posts (war stories), Patterns (reference), Lessons (progressive) -- **Design system:** DESIGN.md at project root (Google DESIGN.md spec-compliant) -- **Aesthetic:** "Workbench, not gallery" -- warm, grounded, un-digital -- **Voice profile:** .amplifier/VOICE.md -- **Design specs:** .design/AESTHETIC-GUIDE.md, .design/specs/ - ### Visualization Pass Is Mandatory Before Publishing Every post gets a visualization pass. The question is not "does this post need @@ -126,12 +116,28 @@ for them. The consideration is mandatory. The diagrams are not. - For concept art / visual targets: use image generation, then code SVG approximations toward the target +## Project Context + +- **Site:** Crash Test Dev (Astro blog at blog.ampbox.io / kenotron.github.io/crashtestdev) +- **Author:** Ken Chau (kenotron on GitHub, @kenneth_chau on Twitter) +- **Content types:** Posts (war stories), Patterns (reference), Lessons (progressive) +- **Design system:** DESIGN.md at project root (Google DESIGN.md spec-compliant) +- **Aesthetic:** "Workbench, not gallery" -- warm, grounded, un-digital +- **Voice profile:** .amplifier/VOICE.md +- **Design specs:** .design/AESTHETIC-GUIDE.md, .design/specs/ + ## Content Pipeline ``` Idea / source material | v +Plan visuals FIRST: what diagrams, animations, or visuals +does this piece need? Static SVG? Animated (Remotion)? +Interactive (d3-graphviz)? Plan them alongside the outline, +not as an afterthought. + | + v Draft post (src/content/posts/slug.md) | v