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
- 需求
- 4
- 贊同
- 501
- 已規劃
- 4,954
- 已發布
- A planning-rail submit that outlives a waking motir-ai is still one unkeyed 30 s attempt, so its late job can run and bill with no plan, and Try again pays twice
- Translate the second group of docs (slugs 6–9) into content/docs/<slug>/zh-tw.md with matching front-matter source (motir-marketing)
- Translate the first group of docs (slugs 1–5 as listSlugs orders them) into content/docs/<slug>/zh-tw.md with matching front-matter source (motir-marketing)
- Seed and review the zh-tw catalogue (messages/zh-tw.json, messages/sources/zh-tw.json) from zh.json in Taiwan vocabulary, and generate the zh-tw OG font subsets (OG_CJK_LOCALES, brand:og-fonts, ogFonts.ts case) (motir-marketing)
- Story-level integration gate for motir-core: coverage floor and seam/contract guards over the glossary, the zh-Hant font set and the Traditional Accept-Language rule (motir-core)
- Widen the two-letter locale assumptions so a zh-tw code passes: docs.test.ts [a-z]{2}.md, publicApiStub.ts, acceptance-legal-binding-english.spec.ts, routing.test.ts og regex (motir-marketing)
- State the Traditional-Chinese Accept-Language rule in lib/i18n/acceptLanguage.ts: zh-TW, zh-Hant, zh-HK, zh-MO and zh-Hant-* resolve to zh-tw when the locale set holds it, else to zh (motir-core)
- Add the zh-tw glossary (messages/glossary/zh-tw.json) in Taiwan vocabulary, with the "work item" banned-words entry and the nav.productItems.* product names (motir-core)
- `likely-self-blocking-design` reports a server-only card as its own design blocker — "the shared mock's" reads as a design asset, and "a page … before any transaction opens" as a rendered surface
- Publish the @motir/design-system version carrying the zh-Hant font set to npm (manual)
- The Design asset guards job is cancelled at its 10-minute timeout because tests/design-state-ink-contrast.test.ts takes 5–8 minutes to import
- The Calculator view cannot print a larger pool's credits: motir-core's estimate DTO has no recommendation.poolCredits
- The load-test report has no agent-mix breakdown — served rate and latency are never split by reads, writes, claims, runs and readers, though k6's points carry the group and role tags to do itmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Animate the Motir mark beside the planning notes while Motir AI is working
- Add the zh-Hant font set to @motir/design-system: Noto Sans TC / Noto Serif TC / LXGW WenKai TC, 'zh-tw' in the registry, resolveFontSet trying the full tag first, and [lang]:lang(zh-TW) blocks in theme.css (motir-core)
- A conversation's target leaves Planning 30 minutes after the last turn while its hosted walk is still writing the plan: the lock sweep treats every `generating` plan as a dead author
- Implement the refined /onboarding and /onboarding/migrate pages
- A conversation turn sent while motir-ai is asleep fails after core's 30 s submit deadline, yet motir-ai may still run and bill it — the person sees "didn't finish", and Try again can charge twice
- Refine the onboarding pages (/onboarding and /onboarding/migrate)
- Planning bug (both planners): a design card allocates its elements to named consumer cards and amends what it TAKES from them, and a consumer is authored in parallel with its design. A design should describe its elements only; a session writes its blocked_by edge first, and the consumer is authored after its design and claims what it builds