Jellydn My Ai Tools
jellydn-my-ai-tools is a Claude Code plugin for the Build phase that replicates a ten-plugin AI coding configuration with MCP servers, handoffs, planning, and TDD workflows across Claude Code and sibling agents.
by jellydn · github.com/jellydn/my-ai-tools
Clone a full multi-tool AI coding setup—MCP servers, plugins, handoffs, PRD/TDD flows, and session continuity—for Claude Code, OpenCode, Amp, and Codex from one maintained bundle.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install jellydn-my-ai-tools@jellydn/my-ai-toolsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:jellydn/my-ai-tools") and the paste-ready config with skillselion.get_install_config("plugin:jellydn/my-ai-tools").
What it does
jellydn-my-ai-tools is a Claude Code plugin collection that exports jellydn’s production AI coding configuration so indie builders can bootstrap the same MCP servers, plugins, slash commands, and cross-editor switches they use daily. The ten plugins read like a compressed journey: product requirements and planning artifacts, architectural decision records, handoffs between sessions, Ralph continuation patterns, TDD discipline, refactor passes, and codebase understanding via codemaps and structured search. Because it spans planning, implementation, review, and resume-after-interrupt flows, treat it as journey-wide process infrastructure even though Skillselion shelves it under Build and agent-tooling for discovery. It suits builders who want one maintained reference stack instead of assembling OpenCode, Amp, and Codex configs separately. Expect strong opinions on workflow gates; disable pieces that conflict with your team’s ship or security policies. Prerequisites include willingness to align directory layout and secrets with the author’s patterns.
Highlights
- Ten plugins covering handoffs, Ralph-style loops, PRD generation, planning, TDD red-green-refactor, and codebase maps
- Cross-tool replication for Claude Code, OpenCode, Amp, Codex, and Claude Code Switch
- Session continuation, structured notes, ADR-style decision capture, and searchable context (qmd motifs)
- Parallel and orchestration-oriented workflows for implementing features with quality and slop checks
- MCP servers, custom commands, and plugins bundled as one opinionated solo-builder stack
Why builders use it
Solo builders lose days replicating MCP wiring, handoff rituals, and multi-editor configs every time they switch machines or agent products.
After you register the bundle, you inherit a documented, multi-plugin agent toolchain with continuity, planning, and implementation commands ready to adapt.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 53 stars, 0 votes.
FAQ
Who is jellydn-my-ai-tools for?
It is for solo builders and small teams who want jellydn’s complete AI tool configuration—MCP, plugins, commands, and cross-editor switches—without manually copying dotfiles and docs.
When should I use jellydn-my-ai-tools?
Use it when you are standing up or migrating agent-tooling at the start of a build (or after validate) and need session handoffs, planning, and implementation commands across the whole delivery cycle.
How do I add jellydn-my-ai-tools to my agent?
Install the Claude Code plugin from jellydn/my-ai-tools, follow the repo’s setup for MCP and secrets, then enable the subset of ten plugins that match your editors (Claude Code, OpenCode, Amp, Codex, CCSwitch).
Comments
Share how you use jellydn-my-ai-tools, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.