Ed3dai Ed3d Plugins
ed3dai-ed3d-plugins is a Claude Code plugin for the Idea phase that anchors a research-plan-implement workflow across eleven modular plugins.
by ed3dai · github.com/ed3dai/ed3d-plugins
Add Ed’s Claude Code plugin set built around research, plan, and implement—with hooks, security reminders, and optional browser automation.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ed3dai-ed3d-plugins@ed3dai/ed3d-pluginsBuilt 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:ed3dai/ed3d-plugins") and the paste-ready config with skillselion.get_install_config("plugin:ed3dai/ed3d-plugins").
What it does
ed3dai-ed3d-plugins is a Claude Code plugin marketplace from Ed’s ed3d-plugins repository, described as centered on a research-plan-implement workflow with a deliberately experimental edge. Rather than one monolithic skill, it spreads capabilities across eleven plugins covering research, planning, execution, documentation, hooks, and guardrails. Solo builders benefit when they want Claude Code sessions to start with investigation, move into an explicit plan, then implement—with hooks that nudge secret hygiene, token awareness, and reflection instead of silent tool churn. Keywords point to browser automation, Playwright testing, marketplace metadata, project librarian patterns, and security-oriented reminders, so the bundle spans idea through ship depending on which plugins you enable. Treat it as a personal workflow lab: not every plugin is production-grade, but the collection teaches a repeatable ritual from reading sources to shipping tested changes. Install the marketplace when you outgrow ad hoc prompts and want modular plugins you can toggle per project.
Highlights
- 11 plugins in one marketplace organized around research-plan-implement
- Session hooks (pre/post tool use, session start) for secrets and workflow discipline
- Playwright and browser-automation oriented tooling for e2e-style tasks
- Claude.md, librarian, and onboarding-style plugins for project context
- Experimental and ‘obra superpowers’-style workflow extensions alongside security hardening
Why builders use it
Jumping straight to codegen wastes context and repeats mistakes when research and planning never get their own structured plugins.
After adding the marketplace, you can chain research, planning, and implementation plugins—with hooks for security and session hygiene—inside one Claude Code setup.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 160 stars, 0 votes.
FAQ
Who is ed3dai-ed3d-plugins for?
It is for Claude Code users who want modular plugins for research, planning, implementation, docs, and light security hardening rather than one all-in-one skill.
When should I use ed3dai-ed3d-plugins?
Use it at the start of a feature or project for research, then enable plan and implement plugins as you scope and build, plus testing plugins before ship.
How do I add ed3dai-ed3d-plugins to my agent?
Install the ed3dai/ed3d-plugins marketplace in Claude Code, select the plugins you need from the eleven-plugin bundle, and configure hooks described in the repo.
Comments
Share how you use ed3dai-ed3d-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.