add pdftomd

2026-05-08 16:42:19 +09:00
parent 551ab50735
commit 88d6b92283
99 changed files with 47332 additions and 0 deletions
@@ -0,0 +1,31 @@
+---
+name: math-markdown-review
+description: Review and design Obsidian-friendly Markdown normalization for math-heavy PDF conversion, including LaTeX delimiters, display math spacing, asset links, tables, and quality report warnings. Use when Codex needs to check Markdown output assumptions, design post-processing rules, or define renderability checks for formulas and assets.
+---
+
+# Math Markdown Review
+
+## Overview
+
+Use this skill when Markdown output quality matters more than raw text extraction. The goal is best-effort automatic conversion with explicit warnings and provenance for failures.
+
+## Workflow
+
+1. Read `PLAN.md` and `PROGRESS.md` first.
+2. Read `PRD.md` and `ARCHITECTURE.md` when output behavior, metadata, or reporting is affected.
+3. Preserve project delimiter policy: inline math uses `$...$`; display math uses `$$...$$`.
+4. Check asset links, table fallback behavior, heading/list interactions, and page boundary markers against Obsidian rendering assumptions.
+5. Define warnings for low-confidence math, non-renderable LaTeX, broken asset links, table degradation, and reading-order uncertainty.
+6. Ensure `.report.md` content is derived from metadata, not separate manual state.
+
+## Checks
+
+- Inline math should not contain unescaped newlines or surrounding spaces that break rendering.
+- Display math should be separated from surrounding paragraphs by blank lines.
+- Asset paths should be stable, relative to the Markdown file, and safe for Obsidian vaults.
+- Tables with formulas should prefer readable Markdown when reliable and warn when downgraded.
+- Every renderability failure should be countable in metadata and visible in `.report.md`.
+
+## Reference
+
+Read `references/obsidian-output-checks.md` for concrete normalization and report-signal guidance.