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
- 6
- requests
- 4
- upvotes
- 597
- planned
- 5,376
- shipped
- (motir-core · design) THE APPROVALS ROOM, drawn — its two scopes, the pending-then-decided order, the row it COMPOSES rather than redraws, the four states' words, and its ENTRANCE in the project railApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) A design card with an open linked pull request raises no `design_result` gate — the publish reads the delivery set, and linking a pull request supersedes an awaiting design gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Decision — AMENDMENT 4 gains Q8: a design card with an open linked pull request shows its result INSIDE the Development block, raises no `design_result` gate, and is decided by the approve-to-merge gateApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Story-level E2E (Playwright) + ACCEPTANCE VIDEO — publish a mock and its note, review it on the card and in the approval overlay, and watch a screenshot and a non-gating publish refusedApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- Story-level vitest gate (motir-core) — the coverage floor over the story's changed surface, the publish → panel seam, the gating refusal against real edges, and the two-file guard's fixture casesApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The design result renders WHAT TO REVIEW — mock frame(s) with the note as a link, older results as file links — and inside the Development block, with the PR rows and How to test, when the card has open linked pull requestsApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-ai) `THE_DESIGN_GATE` in `SHARED_PLANNING_RULES` stops requiring the `.png` and gains the delta-mock and publish-only-when-work-waits clauses — the shipped planner's twin of the pack editApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (starter) `design/README.md` and the README's design section describe the two-file set, the delta mock, the note published as a link, and publishing only when work waits on the designApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The design dispatch prompt — two files, a change drawn as a new delta mock, and the PUBLISH step only when the server finds an open work item `blocked_by` the cardApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Design — the design result as WHAT TO REVIEW: the mock frame(s), the note as a link, older results as file links — and on a card with linked pull requests, INSIDE the Development block with the PR rows and How to test, one sectionApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-marketing) Its design convention and `designThreeFileSet` guard stop requiring the `.png` — the two-file set and the delta-mock rule, in this repository's own copyApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-meta) The runbook and the plan-rules packs teach the new design result — two files, a delta mock for a change, and publish only when an open work item is `blocked_by` the designApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The publish contract — `publish_design_result` and the design-evidence routes refuse an `image`, a `noteMd`, a result without a mock and its note file, and a publish to a design card no open work item is `blocked_by`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The design asset set becomes TWO files — `CLAUDE.md` § Design assets rewritten (notes + mock, a change is a new delta mock, no new `.pen`) and `design-three-file-set` stops requiring a `.png`Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) Decision — `design-result.md` AMENDMENT 4: a result is the changed mock(s) plus a link to the note, carries no screenshot, is published only when an open work item is `blocked_by` the design, and a change is a new delta mockApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- A design result shows only WHAT TO REVIEW — the changed mock with its note one link away, no screenshot, and published only when work waits on the designApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The `/items` project ROOT reads epics, then folders, then its other work items — the three-band level read, its paging, and the tree's client placementProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) `/items` renders its first-run empty state when the root holds folders but NO work items — the rule the design records, and the three E2E specs that assert itProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) Deleting the destination folder CARRIES the destination up — `deleteFolder` re-points the project in the same transactionProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core) Story E2E — a person re-points the Bugs destination to a folder and to Project root, and the next filed bug lands thereProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back