max/markdowned-datasheets
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Datasheets turned into markdown, useful for agents to read.
4 commits 1 branch 0 tags 49 MiB
Find a file
Exact
0m.ax a1c36ccc90 add USB_PD_R3.2
2026-08-23 15:14:35 +02:00
REN_RAA489118 add REN_RAA489118 2026-08-23 15:14:00 +02:00
REN_RAA489400 add REN_RAA489400 2026-08-23 15:14:22 +02:00
tools init 2026-08-23 15:13:42 +02:00
USB_PD_R3.2 add USB_PD_R3.2 2026-08-23 15:14:35 +02:00
.gitignore init 2026-08-23 15:13:42 +02:00
flake.lock init 2026-08-23 15:13:42 +02:00
flake.nix init 2026-08-23 15:13:42 +02:00
PROCESS.md init 2026-08-23 15:13:42 +02:00
README.md init 2026-08-23 15:13:42 +02:00
REN_RAA489118_DST_20251028.pdf add REN_RAA489118 2026-08-23 15:14:00 +02:00
REN_RAA489400_DST_20240827.pdf add REN_RAA489400 2026-08-23 15:14:22 +02:00
USB_PD_R3.2_V1.2_2026_05_20.pdf add USB_PD_R3.2 2026-08-23 15:14:35 +02:00

README.md

Markdowned Datasheets

Vendor datasheets and technical specifications, converted from PDF into per-chapter Markdown with extracted figures and a generated table of contents.

Each PDF is transcribed verbatim, full body text, complete tables, and figures cropped out as PNGs and linked back in with their printed captions.

What's here

Each converted document starts with TOC.md, it links every chapter, every figure, and lists the source document's own known defects so you don't mistake a vendor typo for a transcription error.

Converting another datasheet

PROCESS.md is the runbook a coding agent follows to do the conversion — prompt templates, known failure modes, and a checklist.

To convert a new one, drop the PDF in the repo root and ask your agent to follow PROCESS.md for it. Point it at whichever existing conversion is closest in scale for reference if the source document is unusual (a single short datasheet vs. a 400+ page multi-vendor specification).