menu of options
## Anti-patterns to avoid
- Verbose explanations of what Claude already knows ("PDF stands for…").
- Multiple options where one default would do — pick a default, mention escape hatch
TypeScript and comprehensive test suite
- **Java Projects**:
- `certificate-service`: Modern Spring Boot application with PDF generation
- `shopping-service`: Legacy Grails/Groovy application for modernization exercises
### Skills and Custom Commands Integration
- **`custom-commands.md
worst offenders
---
## Default File Locations
### Documents and Reports
When asked to create documents (PDF, MD, reports, notes) with no specified location:
- ALWAYS default to the `/docs` directory in the project
same cases), `/trace`, `/codex-review`.
- **Deliverables**: brief + chart into `outputs/`; `/export` to Docs, Slides, Notion, PDF, Word.
- **Pace**: `/pace guided | narrated | autopilot`. Never run an L3+ analysis silently in guided
changing the skill, read:
- `skill/SKILL.md`
- `skill/references/design-principles.md`
- `skill/references/qa-and-delivery.md`
- `docs/README.md`
The final acceptance gate is PPTX -> PDF -> PNG followed by direct LLM review
of the rendered PNGs. Keep the skill name
source file back into the .lit.md
bun run scripts/untangle.ts [--lit-map ] [--weave]
# Weave: generate PDF from a literate program (requires pandoc + xelatex + mermaid-filter)
pandoc project.lit.md -o project.pdf --pdf-engine
toolbar. Exports use the File System Access API or `window.open` + `print()` for PDF.
Mode branching lives in [index.ts](src/browser/index.ts), [EditorManager](src/browser/core/EditorManager.ts), [SettingsProvider](src/browser/core/providers/SettingsProvider.ts), [ExportSettingsProvider](src/browser/core/providers/ExportSettingsProvider.ts), and a few React components
Corpus
The `docs` dict in `mcp_server.py` ships six audience-calibrated documents (2 `.md`, 2 `.pdf`, 1 `.docx`, 1 `.txt`). All are 150-250 words with embedded structure cues
render` shells out to Word (macOS/Windows) or LibreOffice (cross-platform) to produce a PDF, then rasterizes in-process via the bundled `@hyzyla/pdfium` WASM package (no system tools needed
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.