> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibely.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Your first week

> A seven-day path from sign-up to shipping. One small thing per day.

The [Quick start](/docs/introduction/quick-start) gets you to a live preview in five minutes. This page is the longer arc — the one-thing-per-day path that gets you comfortable with everything Vibely does, without trying to learn it all at once.

Treat the days loosely. If day 1 takes you 15 minutes and you want to jump to day 3, do it. The order matters more than the calendar.

## Day 1 — Build your first thing

Goal: one working preview URL.

Open [vibely.sh/code](https://vibely.sh/code), pick **Web app**, and type the most boring prompt you can think of:

> "A todo app with add, complete, and delete. Use local storage, no backend."

Three reasons it's deliberately boring:

1. Boring prompts produce boring code, which is the easiest kind to read.
2. You get to see the streaming agent loop end-to-end before any ambiguity creeps in.
3. You'll have something to compare against on day 4 when you build something hard.

When the preview appears, click around. Note how fast the iteration loop is. That's the floor of every future build.

[Quick start →](/docs/introduction/quick-start)

## Day 2 — Iterate

Goal: feel how Vibely keeps project state across turns.

Open yesterday's project. Without re-explaining the app, ask for three changes back-to-back:

1. "Add a 'clear completed' button."
2. "Persist the list per user — use a fake `user_id` in localStorage."
3. "Add dark mode that follows the system."

Watch what changes between turns. The agent doesn't re-scaffold the project; it touches the files that need touching. This is the loop you'll spend most of your Vibely time in.

[Iterating tips →](/docs/tips/iterating)

## Day 3 — Pin what you learned in project memory

Goal: stop typing the same correction twice.

Whatever you've already corrected ("don't add summaries", "use Bun, not npm", "skip the explanation, just the diff", "primary colour is `#0ea5e9`") — codify it.

Ask the agent: *"Save to memory: …"* with the facts you want it to remember in this project. It writes them to `.mana/memory.md` and reads them back on every turn — so the second time should be unnecessary.

[Tips → Memory →](/docs/tips/memory)

## Day 4 — Build something real

Goal: a project you'd actually use.

Pick something from your own life — a tracker for a habit, a tool for a side hustle, a dashboard for something you check too often. Constraints:

* Multi-page (router, navigation, at least three routes).
* One connector (Supabase for auth + data is the obvious choice).
* One small piece of real polish (animation, a chart, a nice empty state).

This is the build that tells you whether Vibely fits your work. If you finish it in an afternoon and want to keep going, good signal.

[Web App Mode overview →](/docs/web-app/overview)

## Day 5 — Plug something in

Goal: experience the connector layer.

Pick one third-party service from the [Catalog](/docs/connectors/catalog) — Slack, Linear, Stripe, Notion — and wire it into yesterday's project. A few prompts that produce good demos:

* "When a user signs up, post their email to my Slack `#signups` channel."
* "Add Stripe test-mode checkout for a \$9/month plan, gated behind login."
* "Sync new entries to a Notion database I'll connect."

Vibely handles the OAuth dance and the code; you just click **Authorize**.

[Connectors overview →](/docs/connectors/overview)

## Day 6 — Ship

Goal: a public URL someone else can open.

Two paths:

* **Preview link** — already public, lives at `*.vibelyagent.com`. Share it as-is.
* **Custom domain** — bring your own domain, add a CNAME, click Verify. TLS provisions in under two minutes.

Either way, send the link to one person — a friend, a colleague, the original "I wish there was a tool that…" who inspired the project. Their reaction is the actual deliverable.

[Publishing a web app →](/docs/web-app/publish)

## Day 7 — Make it yours for the long haul

Goal: set up the small habits that compound across every future project.

Three things to do, in any order:

* **Sync the project to GitHub.** Project menu → Export → GitHub. Now you have a real safety net — if a future turn destabilizes the project, you can branch off the green commit and replay. See [Project settings → GitHub](/docs/workspace/project-settings#github).
* **Revisit your project memory.** Open the project you've spent the most time in this week. Ask: *"Show me memory."* Read it. Tighten or expand it based on a week of patterns you've spotted. See [Tips → Memory](/docs/tips/memory).
* **Author a skill.** If you found a build pattern you'll reuse, drop it into Settings → Skills. The next project starts ahead. See [Skills](/docs/customize/skills).

These three habits are the difference between Vibely-the-tool-you-tried and Vibely-the-tool-that-quietly-shaped-your-week-two-output.

## After day 7

You now have:

* A real project shipped behind a URL someone has seen.
* Project memory pinned with the decisions you want the agent to remember.
* One connector wired, GitHub synced, and the muscle memory of the prompt loop.

Everything from here is repetition — the second project goes faster than the first, the tenth faster than the second. The point of week one isn't mastery; it's removing every excuse not to start project number two.