Schema and harness document for the CMDS LLM Wiki vault. Defines the 3-layer architecture (Raw Sources / Wiki / Schema), ingest-query-lint operations, file conventions, and frontmatter standards. This is the single source of truth for LLM behavior in this vault.
python -m examples.spam_detection` - Run example
- `bachata-example` - Run spam detection example
- `bachata-pdf-example` - Run PDF extraction example
## Documentation
- Generate docs on each version
```bash
uv run pdoc
that script generates a smaller scaffold cut and would overwrite the shipped file). No PDF is committed; export fresh from the `.pptx` if a cohort needs one.
- `images/social-preview.png` - the GitHub
directories use **noun/doer form** in kebab-case: `agent-skill-reviewer` not `agent-skill-review`, `pdf-translator` not `translate-pdf`.
- This aligns with skills being "personified" agent roles.
### Key design principle
Notes
- Primary source: `stockn.xueqiu.com` (no anti-crawl); fallback: `notice.10jqka.com.cn` (同花顺)
- The Python script validates PDF magic bytes and retries with backoff on failure
- Supported markets: A-share (SH/SZ), Hong Kong
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.