Skip to content

Commit 6e24861

Browse files
dormsternclaude
andcommitted
docs: README overhaul design — proof-first, GIF demo, 3KB target
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 290b532 commit 6e24861

1 file changed

Lines changed: 85 additions & 0 deletions

File tree

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# Design: declawed README Overhaul
2+
3+
## Problem
4+
5+
A 15-year veteran cyber CTO couldn't figure out how to use declawed from the README. His feedback: "It's not clear how it works" and "show me a demo." Current README is 6 KB of syntax-first, proof-last content with zero visual demos.
6+
7+
Comparison with dormstern/segspec (which works): segspec leads with animated GIFs of real CLI output on real codebases (Sentry, PostHog). declawed leads with abstract before/after pseudocode and 4 policy examples before any proof.
8+
9+
## Decision
10+
11+
Approach A: Proof-first, API-last. Cut README from 6 KB to ~3 KB. Lead with a terminal GIF. Move reference docs to docs/API.md.
12+
13+
## New README Structure (~3 KB, ~120 lines)
14+
15+
```
16+
1. HOOK
17+
"Your AI agent has your credentials. This gives it rules."
18+
"Policy, audit, kill switch — in 5 lines of YAML."
19+
20+
2. BADGES (npm, license, tests, CI)
21+
22+
3. DEMO GIF (3-7s terminal recording)
23+
Real AnchorBrowser session (unlimited credits available).
24+
Shows: create shield → allowed task → blocked task → status → audit
25+
File: docs/demos/declawed-demo.gif
26+
27+
4. THE PROBLEM (2 sentences)
28+
42K credentials leaked from AI agent workflows.
29+
declawed = policy file + audit log + kill switch. Not a Mac Mini.
30+
31+
5. QUICK START (3 steps, zero prose)
32+
1. npm install declawed
33+
2. shield.yaml (one compact policy)
34+
3. TypeScript (import, create, task — 3 lines)
35+
"That's it."
36+
37+
6. HOW IT WORKS (ASCII flow — keep existing)
38+
39+
7. CLI (compact — status, audit, kill in one block)
40+
41+
8. Link to full API docs: docs/API.md
42+
43+
9. EMPOWERED BY ANCHORBROWSER (keep current)
44+
45+
10. WHY THIS EXISTS (3 lines) + Built by Behalf
46+
47+
11. LICENSE
48+
```
49+
50+
## What Moves to docs/API.md
51+
52+
- Full API reference (createShield, shield.task, shield.kill, shield.audit, shield.status)
53+
- 4 policy examples (restrictive, permissive, time-boxed, inline)
54+
- Pattern matching rules
55+
- Security details
56+
- Testing philosophy
57+
- Audit log format + JSONL explanation
58+
- Kill switch details (code + CLI + status)
59+
60+
README links to it: `[Full API reference & policy examples →](./docs/API.md)`
61+
62+
## Demo GIF Approach
63+
64+
- Script: `scripts/record-demo.ts` — runs real AnchorBrowser session with declawed governance
65+
- Shows colorized terminal output: green ALLOWED, red BLOCKED
66+
- Ends with `npx declawed status` showing counts
67+
- Record with `vhs` (Charm terminal recorder) or manual asciinema → gif
68+
- 3-7 seconds, committed to `docs/demos/declawed-demo.gif`
69+
- Real session (AnchorBrowser credits unlimited, CEO wants to promote)
70+
71+
## Files
72+
73+
| File | Action |
74+
|------|--------|
75+
| README.md | Rewrite (6 KB → 3 KB) |
76+
| docs/API.md | New (extracted reference content) |
77+
| docs/demos/declawed-demo.gif | New (terminal recording) |
78+
| scripts/record-demo.ts | New (demo script with real AnchorBrowser) |
79+
80+
## Success Criteria
81+
82+
- A cyber CTO reads the README and knows exactly what declawed does in 10 seconds
83+
- The GIF alone tells the whole story
84+
- Quick Start is copy-pasteable without reading anything else
85+
- AnchorBrowser CEO screenshots the README for their BD deck

0 commit comments

Comments
 (0)