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
- 488
- planned
- 5,024
- shipped
- (motir-skills) The two-mode `motir-fix-bugs` skill — runbook mode routes to `prompts/fix-bugs.md`; standalone mode condenses the population, the three terminating dispositions and one PR per bugMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-meta) The FIX-BUGS protocol — `prompts/fix-bugs.md` + `prompts/fix-bugs.py next`: the Bugs folder's own `todo` bugs, one at a time, three terminating dispositions, one PR per bugMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- Fix the Bugs folder — the fix-bugs protocol in the runbook and the two-mode `motir-fix-bugs` skill on `motir-skills` `main`Motir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-ai) `creditLaneGate`'s two regression-seam tests loop every shipped planning rate under vitest's default 5 s timeout, so they time out on a loaded runner
- (motir-skills) The two-mode `motir-run` skill — runbook mode routes into `run.md`; standalone mode condenses the close-out sweep, claim, branch-per-card, one PR, status walk, How to test, out-of-scope bugs, and the no-`motir-plan` fallbackMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-skills) Scaffold the public skills repository — README, the two-mode SKILL.md shape, the sync-metadata format, plugin-marketplace manifests and a CI validator — and ship `motir-mark` and `motir-log-bug` in itMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- Motir's skills in a public repository — `motir-run`, `motir-log-bug` and `motir-mark` as two-mode skills on `motir-skills` `main`Motir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-ai) The Part 1 conversation composes the `core` pack whole, so its system prompt names tools it does not hold — and one rule tells it `web_search` "is on your tool surface"
- (verification) On the live tenant, a run without `motir-plan` submits its correction to the hosted planner — and with a token lacking `ai:plan` it parks, comments and stopsMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (manual) Create the public `moooon-B-V/motir-skills` repository (MIT, `main` protected) and connect it to the MOTIR project's repository setMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-core) The Visitor consent screen at `app.motir.co/p/<identifier>/consent` — it says the reader's name and email will be visible to the project's Managers, Continue records the consent and returns to the view they asked for, Go back leaves without a recordRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) A person's own visitor records in their account data export — which public projects they consented to share their name and email with, and whenRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The project's Visitors, for its Managers — a Visitors section on Settings › Access & members listing each visitor's name, email, first and latest visit and consent time, newest first and paged, behind `project:manage_access`Roles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The Visitor needs a session and a consent — `resolveVisitor` answers `sign_in` with no session and `consent` for a signed-in non-entrant with no record, `visitorRecordsService.recordConsent` writes the record, a Visitor read touches the latest visit, and `public-projects.md` and `role-model.md` are amendedRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The visitor record — a `project_visitor` table (project, person, consented at, first and last visit), its repository, and the migration, deleted with the person or the projectRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The work-item page honours the Visitor — a hidden item is not-found by key, and a visible item's edges, child panel, rollups, work-item chips, activity and comments name no private-epic descendantRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core · test) E2E + acceptance video — a reader follows a public project's link, signs in, is told their name and email go to the project's Managers, continues, walks the items list, tree, board, roadmap, an item, Plans, Approvals and Runs, meets no write control and no private epic's child, is not asked again, and the project's Manager sees them in the Visitors list with their emailRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core · test) The story's integration gate — the changed surface topped up to the 90% floor, the Visitor's sign-in, consent and reads driven through the real resolver and datastore with a private epic in the fixture, a no-email scan over every Visitor payload with the Managers' list the one email-bearing surface, and a guard that drives every write route and server action as a Visitor and asserts refusal with no row changedRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The Build-in-public settings page offers the project's Visitor link — copyable, shown only while the project is Public and the cloud capability is on, behind the page's existing keyRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- (motir-core) The Visitor route tree at `app.motir.co/p/<identifier>/<view>` — the Visitor layout sending a signed-out reader to sign-in and a first-time reader to the consent screen, the Visitor chrome over the shared page bodies, `proxy.ts` letting the view paths through while the bare path and act pages still 308 to motir.co, a member redirected into their own view, and `public-surface-hosts.md` §2 amendedRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do