The product design thinking tool
Define the ontology, architecture, and wireframes behind your product.
Create a blueprint AI can build from.
Denote captures your product's objects, rules, flows, sitemap, navigation, screens, and wireframes. It then writes it all to Markdown and JSON, so your AI tool can dive right into the code.
From a first conversation to a finished spec.
Five steps that build on each other.
-
01
Vision
Talk it through: Think out loud with Denote. Goals, constraints, audience, and open questions collect in the sidebar as you go. Nothing is structured yet. Denote will start turning concepts and ideas into a clear brief.
Read the docs -
02
Ontology
Name the objects: Turn the idea into structure: the entities in your product, the people who use it, the tasks they perform, and the rules that decide how each is treated. This is where the product becomes a system.
Read the docs -
03
Architecture
Lay out the sitemap: Extract from the ontology a complete screen inventory with hierarchy and navigation. Every screen carries a template and variant, so the design's structure is settled before anything gets built.
Read the docs -
04
Screens
Fill each screen: Compose every screen from shells, zones, and content-type chips. You decide what content lives where, and how overlays like panels and dialogs behave. End up with basic wireframes that are ready to be visualized.
Read the docs -
05
Spec
Hand it off: One file,
Read the docsdesign/SPEC.md, generated from everything above. This is the brief Claude Code builds from, governed by every decision you made.
An opinionated design mind, built in.
Denote ships with 34 knowledge files on how good products get structured: objects and their relationships, interaction patterns, visual hierarchy, design systems. The methodology underneath is Object Oriented UX.
That knowledge does double duty. It shapes what Denote recommends while you design, then travels into your project and governs how Claude Code builds. The thinking that produced your design is the thinking that constrains your code.
And it's yours to change. Every file is plain markdown. Edit a principle, add a pattern, adjust the rules, and both sides follow your lead.
Markdown and JSON, in a folder.
Everything Denote writes is plain files you own. Hand them to a teammate or to Claude Code and they build straight from them. No export, no proprietary format, no lock-in.