Skip to content

feat(site): blog post — prompt injection as a compile error#52

Open
marcelofarias wants to merge 1 commit into
mainfrom
botkowski/blog-prompt-injection
Open

feat(site): blog post — prompt injection as a compile error#52
marcelofarias wants to merge 1 commit into
mainfrom
botkowski/blog-prompt-injection

Conversation

@marcelofarias
Copy link
Copy Markdown
Owner

Summary

  • Adds botscript.org/posts/prompt-injection — a standalone HTML blog post targeting HN and dev audiences
  • Argues prompt injection is an effect propagation problem, not a filtering problem, and CAP001 makes the attack surface parse-time impossible
  • Covers: lint vs. structural enforcement, the 5 real PR receipts, and the MCP server as the first reviewer every LLM has to satisfy
  • Self-contained HTML with inlined CSS matching the main site design tokens — no Vite build dependency, served directly by GitHub Pages

Intended use

Post to Hacker News as "Show HN: botscript – prompt injection caught at compile time, not runtime" linking to https://botscript.org/posts/prompt-injection.

Test plan

  • Build passes: pnpm --filter playground build
  • File appears in dist/posts/prompt-injection.html
  • Design matches main site (dark bg, teal accents, monospace)
  • All links resolve (playground, GitHub, npm, PR receipts)
  • OG/meta tags correct for social sharing

🤖 Generated with Claude Code

Adds botscript.org/posts/prompt-injection — a standalone HTML post
targeting HN / dev audiences. Argues that prompt injection is an
effect propagation problem (not a filtering problem) and that CAP001
makes the attack surface impossible to express in .bs.

Also covers: lint vs. structural enforcement, the 5 real PR receipts,
and the MCP server as the first LLM reviewer. Self-contained HTML with
inlined design tokens matching the main site aesthetic.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant