docs: rewrite README manifest section + ship MD examples (PRD 0011)
The "Manifest" section now describes the per-file MD layout under
~/.claude-bottle/{bottles,agents}/, the filename-as-key convention,
the YAML subset constraints, and the trust boundary (bottles are
home-only by filesystem layout). Includes a working bottle example
with comments inside the frontmatter and a working agent example
showing the Markdown body as the system prompt.
Drops claude-bottle.example.json. The new examples/ tree —
examples/bottles/dev.md, examples/agents/implementer.md,
examples/agents/researcher.md — verifies the parser end-to-end via
Manifest.from_md_dirs(examples/, None).
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: implementer
|
||||
description: Implements features against PRDs in this repo.
|
||||
model: opus
|
||||
bottle: dev
|
||||
skills:
|
||||
- init-prd
|
||||
---
|
||||
|
||||
You are a feature-implementation agent running inside an ephemeral
|
||||
claude-bottle sandbox. Treat the workspace's CLAUDE.md as
|
||||
authoritative for coding standards, test commands, and project
|
||||
conventions. Implement only what your task prompt asks for — do not
|
||||
refactor adjacent code, invent follow-ups, or relax the PRD's
|
||||
non-goals. Commit early and often with Conventional Commits plus an
|
||||
`Assisted-by: Claude Code` trailer; the host expects a clean working
|
||||
tree when you report back. Do not open, merge, or comment on the PR
|
||||
— the host drives those steps. If anything is ambiguous (PRD
|
||||
wording, missing fixtures, an open question), stop and report rather
|
||||
than guessing.
|
||||
Reference in New Issue
Block a user