By mergodon
Lean work rhythm: close + mailbox + cross-repo GitHub issues. The lean rebuild of td-flow.
Wrap a work session or project — capture core knowledge to repo docs (working-style to memory), run a fresh-eyes sweep of docs + memory (flag doc drift, prune stale/duplicate/misfiled memory), park leftover TODOs to GitHub issues, commit, and push. The lean close ceremony.
Migrate THIS project off td-flow onto lean td-fly — swap the contract @import, PRESERVE load-bearing knowledge into repo docs, park backlog to issues, fold the cross-repo registry into CLAUDE.md, then remove the scaffold — and when it's the last td-flow repo, retire the global td-flow install too. Previews the whole plan first; destructive and one-way, runs only on confirm.
Cross-repo work check — issues filed INTO this repo (inbound) and issues this repo filed INTO others (outbound), as one digest with a recommended action each. Decide in one reply; reversible actions just run.
The lean rebuild of td-flow — three commands (close, mailbox, flow-down) plus the cross-repo GitHub-issues protocol and the @import contract, shipped as a native Claude Code plugin. Everything else from td-flow was cut.
This folder is both the plugin and its own marketplace — .claude-plugin/marketplace.json lists the plugin and points its source at the public mergodon/td-fly github repo, so it installs on any machine with no extra repo.
/plugin marketplace add mergodon/td-fly
/plugin install td-fly@td-fly
Commands land namespaced under the plugin: /td-fly:close, /td-fly:mailbox, /td-fly:flow-down.
Because the marketplace source is the GitHub repo (not this local folder), iterating on a command is: edit → commit → push → /plugin marketplace update td-fly → /reload-plugins. Local-only edits won't show until pushed.
@import contractcontract.md is the one shared rhythm file. install.sh symlinks it to ~/.claude/td-fly.md; each project adopts it with one line at the top of its CLAUDE.md:
@~/.claude/td-fly.md
The symlink points back into this repo, so a git pull here updates the contract in every project at once — zero drift. A project declares its cross-repo connections under a ## Cross-repo heading in its own CLAUDE.md; that list scopes /td-fly:mailbox outbound.
/td-fly:close (lean close ceremony)/td-fly:mailbox (cross-repo issue digest — slimmed from td-flow's bulky original)@import contract / rendezvous convention (contract.md + install.sh)/td-fly:flow-down (migrate a project off td-flow, preserving its knowledge into repo docs)/ship-watch first)Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub mergodon/td-fly --plugin td-flyComprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.
Unified status line for Claude Code with multi-CLI (Claude, Codex, Gemini, z.ai) usage monitoring, context, rate limits, and cost tracking