Use Case · Team Enablement
Onboarding docs that stay true to the codebase.
Walk a new hire through a subsystem out loud once. Dicty captures the tour as a living onboarding doc linked to the exact files you mention.
Onboarding lives in a senior engineer’s head. It gets repeated verbally every hire and written down never — or written once and rotted immediately.
Give the tour by voice. Dicty structures it into a navigable onboarding guide and keeps it reconciled as the code evolves.
The flow
From spoken thought to filed doc.
Pick the subsystem
Attach the service, package, or directory you’re explaining.
Give the tour
Explain the entry points, gotchas, and mental model as you would in person.
Structure the guide
Dicty builds sections with links to the files and functions referenced.
Keep it alive
Future changes to those files flag the guide for a quick reconcile.
Ramp faster
New engineers get the mental model, not just the file tree.
Say it once
The verbal tour becomes a reusable, searchable asset.
Decay-resistant
Linked code changes surface the doc for updates before it rots.
# Billing service — start here
## Entry point
`src/billing/index.ts` → routes → handlers
## Gotchas
- Idempotency keys are required on every charge
- Read models are eventually consistent (~2s)Stop writing docs. Start speaking them.
More use cases