Use case guide
How to use SideQuick for programming and side projects
Side repos die when the next shiny idea arrives. The fix is not more motivation, it is a visible trail of "what is next" and proof you showed up this week. SideQuick is free end to end, no account wall, works on Windows, Mac, and Linux, and stores projects locally so your roadmap is not another SaaS database.
Steps that map to the real app
1Spin up a project that sounds like shipping, not fantasising
Give it the repo name or product name you would tell a friend. Write a one-paragraph north star in the description so future-you remembers the point. If you use AI generation, choose Programming as the category so titles read like engineering work, not generic chores.
2Generate a quest tree, then edit like a tech lead
Use AI-assisted setup to propose stages (scaffold, core feature, polish, release) and quests under each. Immediately rename anything that is too vague. Large scope should feel like a deep tree, small scope like a tight ladder. You keep full control; the model just speeds up the first pass.
3Work in focus mode when you are actually typing
Start a session on the quest that matches the file or feature in front of you. Hide the noise, stay inside the loop, and let the timer run so you see how long real coding takes. When you switch tasks, move the active quest so your history matches reality.
4Use streaks as an early warning for the abandoned repo trap
A quiet streak is data. If you notice two missed weeks, shrink the next quest until it is embarrassingly small (one commit, one test, one doc). Small shipped beats big imaginary. XP and levels are there to celebrate those tiny wins.
5Close the loop with notes you will read
Jot decisions, URLs, and "why I paused here" inside the project so re-entry is cheap. Local-only storage means you can paste stack traces or half-baked ideas without worrying about cloud sync drama.