FOR ENGINEERS Keep the whole spec straight

Keep the whole spec consistent.

A README is easy. A design doc whose requirements in section one have to hold up against the data model in section three is a different game. Slima holds the structure, handles the Markdown, and reads every section.

Start writing free See how it works
app.slima.ai · Writing Studio
📐 Payments RFC v2 · 8 sections
Overview
Architecture
API reference
Changelog
3 open RFCs linked
+ New section
ARCHITECTURE · ~6 MIN✓ SAVEDMarkdown ⇄ Export

Service architecture

The payments service owns the ledger and exposes a single write path. Reads are served from a replica, so any caller that needs strong consistency must go through the write path explicitly.

Every state transition is idempotent. A duplicate request with the same key returns the original result rather than double-charging the customer.

Timeouts retry with backoff, capped at two attempts, after which the request is parked on the dead-letter queue for manual review.

✓ Saved · v4Section 2 of 8~6 min read
AI Coach
READ THE WHOLE SPEC
Does the retry budget here match the SLA in §1?
Not quite. §1 promises 99.9% availability, but capping retries at two attempts leaves no headroom for a slow dependency. Raise the cap or soften the number.↳ from §1 · Overview
Consistency checkOpen questions
Markdown native
Plain text in · clean export out
🗂️ Doc tree
8 sections · 3 RFCs linked
📤 Export
Markdown, PDF & HTML ready
✦ AI Coach
Reading the whole spec…
Trusted by engineers who write as much as they ship
Backend teamsPlatform engineersTech leadsOSS maintainers
Built for technical writing

From first draft to shipped spec.

Structure a document the way it is actually shaped, with the Markdown handled for you and every reference tracked across every section.

One workspace

Outline, draft, review, ship.

Each stage solves a real place engineers get stuck writing things down, and the AI Coach follows you across all four.

🗺️

Outline that holds

Structure the whole document the way it is shaped, from overview to appendix, before you write a line of prose.

🗂️

Structure that moves

Reorder sections and their headings, links, and references move with them — nothing left pointing at the wrong place.

✍️

Write in clean Markdown

Headings, code blocks, tables, and callouts, with the AI Coach reading every line as you type.

📤

Ship anywhere

A one-click export in whatever shape the review needs — Markdown, PDF, or self-contained HTML.

Doc tree

Structure before prose.

Drag sections around the tree and their headings and references move with them. Color bars show which thread each section carries, so the link in §9 still resolves and nothing quietly drifts out of sync.

  • Tree, outline, and graph views
  • RFC, ADR, or a custom doc template
Doc tree
Drag to reorder · links stay in sync
OVERVIEW · §1
Goals and non-goals
ARCHITECTURE · §2
Service boundaries
API · §4
Endpoints and schemas
Markdown native

One source, every format.

Write in plain Markdown and preview the rendered doc in a click. Headings, code blocks, and tables format themselves. Export the version review asks for, with no second file to keep in sync.

  • Code blocks, tables, and callouts built in
  • Headings stay synced to the outline
Payments RFC
MarkdownPreview
One file, clean export
## Authentication

Every request carries a signed bearer token. Tokens expire after 15 minutes and refresh silently in the background.

### Issuing a token

POST /v2/tokens with client credentials; the response returns an access token and a refresh token.

An AI Coach that read the spec

It knows your spec and every section.

Ask it anything on any doc. The AI Coach holds your sections, requirements, and glossary in mind across the whole workspace, so its notes come from inside your spec — not from a generic style guide.

  • Follows you across every doc in the workspace
  • Flags the section that is still a stub
AI Coach
Reads your spec, every section, every doc
You
Which requirement in §1 still has no implementation note?
Coach
Idempotency. You promise exactly-once in §1, but no section says how keys are stored or expired. §3, the data model, is the natural home for it.
↳ from §1 · requirements
And the rest, quietly

Ready for review.

Everything a reviewer expects, handled before you open the pull request.

📤

Export anywhere

Markdown, PDF, and self-contained HTML in one click. Import existing Markdown too.

🧵

Consistency across docs

Every term and reference tracked, so the API in §4 still matches the contract in §1.

👥

Glossary and references

Every term, where it is defined, and which docs depend on it.

🏛️

Doc templates

RFC, ADR, design doc, or a custom outline, with a nudge when a section is still empty.

📄

Clean, shareable output

Consistent headings, numbered sections, and a title block reviewers expect.

🕓

Version history

Every version restorable — the same version control you already trust in code.

“Before Slima I was writing my novel in Notion and getting tangled up in my own structure. With Slima I can find the right reference notes intuitively, and focus mode + daily word tracking help me actually hit each day’s target without friction.”
RZ
Rozhen
Fantasy & Sci-Fi Novelist

Write the docs. Keep them true.

Start free and open your first doc. The AI Coach is free to try for seven days.

Start writing free Explore the Writing Studio