By mayankdharwa
Explore → plan → build workflow for backend features. `develop-feature` for multi-day, multi-topic features; `develop-mini-feature` for ~day-scale, 1–2 area features with a one-way graduation path between them.
Use when bootstrapping a new feature under `docs/<feature>/`, locking units, deferring questions, distilling spec, archiving build sections, surgically reopening locked phases, or checking project-done. Operates a three-phase exploration → spec → build process for medium-to-large backend features. Invoke with arg `review` to act as the Review Agent during build.
Use for small features (up to a day, 1–2 areas) under `docs/<feature>/` — bootstrapping, advancing phases, lifting decisions, optional review. Mirrors `io:develop-feature` shape but drops phase/topic/section ceremony. Graduates to `io:develop-feature` when scope grows. Invoke with arg `review` to act as the Review Agent.
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.
A Claude Code plugin marketplace. Each plugin in this repo bundles one or more skills (and, eventually, commands / hooks / agents) under a single namespace.
Add the marketplace once, then install plugins individually.
/plugin marketplace add mayankdharwa/helios
/plugin install io@helios
For a local clone:
/plugin marketplace add /path/to/helios
| Plugin | Skills | Slash commands |
|---|---|---|
io | develop-feature, develop-mini-feature | /io:develop-feature, /io:develop-mini-feature |
iodevelop-feature — three-phase exploration → spec → build process for medium-to-large backend features. Invoke as /io:develop-feature, or with args="review" to act as the Review Agent during build.
develop-mini-feature — lightweight explore → approach → build cycle for ~day-scale features touching 1–2 areas. Invoke as /io:develop-mini-feature, or with args="review" for the Review Agent. Graduates one-way into develop-feature when scope grows.
Each plugin lives in its own top-level directory with this shape:
<plugin-name>/
├── .claude-plugin/
│ └── plugin.json
└── skills/
└── <skill-name>/
└── SKILL.md
Then add an entry to .claude-plugin/marketplace.json:
{
"name": "<plugin-name>",
"source": "./<plugin-name>",
"description": "..."
}
Skills inside a plugin appear as /<plugin-name>:<skill-name>.
npx claudepluginhub mayankdharwa/helios --plugin ioReliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls