Separate what is spoken from what is read
The walkthrough is explained in conversational sections; file references and runnable checks live in companion text. Voice stays listenable and nothing precise is lost.
AtlasCase 02 / 07Studio product / voice-first AI skill
VeritasAxis studio
Understanding the code you shipped
Know Your Code is a voice-first skill for Codex, Cursor, and Claude Code. Ask “What happens when I press Save?” and the assistant follows the actual code, explains it in conversational sections, and keeps file references and runnable checks alongside. The design problem was pacing: an explanation people can interrupt, steer, and come back to.
8Companion skills
3Hosts: Codex, Cursor, Claude Code
Voice + textSame instructions, either way
The problem
More people are shipping software they did not fully write. When it breaks or needs to change, they need the actual path through their own code — not a generic lecture, and not a wall of file references.
I designed the skill’s conversational structure and its seven companions, then the brand, the installation site with a voice orb, and a six-part launch series — all built so one set of instructions works across Codex, Cursor, and Claude Code.
Follow the real code, at the listener’s pace.
How it fits together
From a question to code you can own.
Explore the system
Start from something the app does: “What happens when I press Save?”
See it in the workThe voice interfaceFollow the actual code path, from the button to storage.
See it in the workFollow one featureSay “less jargon”, take a side question, return without restarting.
See it in the workSet your own paceMake changes you can maintain, with checks you can run.
See it in the workMake the code yours
Key decisions
The choices that shaped the work.
Make interruption part of the design
Steering phrases and side questions are expected, not errors. The walkthrough keeps its place and resumes where the listener left it.
One set of instructions, three hosts
The same skills run in Codex, Cursor, and Claude Code with no separate subscription, key, or service — the product is the thinking, not another account.
A brand that sounds like curiosity
Electric blue, an acid-yellow “aha”, and outlined type carry the line “Your code. Your aha.” The launch series follows one feature, finds a cause, and sets the pace.
The work
01 / 08Identity. The cover sets the promise and the voice: plain words, one bright moment of understanding.
The work
02 / 08Installation site. One page, one orb, and copyable install paths for each host.
The work
03 / 08Launch 01 / Introducing. The idea in one frame: talk through how your app works.
The work
04 / 08Launch 02 / Follow one feature. A single action traced end to end, with the prompt to try it.
The work
05 / 08Launch 03 / Find the cause. The same walkthrough turned toward why something breaks.
The work
06 / 08Launch 04 / Make it yours. Changes the person can understand and maintain afterwards.
The work
07 / 08Launch 05 / Set your pace. Steering — less jargon, go deeper, come back — as a product feature.
The work
08 / 08Mark. A compact icon that survives at plugin and marketplace sizes.
What this case shows
A released skill, not a usage claim
The launch material states that its examples are illustrative, not testimonials or measured outcomes. This case shows the design of the skill, brand, and launch — not adoption metrics.
What the work delivered
- 01
Designed a voice-first explanation pattern that keeps precise references without making speech unreadable.
- 02
Shipped eight skills from one set of instructions across Codex, Cursor, and Claude Code.
- 03
Created the identity, installation site, and six-part launch series around a single, plain promise.
Source material
Know Your Code on GitHubNext case study
03AngstromDeFi market infrastructureHow do you explain trading state and execution quality before someone commits?