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
- 517
- planned
- 4,915
- shipped
- (motir-core) MENTION in the PAGE EDITOR — the work-item picker on `@` and the toolbar, the live chip node view in edit and read, wired through `PageEditorHost`, with its strings in `en` and `zh`Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- (motir-core) The work item's PAGES read — `listPagesForWorkItem` under `page:view`, live pages only, grouped by page with their sources and place, keyset-paged at 50, its route, and withheld from a VisitorPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- (motir-core) The PAGE read carries live CHIP data, and the picker searches ONE project — `getPage` returns `workItemRefs` for the work items its body mentions, and `mention-search` takes a `projectId`Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- (motir-core) The `page_work_item_link` TABLE and the real `replaceDerivedLinks` — migration with the §8.1 columns, unique key, same-project trigger and RLS, the link repository, and the adapter rewriting only derived rows for same-project work itemsPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- (motir-core) `@motir/pages` MENTIONS — the `workItemMention` node in the page schema with its `[KEY](motir:<id>)` markdown round-trip, `extractLinks(body_json)`, and every body write (create, save, markdown write, restore) handing its links to `replaceDerivedLinks`Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- Mention a work item in a page and find the page on that work item — the page editor's work-item picker and live chip, link rows written on every page save, and the work item's Pages sectionPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- (motir-core) The quick view never appears while a roadmap canvas is in full screen — it portals to document.body, outside the element the browser made full screen
- (motir-ai) `graphServiceWarming` AC 3 case races a 100 ms per-call timeout, so `both are answered once a 200 ms download lands` fails intermittently under load
- (decision) A personal access token passes the platform-staff gate on the ideas endpoints only, when the token's owner is platform staff at the required level — no new scope; every other platform surface stays session-onlyIdeas to build becomes a living idea store — the owner curates ideas in motir-core by hand and by a recurring research skill, and motir.co shows them live, searchable by category, tag and text
- (motir-core · design) The work item's PAGES section — linking pages with title, place, how linked and last edited, paged, and its empty / loading / error / no-access states (delta mock)Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- agentTerminalStoryGate's owner-only test reads the connection row before the relay's fire-and-forget insert lands, so it fails intermittently under CI load and ejects PRs from the merge queue
- (motir-core · design) MENTION a work item in a PAGE — the page editor's work-item picker (`@` and toolbar), the inline chip in edit and read, and its unavailable / hidden states (delta mock)Pages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- (motir-core) `@motir/pages` save test compares two independently encoded Yjs states, so `refuses a merged state over the body cap after the lock` fails intermittently on its exact `size`
- motir.co adopts the warm-touch default palette — re-pin `@motir/design-system` from 0.6.0 to the release that carries it, and prove the site renders it (motir-marketing)
- A Combobox menu inside `Modal.Body` is clipped by the body's scroll edge — only the first few options show (e.g. Add a model planning may use)
- Release `@motir/design-system` carrying the warm-touch Motir palette — merge the Version Packages PR, let the tag lane publish, and pull the published version from npm
- (motir-meta) Pin `.claude/skills/PUBLIC_SKILLS` to the release that carries the run-reporting `motir-run`, reinstall the doors, and `install.sh --check` reads cleanRun provenance — every run of a card records who ran it, on which model and for how long, however it was started
- (motir-skills · deploy) Release `motir-skills` with the run-reporting `motir-run` — the next minor tag and GitHub release, the plugin manifest's version bumped, then the skill installed from that tag as a consumer would and read backRun provenance — every run of a card records who ran it, on which model and for how long, however it was started
- Story E2E + acceptance video — the default Motir palette with its warm touches, light and dark, identity roles unchanged (motir-core)
- Story integration gate (motir-core) — coverage floor, seams and guards over the warm-touch palette change