Your first app

Create your workspace

When you first log in, you describe your app. CodeSpring opens a fresh map with your app at the center and four cards around it to fill in. Each card teaches your agent something it would otherwise have to guess.

• Technology stack is the languages, frameworks and tools your app runs on.
• Core features is the main things your app does, one card per feature.
• Target audience is who the app is for, so decisions stay grounded in real users.
• Competitors is the similar products your app should match or beat.

Meet your project node

This is your project node, the root of the whole map. It holds your app name, a short description and the GitHub repo your agent clones. Everything you add from here grows out of this one node.

Add your first core feature

Your Core features card starts empty. Click Add Card, then give the feature a clear name and a plain description of what it does. A card is one feature. Here we add a Dashboard.

Your feature on the map

The feature now appears on the map as its own card, showing just the name and the plain description you wrote. Nothing is bolted to the card itself. Every action lives in its right-click menu: rename it, rewrite its description, add a bridge for more detail, or delete it. Opening that menu is the next step.

Add detail with a bridge

Right-click your feature to open its menu, then choose Add a bridge. Give the bridge a name and it attaches straight to the feature. A bridge is where the detail lives, so notes and other cards hang off it while the feature card itself stays clean.

Attach a note

A bridge holds the detail, and a note is the first thing to hang off it. On the Dashboard bridge you just made, click the plus to open its menu, then choose Notes. A Notes card appears joined straight to the bridge, and you write down how the feature should work in plain language. This is the detail your agent reads before it writes any code, so the more specific you are, the closer the result.

See it come together

Here is the map so far. Your project node sits at the center. Off it hangs the Core Features folder, holding each feature as a card. One card, Dashboard, has grown a bridge, and off that bridge fan the details you attach: a note, a Sub-features folder, and a PRD bridge. Every app grows this same way, one node at a time, from the center outward.

Add sub-features

Features can hold sub-features too. Here Analytics sits under Dashboard. The pattern never changes: right-click to add a bridge, hang notes off it, and keep describing what you want in plain language.

Generate PRDs and build

When your map has enough detail, turn it into build-ready specs. Go to Docs and PRDs to generate a PRD from any feature, then Kanban and tasks to break it into tasks your agent works through one by one. To connect your agent, clone the Getting started skill below. Already working in an existing repo? The import journey maps it for you first.