Form.io REST endpoint and navigates into the relevant reference by scope (platform, project, runtime, pdf).
The library's default "build me an app" entry point is [`plugin/skills/formio-application/`](plugin/skills/formio-application/) — a framework
arxiv.org/pdf`) hit other hosts and aren't queued — but a 429 from the PDF fetch records the shared cooldown, so a throttle picked up there still slows subsequent
that copy plugin assets into `~/.claude/` or a target project's `.claude/`
- `mcp-servers/{pdf-ocr-processor,rbi-scraper,sebi-scraper}/index.js` — Node MCP servers (each has its own `package.json
scripts/google_report.py`** as the canonical report generator
- **Dependencies**: `matplotlib>=3.8.0` (charts) + `weasyprint>=61.0` (HTML-to-PDF), both in `requirements.txt`
- **Format**: A4 PDF via WeasyPrint + matplotlib charts at 200 DPI
- **Style**: Clean
standalone animated HTML slide decks (1920×1080 ` ` canvas) from a design system, exportable to PDF (browser print) and editable PPTX. Forked from `marcogalluccio/claude-slides` (see `NOTICE.md`).
The "product" is mostly prose
data is never committed:** all files generated for the person — dossier, CVs, tracker, `.docx`/`.pdf` output — live only under `Personal/` (git-ignored) in a dated per-person subfolder `Personal/ - /`. These
declarative but some actions are imperative one-shots (force reload, find next/prev, export PDF, focus search). These are modeled as incrementing `Int` tokens on `AppState` (`reloadToken`, `findNextToken`, `findPrevToken`, `exportToken
server automatically) |
| Exported case state | `./exports/case_state.json` | Full `CaseState` snapshot on session end |
| PDF report (optional) | `./reports/report.pdf` | Generated by `python3 generate_pdf_report.py` |
All timestamps in output files must
rules.
## Output Language — mirror the user (mandatory) 🌐
Write every response and **generated report (incl. PDF)** in the **language the user
writes to you in** — user writes Turkish → reply + reports
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.