ken/crashtestdev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: plan visuals upfront, not as afterthought; note Remotion for animations

Browse Source 
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>
This commit is contained in:
Ken
2026-05-27 01:01:53 +00:00
parent c4e013fbce
commit d4a9f8b16f
1 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.amplifier/AGENTS.md
+16 -10
View File
@@ -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