feat: make examples cumulative with carry-forward chain and capstone
Add three new sections to all 14 examples: - "Carry Forward": what output feeds into later examples (01-10) - "The Cumulative Path": alternative prompt building on previous output (02-10) - "Now Try It Yourself": personalized template with transferable pattern (all) - "Building On" callout connecting back to previous examples (02-10) Add Example 14: Build Your Personal Agent - capstone that guides reader through writing their own CLAUDE.md, creating a personal skill, connecting a messaging channel, setting up automation, and testing end-to-end. Update README with cumulative path diagram, two usage modes, and example 14. Update GETTING-STARTED.md with cross-references to relevant examples. 17 files changed, 703+ lines added. The examples now form a coherent learning path from "see what it can do" to "build your own agent." Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
06ae605051
commit
0d0b83f98c
17 changed files with 979 additions and 11 deletions
|
|
@ -24,7 +24,7 @@ ecosystem.
|
|||
## Project structure
|
||||
|
||||
```
|
||||
examples/ 13 numbered examples, each with a prompt.md
|
||||
examples/ 14 numbered examples, each with a prompt.md
|
||||
security/ Permission modes, Auto Mode, hooks, NemoClaw comparison
|
||||
memory/ How cross-session memory works
|
||||
automation/ Cron, launchd, /loop, /schedule
|
||||
|
|
@ -43,7 +43,9 @@ This file (CLAUDE.md) is for instructions. MEMORY.md is for state.
|
|||
## Rules for this project
|
||||
|
||||
- This is a demo repo. Do not add dependencies or build steps.
|
||||
- Keep examples self-contained. Each should work independently.
|
||||
- Every example has a standalone demo prompt AND a cumulative path prompt.
|
||||
Both must work. The standalone prompt requires no prior examples.
|
||||
The cumulative prompt builds on output from previous examples.
|
||||
- All output files go in `pipeline-output/` or `briefings/`.
|
||||
- Do not modify files in `security/` or `hooks/` without reviewing
|
||||
the security implications.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue