M
melucasleite/ultracodefactory
Ultra Code Factory: a native macOS app that turns your markdown backlog into pull requests with Claude Code…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · melucasleite/ultracodefactory · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-24 · last seen 2026-11-14 · seen 25× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
melucasleite/ultracodefactory;first catalogued 2026-10-24;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Ultra Code Factory
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Your backlog is the assembly line. Claude Code agents are the crew.
A native macOS kanban board for markdown work cards, built in SwiftUI with Liquid Glass.
🌐 ultracodefactory.com
Website ·
Quick start ·
How it works ·
Security
Ultra Code Factory turns a folder of plain markdown files into a production line.
Every card is a .md file and every column is a folder. Drag a card and the
file moves. Describe an idea and an agent writes the card. Hit Run Work
and an agent picks it up inside the project's repository. You watch its
terminal live, answer its questions with real buttons, and get a notification
the moment it needs you.
No database, no account, no cloud. Your cards stay plain text, so they work
just as well in Obsidian, your editor, git or grep.
## Core tenets
What Ultra Code Factory believes, and builds for.
1. The spec is the product. Code is an implementation detail. The
brief, the cards and their acceptance criteria are what you own and care
about. Code is one way of meeting them: it can be rewritten, regenerated or
replaced, but a clear spec keeps its value.
2. Docs first, always. Every project starts with a PROJECT.md, and every
change starts as a card that says what and why before anyone (or anything)
writes how. If it isn't written down, it isn't ready to build.
3. Specs live with the code. Cards are markdown files in the repository,
versioned in the same commits as the work they describe. No database, no
SaaS, no lock-in: git, grep and your editor all just work.
4. You decide, agents do. You set direction, answer questions and review.
Agents do the typing. The factory never merges for you.
5. Small cards, small PRs. A card should fit in one reviewable pull
request. If it can't, it's two cards.
6. Review is the job. Your time is the scarce resource, so it goes to
judgement (what to build, whether it's right) and not to keystrokes.
7. Safe by default. Agents get the least permission that works. Anything
more is a deliberate choice you make, with the risk spelled out.
## Highlights
| 🏭 Live board | Six stations: Proposed, To-Do, Picked Up, Waiting, Done, Won't Do. Drag and drop, search, and a filter by kind. FSEvents updates the board the instant any file changes, whoever changed it. |
| 🪄 Create Work | Type an idea and a headless claude -p agent turns it into a card. A hazard-striped Fabricating… placeholder holds its spot until the card lands. |
| ▶️ Run Work & Triage | Interactive Claude Code sessions run in detached tmux sessions, one per job, inside the project's repository. |
| 💬 Native questions | When Claude asks a multiple-choice question, the console turns it into glass buttons. Click one or press ⌘1–⌘9. |
| 🖥️ Live consoles | A full-colour mirror of every agent's terminal with keyboard passthrough, ⌃C, and a one-click tmux attach command for your own terminal. |
| 🧭 Factory Floor | A floating glass panel listing every agent's state (working, waiting for you, finished, failed) with elapsed time and Stop. |
| 🔔 Stays out of the way | A menu bar status icon, plus notifications when an agent finishes or needs input. |
| ✅ Real markdown | Rendered cards with clickable checkboxes that write straight back to the file, and a raw editor on ⌘S. |
A native macOS kanban board for markdown work cards, built in SwiftUI with Liquid Glass.
🌐 ultracodefactory.com
Website ·
Quick start ·
How it works ·
Security
Ultra Code Factory turns a folder of plain markdown files into a production line.
Every card is a .md file and every column is a folder. Drag a card and the
file moves. Describe an idea and an agent writes the card. Hit Run Work
and an agent picks it up inside the project's repository. You watch its
terminal live, answer its questions with real buttons, and get a notification
the moment it needs you.
No database, no account, no cloud. Your cards stay plain text, so they work
just as well in Obsidian, your editor, git or grep.
## Core tenets
What Ultra Code Factory believes, and builds for.
1. The spec is the product. Code is an implementation detail. The
brief, the cards and their acceptance criteria are what you own and care
about. Code is one way of meeting them: it can be rewritten, regenerated or
replaced, but a clear spec keeps its value.
2. Docs first, always. Every project starts with a PROJECT.md, and every
change starts as a card that says what and why before anyone (or anything)
writes how. If it isn't written down, it isn't ready to build.
3. Specs live with the code. Cards are markdown files in the repository,
versioned in the same commits as the work they describe. No database, no
SaaS, no lock-in: git, grep and your editor all just work.
4. You decide, agents do. You set direction, answer questions and review.
Agents do the typing. The factory never merges for you.
5. Small cards, small PRs. A card should fit in one reviewable pull
request. If it can't, it's two cards.
6. Review is the job. Your time is the scarce resource, so it goes to
judgement (what to build, whether it's right) and not to keystrokes.
7. Safe by default. Agents get the least permission that works. Anything
more is a deliberate choice you make, with the risk spelled out.
## Highlights
| 🏭 Live board | Six stations: Proposed, To-Do, Picked Up, Waiting, Done, Won't Do. Drag and drop, search, and a filter by kind. FSEvents updates the board the instant any file changes, whoever changed it. |
| 🪄 Create Work | Type an idea and a headless claude -p agent turns it into a card. A hazard-striped Fabricating… placeholder holds its spot until the card lands. |
| ▶️ Run Work & Triage | Interactive Claude Code sessions run in detached tmux sessions, one per job, inside the project's repository. |
| 💬 Native questions | When Claude asks a multiple-choice question, the console turns it into glass buttons. Click one or press ⌘1–⌘9. |
| 🖥️ Live consoles | A full-colour mirror of every agent's terminal with keyboard passthrough, ⌃C, and a one-click tmux attach command for your own terminal. |
| 🧭 Factory Floor | A floating glass panel listing every agent's state (working, waiting for you, finished, failed) with elapsed time and Stop. |
| 🔔 Stays out of the way | A menu bar status icon, plus notifications when an agent finishes or needs input. |
| ✅ Real markdown | Rendered cards with clickable checkboxes that write straight back to the file, and a raw editor on ⌘S. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/melucasleite-ultracodefactory/)
- Source
- github · https://github.com/melucasleite/ultracodefactory
- Browse by field
- Open source
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.