Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By ed3dai
Use specialized AI agents to deeply investigate local codebases for structure and patterns, research current internet sources for API docs, libraries, and best practices, and clone/analyze remote Git repos with precise file citations—grounding feature planning and tech decisions in verified data before coding.
npx claudepluginhub ed3dai/ed3d-plugins --plugin ed3d-research-agentsUse this agent when planning or designing features and you need to understand current codebase state, find existing patterns, or verify assumptions about what exists. Examples: <example>Context: Starting brainstorming phase and need to understand current authentication implementation. user: "I want to add OAuth support to our app" assistant: "Let me use the codebase-investigator agent to understand how authentication currently works before we design the OAuth integration" <commentary>Before designing new features, investigate existing patterns to ensure the design builds on what's already there.</commentary></example> <example>Context: Writing implementation plan and need to verify file locations and current structure. user: "Create a plan for adding user profiles" assistant: "I'll use the codebase-investigator agent to verify the current user model structure and find where user-related code lives" <commentary>Investigation prevents hallucinating file paths or assuming structure that doesn't exist.</commentary></example>
Use this agent when planning or designing features and you need current information BOTH the local system AND from the internet, API documentation, library usage patterns, or external knowledge. Examples: <example>Context: Designing integration with external service and need to understand current API. user: "I want to integrate with the Stripe API for payments" assistant: "Let me use the combined-researcher agent to find if and how we currently use Stripe, and then the current Stripe API documentation and best practices for integration" <commentary>Before designing integrations, research current API state and current local codebase state to ensure plan matches reality.</commentary></example> <example>Context: Evaluating technology choices for implementation plan. user: "Should we use library X or Y for this feature?" assistant: "I'll use the combined-researcher agent to research what we've currently selected already, then if we haven't selected something we'll look at both libraries' current status, features, and community recommendations" <commentary>Research helps make informed technology decisions based on current information.</commentary></example>
Use this agent when planning or designing features and you need current information from the internet, API documentation, library usage patterns, or external knowledge. Examples: <example>Context: Designing integration with external service and need to understand current API. user: "I want to integrate with the Stripe API for payments" assistant: "Let me use the internet-researcher agent to find the current Stripe API documentation and best practices for integration" <commentary>Before designing integrations, research current API state to ensure plan matches reality.</commentary></example> <example>Context: Evaluating technology choices for implementation plan. user: "Should we use library X or Y for this feature?" assistant: "I'll use the internet-researcher agent to research both libraries' current status, features, and community recommendations" <commentary>Research helps make informed technology decisions based on current information.</commentary></example>
Use when understanding how external libraries or open-source projects implement features by examining actual source code - finds repos via web search, clones to temp directory, investigates with codebase analysis. Triggers: "how does library X implement Y", "show me how Z handles this", "I want to see the actual code for", evaluating library internals before adoption.
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in reality
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - gathers well-sourced, current information from the internet to inform technical decisions
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Planning and execution workflows for Claude Code. Based on obra/superpowers.
General purpose Claude Code toolkit with research agents, skills, and introspection commands
Plugin for effective agentic development
No description provided.
Skills for effective use of developer tooling
Research existing solutions when exploring a new problem space
Core agents for general-purpose tasks. Other plugins expect this to exist.
EXPERIMENTAL. Session awareness and conversation review tooling. Captures session metadata via SessionStart hook and provides conversation review agents and skills for analyzing prompting effectiveness, agent performance, and environment gaps.
Playwright automation toolkit with MCP integration, specialized agent for browser control, and best practice skills
Getting started guide and onboarding for ed3d-plugins
Ed's stylistic particulars for writing code and English.
This is my collection of plugins that I use on a day-to-day basis for getting stuff done with Claude Code. Most of these are development-oriented in some way or another, but also often end up being useful for other things. Product design, general research, accidentally becoming my homelab sysadmin—these are a lot of what I've learned so far and what I've found helpful.
The big stick in this repository is ed3d-plan-and-execute, which implements an "RPI" (research-plan-implement) loop that I think does a really good job of avoiding hallucination in the planning stages, adhering to high-level product requirements, avoiding drift between design planning and implementation planning, and reviewing the results such that you get out the other end not just what you asked for, but what you actually wanted.
NOTE: ed3d-plugins is generally a more stable marketplace. If you'd like to track changes as they happen a bit more aggressively, take a look at ed3d-plugins-testing.
ed3d-plan-and-executeMore in the README for the plugin, and it's worth skimming, but here's a quickstart:
Rough Idea
│
▼
/start-design-plan ──────► Design Document (committed to git)
│
▼
/start-implementation-plan ──► Implementation Plan (phase files)
│
▼
/execute-implementation-plan ──► Working Code (reviewed & committed)
Customization: Create .ed3d/design-plan-guidance.md and .ed3d/implementation-plan-guidance.md in your project to provide project-specific constraints, terminology, and standards. Run /how-to-customize for details.
| Plugin | Description |
|---|---|
ed3d-00-getting-started | Getting started guide and onboarding for ed3d-plugins. Run /getting-started to see this README. |
ed3d-plan-and-execute | Planning and execution workflows for Claude Code. Feed it a decent-sized task and it'll help you get it done in a sustainable and thought-through way |
ed3d-house-style | House style for software development; Very Opinionated |
ed3d-basic-agents | Core agents for general-purpose tasks (haiku, sonnet, opus). Other plugins expect this to exist |
ed3d-research-agents | Agents for research across multiple data sources (codebase, internet, combined); other plugins expect this to exist |
ed3d-extending-claude | Knowledge skills for extending Claude Code: plugins, commands, agents, skills, hooks, MCP servers. Other plugins expect this to exist |
ed3d-playwright | Playwright automation with subagents |
ed3d-hook-skill-reinforcement | UserPromptSubmit hook that reinforces the need to activate skills—helps make sure skills actually get used. Requires ed3d-extending-claude to work |
ed3d-hook-claudemd-reminder | PostToolUse hook that reminds to update CLAUDE.md before committing |
ed3d-hook-security-hardening | PreToolUse and PostToolUse hooks that catch secrets leakage patterns |
ed3d-session-reflection | EXPERIMENTAL. Session awareness and conversation review tooling. Requires ed3d-extending-claude |
/plugin marketplace add https://github.com/ed3dai/ed3d-plugins.git
All plugins are available from the ed3d-plugins marketplace:
/plugin install ed3d-plan-and-execute@ed3d-plugins
/plugin install ed3d-house-style@ed3d-plugins
# ... etc
ed3d-plugins/
├── .claude-plugin/
│ └── marketplace.json
├── plugins/
│ ├── ed3d-00-getting-started/
│ ├── ed3d-plan-and-execute/
│ ├── ed3d-house-style/
│ ├── ed3d-basic-agents/
│ ├── ed3d-research-agents/
│ ├── ed3d-extending-claude/
│ ├── ed3d-playwright/
│ ├── ed3d-hook-skill-reinforcement/
│ ├── ed3d-hook-claudemd-reminder/
│ ├── ed3d-hook-security-hardening/
│ └── ed3d-session-reflection/
└── README.md
Issues and pull requests gratefully solicited, except ed3d-house-style is my house style, and provided for reference, so I might not take contributions there. (You can make your own house-style plugin though and use that instead!)
ed3d-plan-and-execute and parts of ed3d-extending-claude are derived from obra/superpowers by Jesse Vincent. The original plugin has been folded, spindled, and mutilated extensively.
Some skills in ed3d-house-style are derived from obra/superpowers and others (property-based-testing is a big one) are derived from the Trail of Bits Skills repository.
The original obra/superpowers code in this repository is licensed under the MIT License, copyright Jesse Vincent. See plugins/ed3d-plan-and-execute/LICENSE.superpowers.