A Skill for vibe coding
See the logic
behind your code
Connect what you asked for, what AI built and what actually runs — in one state graph.
VibeLens
When AI changes the code
Keep the behavior
within reach
A working screen leaves questions. Which rule allowed it? Which state changed? Where did that value come from?
-
01
Agree on the model
Confirm the flow, states and shared rules in conversation.
See the first conversation ↗ -
02
Follow a real run
Record an operation. Follow its calls and values down to the source.
Inspect the recording ↗ -
03
Make the next change
Give AI a precise finding. Review the updated graph and test the next run.
Follow the repair ↗
One graph, different depths
Start with intent
Arrive at the exact value
Business, states and rules connect to entry points, files, functions and stored data. Choose the part you need.
Drag to orbit · Select a layer
Intent
What should people be able to do?
Confirm the actions and paths in conversation.
Actors · Actions · Outcomes
Explore a connected path ↗Your architecture, your choice
A model to build with
A lens to look through
- Drive
- Build execution around the confirmed state model.
- Observe
- Map your existing logic and follow its real behavior.
Focus, record, explore
Keep the path
you care about
Select nodes and relations, save your view, then replay the calls and values along that path.
-
Your own view
Choose layers and relations. Keep your layout across iterations.
-
One recording
Capture an operation and scrub its timeline.
-
Connected details
Follow changes from the graph to highlighted source.
For your next project
Start with a conversation
Install the Skill, then call $vibelens in Codex.
Installation & usage ↗