kortix-voice
Installation
SKILL.md
Kortix Voice
How Kortix reads. The design system governs how it looks; this governs the words. The canonical positioning is suna/COMMS.md — when in doubt, that doc wins; this skill is how you apply it in the product.
The one rule
Plain language by default. Technical detail is opt-in.
A non-technical founder must understand every default surface without knowing what a repo, branch, sandbox, or commit is. The technical truth still exists — it lives one layer down: behind an "Advanced"/"For developers" disclosure, in an "Under the hood" callout, or in the Reference docs. Never lead with jargon; never hide the outcome behind it.
Voice
- Outcome first. Say what the user gets, then (optionally) how. "Your agent drafts the report" > "Spawns a session that runs the prompt."
- You, active, short. Address the user as "you". Active voice. Short sentences. Sentence case for everything (headings, buttons, labels) — not Title Case.
- Calm and confident. Founder-grade, plain. No hype, no fear, no filler.
- Specific, not salesy. Concrete nouns and verbs over adjectives.