Continuum Template: A Habit Tracker Built to Be Rewritten

Continuum Template: A Habit Tracker Built to Be Rewritten

Continuum is one of the 25 ready-made Zugo templates: a habit tracker with a landing page, a sign in page, and a dashboard where each habit gets a row of seven dots, a running streak and a daily completion ring. Cloning it costs no credits, and you reshape it by writing ordinary sentences in chat.

What follows is the actual contents of the file, the edits it takes well, the two things you have to add yourself, and the point where a different starting template would serve you better.

What does the Continuum template contain?

Continuum belongs to the app group, so it has a working data layer rather than a picture of one. Marking a dot changes the streak, the ring and the weekly average immediately, and the change is still there after you reload the page.

Five sample habits ship with it (meditate, read for twenty minutes, workout, no sugar, journal), each with its own glyph and its own carried streak. The header shows the strongest current streak rather than a sum, which is the correct choice: a sum flatters, the strongest streak is the number people actually care about.

The tone is worth noticing before you edit it. There is no leaderboard, no red streak warning, no guilt copy. That restraint is the product idea, and if you paste aggressive gamification over it the screens stop agreeing with each other.

Who is Continuum a good starting point for?

The direct fit is any personal streak habit: exercise, language practice, medication, reading, sobriety counters. Nothing about the layout assumes a particular subject, only that a day is either done or not done.

The second fit is a small group tracker. A team doing daily check ins, a study group, a coach handing the same routine to fifteen clients. The screens survive it, but the data model needs an owner per row, which is a connect Supabase job rather than a chat edit.

The third fit is anything shaped like a checklist over time: equipment inspections, a plant watering log, apartment chores. The dot grid is a generic yes or no over days, and only the labels tell you what it is tracking.

Where it stops fitting is quantity. If what matters is how much rather than whether, the ring and the dots start lying, because half a workout looks like no workout. That case wants a numeric log, and the Coinpath template is the closer relative even though it was written for money.

How is starting here different from writing a prompt?

A blank prompt produces a project shaped by your description, and every structural decision inside it is a guess you have to review. The template hands you decisions already made, visible in full, before a single credit leaves your balance.

That matters most for the small stuff nobody writes into a prompt. Seven dots and not thirty. Best streak in the header and not total completions. An add row at the bottom rather than a modal. You would not have specified any of it, and all of it changes how the app feels in use.

The cost side is simple. A build from scratch costs 6 credits and a second attempt costs 6 more. The clone costs nothing at all, so an unsuitable template is a wasted click rather than a wasted build. Preview two or three before committing.

The honest counterweight: if you find yourself removing more than you are adding, the template is fighting you. Three edits spent deleting things is the signal to describe your own version from scratch instead.

What can you change with chat edits?

Habit trackers are unusually sensitive to small changes, because the ritual is the product. Go one edit at a time and use the app for a day between the big ones.

1. Change the subject: "rename it to Practice, replace the habits with scales, sight reading, and ear training, and use a warm palette". One sentence covers the landing page and the dashboard.
2. Change the window: "show fourteen days instead of seven, and keep the strip scrollable on a phone". The week strip is the single most structural thing in the file.
3. Change what counts: "let a habit have a target of three times a week, and mark the week complete when the target is met". This is two or three edits, not one, because the completion maths changes with it.
4. Add a note: "let me attach a short note to a completed day and show it on tap".
5. Publish to your .zugo.run address and use it for a week on a phone. A tracker that is awkward on a phone is a tracker nobody keeps.

Each rebuild is opened in a sandbox before it reaches you, so an edit that produces a broken screen is reported as a failure rather than handed over. A simple build takes about a minute, so the loop of edit, look, decide stays short enough to keep doing.

What does reworking Continuum cost?

Cloning is free because nothing is generated: a finished page is copied into your project. Credits start moving at the first edit.

Free comes with 5 credits, enough for the clone and one edit, which is genuinely enough to see whether the shape suits you. Pro is $25 a month for 200 credits, about 66 edits or 33 builds, and Business is $99 a month for 800. A full personality change on this template usually lands under ten edits, because most of the work is copy and colour rather than structure.

What do you have to connect for real users?

Out of the box, Continuum stores its data in the browser it is opened in. That is a real improvement on a static mockup and completely insufficient for a product, because two phones are two separate sets of habits and clearing site data erases the lot.

Supabase closes the gap: a table for habits, a table for completions, and email sign in so a row belongs to a person. Ask for it explicitly, including the access rule: "connect Supabase, store habits and daily completions, and only ever show the signed in user's own rows".

After that the useful additions are small. Resend for a weekly summary email, Google Analytics to see whether people come back on day three, Stripe only if you are charging. GitHub export exists for the day you hand it to a developer, and the details of the database step are in connecting Supabase to an AI built app.

Do the database before the polish. Styling a screen whose data is about to be restructured is the most common way to pay for the same edit twice.

Where does this template genuinely stop?

Three limits worth saying plainly.

Reminders are not in it, and they are not a small edit. A browser page cannot reliably nudge someone at eight in the morning, so real reminders mean push notifications or scheduled email, which is separate infrastructure rather than a sentence in chat.

There is no history beyond the visible strip. Streaks carry a starting number, but there is no month view, no year heatmap and no export. Each of those is a real feature to request, not a hidden setting.

And the social layer is absent by design. Friends, shared challenges, comparison: that is a different product with accounts, invitations and permissions. Zugo will not stand in for a development team once you go there, though it will get you a working single user version to test the idea first. If a wider view of the category helps, see building a habit tracker with AI.

Where to start

Open the gallery, find Continuum under apps, and press preview. Mark a few dots, reload the page, and watch what survives: that thirty second test tells you more about the template than any description of it.

Then edit in small steps. Subject first, then the week window, then the stats, then colour. Doing colour first is the classic mistake, because a structural edit afterwards throws half of it away.

The template is at zugo.dev, free credits and all, and the version you publish gets an address you can open on your phone the same evening.