Extract semantic structure and transferable style grammar from academic figures, PDFs, and paper or figure URLs for analysis, redraws, or reference-conditioned generation. Do not use it for paper-text-only figure planning.
Plan evidence-backed figures for a paper draft, markdown notes, outline, manuscript, PDF, or paper webpage. Supports Draft-to-Figure fast-track for Markdown notes as well as comprehensive multi-figure planning for full manuscripts.
Plan, generate, inspect, and refine academic figures from repositories, papers, draft notes, paper URLs, PDFs, or reference images. Supports fast-track draft-to-figure generation and user passthrough mode.
Analyze ML, AI4Science, Systems, and research repositories into an evidence-backed semantic architecture graph for paper figure planning. Code serves as supporting evidence; paper narrative and user intent remain the primary source of truth.
A guide for exploring several implementation or visual-design options before choosing one. It also covers writing an engineering plan, such as an RFC, which records how a chosen solution will be built.
A set of HTML-based formats for reviewing code changes, writing pull-request descriptions, and showing how unfamiliar modules and call paths fit together.
A guide for documenting a design system, meaning the shared visual rules and reusable interface parts of a product. It also explains how to display every version of a component, such as a button or card, together for review.
A guide for testing motion and short interaction flows in a web interface. It covers adjustable animation timing and easing, which controls how movement speeds up or slows down, plus clickable flows across four to six screens.
A guide for creating illustrations and diagrams directly in a web page with inline SVG, a built-in format for scalable vector graphics. It covers document illustrations, flowcharts, state machines, and deployment pipelines.
A guide for explaining how a feature works in a code repository or how an abstract technical idea works. It can structure the explanation with a summary, expandable steps, code views, questions and answers, or an interactive visual.
A set of HTML formats for recurring engineering documents, including weekly status reports and incident postmortems. A postmortem records what happened, why, what it affected, and what will change.
A routing guide for deciding when a single HTML page is more useful than plain text, such as for comparisons, diagrams, reports, or interactive editors.