Skip to content
Motir
Start free

moooon

Motir

Vibe your whole 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
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-2705Done

The platform starter's own maintenance — keeping the vendored copies, CI lanes and scaffold-time defaults true as motir-core moves

A standing, single-repo home for work on nextjs-prisma-vercel-starter itself: the vendored scripts, the CI lanes, and everything a scaffolded project inherits on day one.

Why it exists

The starter is a template, not a library. It cannot import from motir-core, so the parts it shares are copied — scripts/upload-acceptance-video.mjs says so in its own header ("It is not a fork: keep it in sync"), a decision made deliberately in MOTIR-1941. Copies drift, and the drift is invisible until someone downstream trips on it.

Until now that work had nowhere of its own to live. Starter cards were filed as children of whichever motir-core story happened to surface them — MOTIR-1941 and MOTIR-1958 under MOTIR-1627, MOTIR-2673 under MOTIR-2664 — which put two repos inside one story and made those stories unrunnable (MOTIR-2700). This story is the alternative that rule requires: starter work is a SEPARATE story, linked to whatever prompted it, never a child of it.

Scope

  • Vendored-copy re-syncs. Scripts copied from motir-core that have fallen behind upstream cards.
  • CI lanes. The workflows a scaffolded project inherits — correct triggers, correct failure semantics, no lane that is red or green for the wrong reason.
  • Scaffold-time defaults. Anything whose first impression lands on someone who just used the template and has configured nothing.

Not in scope

  • Feature work in motir-core that happens to also need a starter port. That is two stories: the motir-core one, and a starter one linked to it.
  • The -with-design sibling starter, unless a card names it explicitly.

How to use it

File a starter bug or task here, targeting nextjs-prisma-vercel-starter, and relates_to whatever surfaced it. motir run this story to work a batch of them as one branch and one PR — which is the whole point of keeping it single-repo.

Context refs

  • nextjs-prisma-vercel-starter/docs/acceptance-video.md § Why the uploader is VENDORED here — the standing decision this story is the maintenance cost of.
  • MOTIR-9 / MOTIR-24 / MOTIR-25 — where the starter came from.
  • MOTIR-2700 — the ONE STORY = ONE REPO rule that makes this story necessary rather than optional.