moooon
Motir
Vibe the project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.
- Vibe Project
- Open Source
- AI Agent
- AI Loop
- 5
- richieste
- 4
- voti
- 419
- pianificate
- 4270
- rilasciate
- (motir-core) The 47 `getActiveProject()`-null `EmptyState` branches across `app/(authed)` and `app/(onboarding)` — each dispositioned, with its en + zh keys
- (motir-core) Retire the SHELL's own no-project states — `ProjectTier`'s create-first door, the `hasProject` gates it feeds, and the `design/shell` asset that draws them
- (motir-core) Retire the two `ProjectsEmptyState` SCREENS and the component itself, with the guard that no `app/(authed)/**` call site can come back
- (motir-core) A newly REGISTERED reader lands on `/onboarding` — composed in `lib/navigation/landing.ts`, sign-IN unchanged
- (motir-core) `ensureDefaultProject` — the WORKSPACE-tier seam that makes "you are always in a project" true at every zero-project moment, not only at registration
- 8.88 (motir-core) YOU ARE ALWAYS IN A PROJECT — seed a default project at the WORKSPACE tier, land a new registration in `/onboarding`, and retire every no-project surface
- (motir-core) Four shipped components animate on open — except nothing in the repository generates `animate-in` / `animate-out` / `fade-in-0` / `fade-out-0`, so every popover, tooltip, toast and sidebar panel appears instantly
- (motir-core · design) STATE-variant utilities are inert in 3 mocks — 104 occurrences, including a `placeholder:` ink that paints with no interaction at all
- (motir-core) `render-design-mock.mjs` exports the LIGHT board only — a dark export silently keeps drawing the old design, and no guard reads `*.dark.png`
- 8.90 (motir-core) Every pull-request row reads "linked manually" — the flag records a distinction MOTIR-3674 deleted, and its only writer is now the agent's own `link_pull_request`
- (motir-core) The approval-gate ADR — record what a gate IS, its routing and authority, its audit trail, how a third kind registers, and the line against Story 9.2Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · design) 365 rules across 87 hand-written mocks are declared and carried by NO element in the whole design tree — the direction MOTIR-4150 was filed for, now counted
- (motir-core) A repository MOTIR HOSTS is drawn under `From your organisation` and counted as `yours` — the room reads `github_repo` by WORKSPACE and never consults `hostOwner`
- (motir-core) The landing owner-guard reads COMMENTS, so a link whose intent lives in its ACCESSIBLE NAME is invisible to all three scans — the shape that let the brand mark keep `/dashboard`
- (motir-core · design) STRUCTURAL `[&_…]:` utilities are inert in 8 mocks — 500 occurrences, and 452 of them size a nav icon that renders at 24px instead of 18px
- (motir-core · design) `text-(--el-text-faint)` means two different colours depending on the mock — 5 assets declare it as `--el-text-secondary`, and the ink guard reads the declaration
- (motir-core) `get_project_state` reports `code connected: false`, and the repo picker offers nothing, for every workspace of an organisation OTHER than the one the App was installed from
- (motir-core) The project room’s two sections mis-state what they hold — an empty `From your organisation` and copy that still names the WORKSPACE
- (motir-core · design) Design mocks USE arbitrary-value utilities their own shim block never DECLARES — 131 inert utilities across 8 assets, and no guard looks in this direction
- 26 (motir-core) The planning overlay's canvas never groups the work items that are in no epic — MOTIR-3490's "Not in an epic" node and its "+ N more" tile were opted into at ONE of five `buildWorkItemLevel` call sites, and the overlay is not it