Voice
Write like a calm, capable person helping someone finish a task.- Prefer short sentences.
- Lead with what the person is trying to do.
- Explain technical detail only when it helps a decision or builds trust.
- Use contractions when they sound natural.
- Do not sound like marketing copy inside support docs.
- Avoid saying something is “simple,” “easy,” or “obvious.” Show the steps instead.
Product vocabulary
Capitalization
Capitalize branded UI names such as Inbox, People, Recovery Kit, Quick Tuck, and Tuck it when referring to the visible product term. Use lowercase for generic concepts such as thought, brain, tag, todo, reminder, and vault unless the word starts a sentence.Distinguish sign-in from unlock
This is one of the most important language rules in Tuck.- You sign in to your Tuck account with a passkey or email link.
- You unlock your vault with a vault passphrase, Recovery Kit, or an approved device-unlock method such as Face ID.
Describe privacy precisely
Do not say “Tuck can never see anything” because some features intentionally require plaintext metadata or a plaintext boundary crossing. Prefer precise statements such as:- “Thought bodies are encrypted before they sync.”
- “A share link is a plaintext snapshot you chose to publish.”
- “Reminder timing and destination stay readable so Tuck can deliver the reminder while your devices are offline.”
Write task-oriented titles
Prefer Capture by email over Email ingest architecture for user docs. Use implementation-oriented titles only in Reference or developer documentation.UI instructions
Use the visible label in bold: Settings, Share, Lock. Use arrows for a short menu path: Settings → Ingest. Do not invent labels that are not in the product.Examples
Good: “Type# to add a tag while you capture.”
Less useful: “Tags may be applied through the metadata autocomplete subsystem.”
Good: “If you forgot your vault passphrase, use your Recovery Kit.”
Wrong: “Reset your Tuck password.”