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
- solicitações
- 4
- votos
- 374
- planejadas
- 4.119
- entregues
- (motir-meta) The public-skills DRIFT GUARD — `SKILLS_DRIFT.check.py` re-hashes every corpus section a pinned `motir-skills` standalone procedure cites and fails, naming the skill and section, when `origin/main` has moved past it; wired into CIMotir 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-marketing) The `/docs/skills` guide — install Motir's skills in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot (VS Code) and OpenCode, and how to use `motir-run`, `motir-log-bug` and `motir-mark`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-meta) Retire the in-repo `motir-run` / `motir-log-bug` / `motir-mark` doors — `install.sh` installs them from the pinned `motir-skills` release, `--check` flags a stale tag, `DOORS.check.py` covers the private doors only, `_shared.md` says where the public ones liveMotir 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 go public — release `motir-skills` v0.1.0, publish the motir.co/docs/skills guide, and motir-meta installs `motir-run`, `motir-log-bug` and `motir-mark` from the tag, retires its copies and guards driftMotir 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
- DECISION (recorded) — motir.co's public feature-request board is retired, and a public project's pending requests move into the app: signed-in Visitors read them in a Requested features view and upvote them there, while motir.co keeps the request form, request pages, upvotes and comments anonymousRoles & 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
- The Advanced filter drops a just-added empty condition row when an earlier live-apply navigation lands late — `epic6-journey` @smoke flakes on it
- (motir-skills) The two-mode `motir-guide` skill — runbook mode routes to `prompts/guide.md`; standalone mode condenses the one-step-at-a-time walk, read-only validation, ticking, resume and closeMotir 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 GUIDE protocol — `prompts/guide.md`: claim a manual card, take or derive its steps, ONE step at a time, read-only validation, tick, resume, closeMotir 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
- (verification) The three to-do tools are LIVE on app.motir.co — `tools/list` names them, and a list → add → tick → untick round trip works on a scratch cardMotir 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
- Guided manual work — confirm the to-do tools live, then the guide protocol in the runbook and the two-mode `motir-guide` 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
- (deploy) Release `motir-skills` v0.1.0 — tag and GitHub release with `motir-run`, `motir-log-bug`, `motir-mark`, then install it from the tag as a consumer wouldMotir 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 · test) E2E — a public project reads signed-out and is listed in Explore; a Manager switches it to Members only and it leaves Explore and reads not-found signed-out and to a workspace member not added; no acceptance video, because this story adds no surfaceRoles & 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 access-column integration gate — the changed surface topped up to the 90% floor, all seven public-read policies driven against the real database under the app role for a public and a Members-only project, and a project created with no mode landing as Open to the workspaceRoles & 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) Nothing reads `accessLevel` any more — the seven public-read RLS policies re-keyed on `access_mode = 'public'`, the public project listings, the explore search SQL and the tag counts filtered on `accessMode`, and a guard that fails any new readerRoles & 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) `access_mode` is NOT NULL and read directly — a migration that fills every NULL from `accessLevel`, refuses to run if any project's two columns disagree, and sets DEFAULT `workspace` and the constraint; `accessModeOf` deleted, with every caller reading `project.accessMode`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 · chore) Every test sets a project's access through ONE helper that writes the mode and its mapped level together — the tests that write `accessLevel` directly rewritten, and a guard that fails any new direct writeRoles & 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
- The project's access mode becomes the only access column anything reads — `access_mode` NOT NULL with every empty row filled, the seven public-read policies and every public listing keyed on it, and `accessModeOf`'s fallback gone (Release 1 of the three-release retirement of `accessLevel`)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 · test) Story integration gate — the three to-do tools through the real MCP transport: permissions, cross-tenant isolation, ticking, appending, and a concurrent double-tickMotir 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 MCP door onto a work item's TO-DO LIST — `list_work_item_todos`, `add_work_item_todo` and `set_work_item_todo_done`, over the shipped `workItemTodosService`, gated `project:browse` / `work_item:edit`, documented in `docs/mcp.md`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
- Agents read and tick a card's to-do list over the MCP — `list_work_item_todos`, `add_work_item_todo` and `set_work_item_todo_done`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