Token-optimized development workflow pack: cached project context, FE/BE pattern scanners, build & wiring verification, session persistence, and self-review — auto-adapts to any stack.
Show all learned instincts with their confidence levels, grouped by domain
Review a pull request with the code-reviewer agent — fetches the PR diff (Azure DevOps or GitHub), reviews against project conventions, and returns prioritized findings.
Sync the current feature branch with the team base branch before a PR — merge base in, resolve conflicts with evidence, verify with build/tests, and report.
Reconcile this project's .claude/idev/ state with the currently installed plugin version — add missing directories and config keys, refresh the CLAUDE.md snippet, and update stale idev git hooks, without touching caches or user content.
Run the skill quality benchmark — static scorecard for every skill in this plugin (or a given plugin directory), with category classification and improvement recommendations.
Senior backend architect for system design decisions — service decomposition, database schema design, API contract governance, migration strategy, reliability and observability patterns. Use when designing a new backend system or service, choosing between monolith/microservices, designing schemas or APIs, or planning a data migration. Advisory only — produces specifications, does not write code.
Branch synchronization agent — merges the team base branch into the current feature branch before a PR, resolves merge conflicts with three-way evidence and intent analysis, verifies the merge with a build and targeted tests, and reports what was merged and how each conflict was resolved. Use when preparing a branch for a PR, when a PR has conflicts with its target, or when asked to sync/update a feature branch with developer/main.
Browser testing agent — verifies web features and user flows end-to-end by writing and running re-runnable Playwright scripts, capturing screenshot/console/network evidence, and producing structured test reports. Use when a UI change needs real-browser verification, a user flow needs smoke testing, a UI bug needs reproduction, or the user asks to test the site in a browser and report results.
Expert code reviewer providing constructive, prioritized feedback on correctness, security, maintainability, performance, and test coverage — not style preferences. Use when reviewing a diff, branch, or PR for general quality. For a security-only deep audit, use the security-reviewer agent instead.
Expert frontend developer for building and improving web UI — components, state management, responsive layouts, accessibility, and Core Web Vitals performance. Use when implementing UI features or component libraries, fixing layout/responsiveness issues, improving accessibility compliance, or optimizing bundle size and page performance.
Verifies frontend API calls match backend endpoints (URL paths, HTTP methods, request/response types). Use after creating or modifying API endpoints, service functions, or DTOs, or when asked to validate API alignment, check FE-BE contracts, or generate API contract docs.
Detects which architectural layer (frontend or backend) a file or task belongs to and routes to the matching pattern skill. Use when a task spans frontend and backend, or when determining which layer a file belongs to.
Caution protocol for destructive operations. Use before deleting files, dropping database objects, removing exports/public APIs, or running irreversible commands.
Instinct-based learning system that observes sessions via hooks and evolves patterns into skills/commands/agents. Use when the user asks about learned instincts, wants to analyze session patterns, sets up auto-learning or observation hooks, or runs /idev:instinct-status, /idev:instinct-export, /idev:instinct-import, or /idev:evolve.
Scans the codebase to auto-detect backend code conventions (controllers, services, entities, DTOs, DI registration) and caches them. Use when creating or modifying backend code so new files follow existing patterns exactly.
Matches all tools
Hooks run on every tool call, not just specific ones
Modifies files
Hook triggers on file write and edit operations
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.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
A Claude Code plugin packaging 27 skills, 9 agents, 10 commands, and a session-startup hook built around generic-first design: skill logic is universal, project knowledge lives in per-project caches that every skill regenerates by scanning the project it lands in. The scanners are strongest on .NET/React-style projects; other stacks fall back to generic heuristics.
From GitHub (inside Claude Code):
/plugin marketplace add TheophilusChinomona/idev
/plugin install idev@idev
Or test a local checkout:
claude --plugin-dir /path/to/idev
Then, inside each project, scaffold the per-project state:
/idev:idev-init
/idev:idev-init is the one required setup step per project: it creates .claude/idev/ (caches, task journal, lessons file, config templates) and offers to append the operating-guide snippet (templates/claude-md-snippet.md) to the project's CLAUDE.md — the always-loaded routing layer that tells Claude the cache-first context rules, the skill workflow chain, the agent delegation map, and your per-project policies. The SessionStart hook stays completely silent in projects where .claude/idev/ doesn't exist, so nothing happens until you run it.
Two ideas drive everything:
<project>/.claude/idev/ — indexes, pattern caches, journal, lessons, session snapshots. Skills regenerate that state by scanning whatever project they land in, which is what makes the same plugin work across different codebases.Run /idev:idev-init once. It creates .claude/idev/ with the journal, lessons file, rules file, and config templates, offers to append the operating-guide snippet to your CLAUDE.md (how Claude should drive the plugin in this project, plus your tunable policies), and generates the smart-context index (scanner.py detects your stack, features, and conventions). From then on, every session starts with that context injected automatically.
Just describe tasks normally. The skills slot into four phases of the work:
Finding things — instead of reading whole files, Claude consults the caches first: the smart-context index for "which files implement feature X", the file index for fast path lookup, the project map (grepped, never loaded whole) for structure, and the Function Index inside the pattern caches for "where is function Y" without reading the file.
Writing code — architecture-scanner works out which layer a file belongs to; backend-patterns / frontend-patterns scan your codebase once, cache its conventions (file layout, naming, error handling, DI, API client patterns), and make new code follow your style rather than generic style. coding-standards adds security checks when code touches user input, auth, secrets, or queries.
Verifying — after creating files, post-creation-verify checks the wiring (registrations, route tables, DI containers — the stuff that compiles but doesn't run); build-check builds once per logical change set; api-contract-validation cross-checks frontend calls against backend endpoints (paths, methods, DTO shapes) and can emit contract docs; feature-completeness traces a feature end-to-end (UI → service → endpoint → DB) to catch dangling links; self-review runs a final invariant check against your project's cached patterns; test-map knows which tests cover which files so only the relevant ones run; browser-test (+ the browser-tester agent, /idev:browser-test) verifies UI flows with real Playwright runs — every verification script is saved to .claude/idev/browser-tests/scripts/ so the project accumulates an E2E suite as a side effect of normal work.
Remembering — task-journal tracks in-flight work across sessions; session-resume snapshots state so "pick up where we left off" works; lessons-learned logs mistakes-with-fixes so they aren't repeated. The SessionStart hook surfaces all three next time.
Useful things to say:
Set up and manage your OpenClaw self-hosted AI gateway from Claude Code
Crawl websites and extract structured markdown using Crawl4AI — single page, deep BFS, or batch URL list
LinkedIn prospecting pipeline: scrape companies/people, build org-charts, score decision makers
npx claudepluginhub theophiluschinomona/idev --plugin idevHarness-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
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Complete developer toolkit for Claude Code
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.