A spec earns adoption by being effortless to navigate. This template sets Montserrat headings over an Open Sans body in a fresh teal on A4 — airy section spacing, requirement tables with room to breathe, and a heading rhythm that lets an engineer jump straight to the acceptance criteria.
Spec in Markdown next to the code — requirements as tables, flows as numbered lists, edge cases as callouts. Render on merge and the team always has a current, printable spec that looks exactly like every other spec in the org. Version the source in git; treat the PDF as the artifact you circulate.
# Design Spec — Notification Center **Author** S. Adeyemi · **Reviewers** Platform, Mobile · **v1.2** ## Overview A unified in-app notification center replacing the three ad-hoc toast systems currently shipped across web and mobile. ## Goals - One delivery pipeline, one read-state model - p95 delivery latency under 2 seconds - Full parity between web and mobile clients ## Non-goals Email and push digests — handled by the existing comms service. ## Requirements | ID | Requirement | Priority | | --- | -------------------------------------- | -------- | | N-1 | Real-time delivery via existing socket | P0 | | N-2 | Read/unread sync across devices | P0 | | N-3 | Per-category mute controls | P1 | | N-4 | 90-day retention with archive | P2 | ## User flow 1. Event published to the notification topic 2. Fan-out service resolves audience and preferences 3. Client receives payload; badge count updates optimistically > **Edge case:** a mute applied mid-flight must win — check > preferences at delivery, not at publish. ## Acceptance criteria Delivery p95 < 2s at 10× current event volume; zero cross-user leakage in the fan-out audit; mute honored within one event.
Paste your Markdown in the editor, pick Design Spec, and download the PDF — no code involved.
curl https://inkrun.dev/api/v1/render \
-H "Authorization: Bearer sk_..." \
-H "Accept: application/pdf" \
-d '{"template": "design-spec", "markdown": "# ..."}' \
--output design-spec.pdfAdd the Inkrun MCP connector once, then ask your agent:
“Write a design spec from these requirements and render it with the design-spec template.”
Yes — a render call in your pipeline turns the merged Markdown into the circulated PDF, so the spec artifact always matches the repo.
Cells wrap cleanly within the template's column rhythm, and rows never split across a page break.
Duplicate the template per squad with its own hex if you like — or keep one template so every spec in the org is visually interchangeable.
Crisp Inter with a confident indigo — lots of breathing room.
Monospace headings for API references and developer docs.
Roboto Mono headings and grid tables for endpoint docs.