blog: ASD-STE100 prompting, Karpathy's 4 tricks, with coded motion graphics

[chaitanyagiri]

New guide from the founder's brief: /blog/asd-ste100-prompting/.

What is in it

• Post: "ASD-STE100 Prompting: Karpathy's 4 Tricks for Clearer AI Answers", 1,123 words, 5 FAQ.
• Motion graphics, drawn in code (blog/src/assets/media/asd-ste100-prompting/motion.js and motion.css, no libraries):
  • lead: five shapes morph from messy text to clean text, a diagram, a web page and a video
  • the 80% rewrite: filler words marked and struck, then four short sentences, counter 35 to 29
  • a login flow diagram that draws itself, with a marker running through it
  • an explainer scene: a turning circle draws its sine wave, with captions and a voice track
• Live SIP calculator inside the post (three sliders, year by year bars).
• Each scene ships a still PNG. Readers without scripts, or with reduced motion on, see the still. Scenes play only while on screen.
• Hero is a still from the same system, not a sketch.
• Backlink added from context-engineering-for-ai-agents.

Checks

• Gate: PASS (2 warnings: "leverage" is inside the bad example on purpose; undated numbers are rule counts).
• Fact review: round 1 FAIL on 10 points (two errors, attribution and overstated claims), all fixed. Round 2 PASS, 5/5/5/4/5.
• Sources opened 5 Oct 2026: Karpathy's post, Wikipedia on Simplified Technical English, Search Engine Journal.
• npm run build and check-release-links pass.

Before

New page; nothing existed at this URL.

After

Animation stills:

🤖 Generated with Claude Code

[github-actions]

🚫 This PR is missing its before/after evidence

Every pull request here has to show its work. Screenshots or a short screen recording, before the change and after it.

• Before — no image or video under that heading

How to fix it: edit the description, keep the ### Before and ### After headings from the template, and drag an image or video under each. GitHub uploads it inline. This check re-runs the moment you save.

A bug fix with no visible surface still needs it: show the failing behaviour, then the same steps passing. A terminal recording is fine.

Genuinely nothing to show — a CI tweak, a typo, a dependency bump? A maintainer can apply the no-visual-change label. Please don't ask unless it truly has no observable effect.

📖 CONTRIBUTING.md → Evidence is mandatory