distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
without explicit user approval.
Changes to this module require careful review of the safety invariants documented in the code comments.
#### Core concepts
- **`HeapReader<'a, T>`** — A scoped borrow
code in this repo is named, typed, structured, formatted, tested, and reviewed. Pure Python coding standard; framework-agnostic.
- **`documents/ai/guides/serena.md`** — Always-on. When and how to use Serena MCP for symbol
halves:
- **Interactive skills** (`.claude/skills/`) — read and write files in the
repo (no target-code execution, except `/dnr-hunt` / `/dnr-respond`, which
run the bundled demo app locally — see `docs/security.md`), run in this
with code in this repository.
## Project Overview
SEO Machine is an open-source Claude Code workspace for creating SEO-optimized blog content. It combines custom commands, specialized agents, and Python
guides/
└── v12_examples/ # New v12 feature examples
```
Look in `examples/` first before writing new code — there is almost certainly an existing example close to what you need.
---
## Core Primitive: Agent
third-party GitHub repository must have at least 1,000 stars at review time; official provider docs, standards, model cards, and irreplaceable canonical sources are exempt. Curation is the primary
skill creation
- Converts raw PM content into skills via 8-step workflow
- Supports Claude Code, Manual mode (`--agent manual`), and custom adapters
- Includes analysis, planning, generation, validation, and documentation steps
errors from outdated dependencies; upgrade the dependency instead
- Always ask before removing functionality or code that appears to be intentional
- Do not add fallback behavior by default. If required context
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.