PDF to Markdown for Claude Code
Turn specs, API docs and reports into clean Markdown context Claude Code reads natively — then wire it into your project with a tuned CLAUDE.md.
Convert a PDFContext builder
Build your CLAUDE.md
Toggle the sections you need. Copy it or download the file — everything runs in your browser.
Sections
# My Project — CLAUDE.md ## Overview My Project is a … . See @README for the full overview. ## Build & Test - Install: `pnpm install` - Dev: `pnpm dev` - Build: `pnpm build` - Test: `pnpm test` - Lint: `pnpm lint` ## Project Layout - `src/` — source code - `docs/` — reference docs (converted from PDFs) - `tests/` — test suites ## Reference Docs Imported with `@path` — these expand inline when Claude Code starts: - Architecture: @docs/architecture.md - API spec: @docs/api-spec.md - Decisions: @docs/decisions.md ## Coding Standards - TypeScript, strict mode - 2-space indentation - Components: PascalCase; utilities: camelCase - Commits: `type: description` (feat, fix, docs, refactor) <!-- Keep this file tight and high-signal. A 40-line file beats a 400-line one. -->
Prompts
Prompt pack
Copy-paste prompts for working with your converted Markdown in Claude Code.
Summarize & extract key concepts
Turn a converted spec into a quick brief.
I've converted my documentation to Markdown. Please: 1. Read @docs/FILENAME.md 2. Summarize the top 3 key concepts in one sentence each 3. List the 5 most important definitions for a new team member 4. Flag any ambiguous or contradictory sections
Extract structured data into a table
Pull endpoints/params out of an API doc.
From @docs/api-reference.md, create a Markdown table with columns: | Endpoint | HTTP Method | Parameters | Response Code | Description | Then list which endpoints require authentication and which don't.
Consistency check (docs vs codebase)
Find drift between your docs and your code.
Compare @docs/requirements.md against the current codebase for: - Missing functionality mentioned in docs - Code that contradicts documented behavior - Outdated examples or API patterns Report findings as a checklist with file:line references.
Onboarding guide generator
Generate a junior-dev onboarding doc.
Based on @docs/architecture.md and @docs/setup.md, write a step-by-step onboarding guide for a junior dev: project structure, build/test commands, deployment pipeline, and a glossary. Format as Markdown with links to the relevant sections.
Decision log from a spec
Distill decisions out of a long document.
Read @docs/design-decisions.md. For each decision, extract title/date/stakeholders, summarize problem/options/chosen solution, note tradeoffs, and flag anything worth revisiting. Output as a structured Markdown decision log.
Community
Community skill library
Discover and upvote Claude Code skills the community finds useful — or share your own.
Top community skills
Browse the libraryLoading…
Claude Code Context Starter Kit
Everything to wire converted docs into Claude Code — plus skills that set up project goals and build loops for you.
- Annotated CLAUDE.md template
- Three skills: define-project-goal, feature-build-loop, spec-first-feature
- Copy-paste prompt library
- Example .claude/rules + /loop playbook