docs: sort Prerequisites lists numerically ascending (#100)
CI / check (pull_request) Successful in 6s
CI / check (pull_request) Successful in 6s
Reorder the `## Prerequisites` bullets in 9 modules so prior modules are listed lowest number first instead of by pedagogical importance or at random. A trailing "Helpful but not required" group stays last and is sorted within itself; multi-module bullets sort by their lowest number. Intro/closing paragraphs are left in place. Prose is unchanged; only bullet order moves. Modules touched: 7, 9, 14, 15, 22, 24, 25, 26, 27. The other 18 modules were already ascending (or have one/zero prereqs) and are untouched. Module 19's "Helpful but not required: Module 16" correctly trails its ascending 8/14/18 main list, so it stays as is. Closes #100 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CamgR4HaVpfaqUViuHUcWw
This commit is contained in:
@@ -8,20 +8,20 @@
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- **Module 2, Version Control as a Safety Net.** `git restore` and a clean commit are part of the
|
||||
blast-radius story when something an agent did needs undoing.
|
||||
- **Module 15, Security Scanning for AI-Generated Code.** Module 15 scans the code the AI *writes*.
|
||||
This module secures the AI *as an actor*. Same instinct (automated gates against AI-shaped
|
||||
failure), different target. The hallucinated-package supply-chain risk from Module 15 has a direct
|
||||
cousin here.
|
||||
- **Module 20, MCP Servers.** You've connected the AI to real tools and data over MCP. That
|
||||
connection is exactly the attack surface this module defends.
|
||||
- **Module 21, Skills.** You've installed and authored skills (and seen that a skill is just
|
||||
instructions plus, often, scripts the AI runs). A third-party skill is someone else's code and
|
||||
someone else's instructions.
|
||||
- **Module 15, Security Scanning for AI-Generated Code.** Module 15 scans the code the AI *writes*.
|
||||
This module secures the AI *as an actor*. Same instinct (automated gates against AI-shaped
|
||||
failure), different target. The hallucinated-package supply-chain risk from Module 15 has a direct
|
||||
cousin here.
|
||||
- **Module 2, Version Control as a Safety Net.** `git restore` and a clean commit are part of the
|
||||
blast-radius story when something an agent did needs undoing.
|
||||
- Helpful but not required: **Module 16** (containers, for sandboxing untrusted servers),
|
||||
**Module 17** (secrets, for scoping the tokens you hand a server), and **Module 5** (committed
|
||||
config; your MCP/skill setup is itself a reviewable, versioned artifact).
|
||||
- Helpful but not required: **Module 5** (committed config; your MCP/skill setup is itself a
|
||||
reviewable, versioned artifact), **Module 16** (containers, for sandboxing untrusted servers), and
|
||||
**Module 17** (secrets, for scoping the tokens you hand a server).
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user