By Tamircohen28
16 bundled skills, smart worktree hooks, statusline, and MCP server stubs — plan, implement, review, debug, and audit code from one plugin.
Use when the user wants to create generative art, algorithmic art, creative coding, or code-driven visuals — including flow fields, particle systems, noise-based art, Lissajous figures, recursive trees, Voronoi patterns, L-systems, fractals, or any interactive p5.js sketch. Trigger phrases: 'generative art', 'algorithmic art', 'flow field', 'particle system', 'make art with code', 'creative coding', 'p5.js sketch', 'procedural art', 'noise art', 'make something visual with code', 'code art'.
Use when the user pastes a stack trace, traceback, panic, crash log, or error message WITH a file:line reference and wants to know the root cause. Triggers on: 'debug this error', 'look at this stack trace', 'why does X crash', 'what causes this exception', 'why is this panicking', 'look at this file:line', error types (NullPointerException, AttributeError, TypeError, nil pointer dereference, unwrap on None, index out of bounds, segfault, unbound variable, cannot read properties of undefined). Does NOT trigger on vague 'something is broken' or 'why is it slow' without a concrete error signal.
Use when the user wants to convert an informal task, feature request, spec, or review doc into a structured implementation plan before any code is written. User's intent is organization and sequencing — phases, dependency ordering, and GitHub issues that make work trackable and reviewable. Invoke for: 'plan this', 'break into phases', 'create issues for', 'decompose this spec', 'turn into tickets', 'what order should I tackle these', 'help me organize this work', 'structure this feature', 'plan-dev'. This is distinct from architecture analysis of existing code, how-to questions, or direct coding requests — the output is a roadmap, not code.
Use when the user wants to make a plugin, extension, or tool repo compatible with one or more AI coding assistants — Claude Code, Cursor, or OpenAI Codex. Triggers: 'make this compatible with Claude and Cursor', 'add Codex support', 'port this plugin to Cursor', 'make this work with all AI assistants', 'add AGENTS.md', 'add cursor rules', 'generate .cursor/rules', 'add claude code plugin files', 'plugin compatibility', 'multi-platform AI support', 'set up for Claude Cursor and Codex'.
Use when the user wants to actively drive a PR to completion — 'finish this PR', 'address review comments', 'ship/land/close the PR', 'drive PR #N to merge', 'fix CI and merge', 'clean up this PR'. Persistently loops: addresses all review threads, fixes branch-related CI, retries flakes (max 3×), and stops only when ready (asks for `approved`) or blocked (asks for help).
Admin access level
Server config contains admin-level keywords
Executes bash commands
Hook triggers when Bash tool is used
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.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
A personal Claude Code plugin that bundles 17 skills, smart worktree hooks, and MCP server stubs — installed with a single /plugin install command and kept current via marketplace auto-update.
plugin.json so superpowers and other required plugins resolve and install automaticallyjq (for hooks): brew install jqgit 2.30+ (for worktree hooks)gh CLI (for pr-dev, plan-dev, start-dev skills): brew install ghThis plugin is published through the tamirs-plugins
catalog — install it from there, not by adding this repo as a marketplace
(this repo no longer ships its own marketplace.json).
# 1. Add Tamir's plugin marketplace (one-time per machine)
/plugin marketplace add Tamircohen28/plugins
# 2. Install — the `superpowers` dependency auto-installs alongside
/plugin install tamirs-superpowers@tamirs-plugins
# 3. Verify
/doctor
claude CLI)claude plugin marketplace add Tamircohen28/plugins
claude plugin install tamirs-superpowers@tamirs-plugins
claude plugin list # confirm it's installed
Restart any running Claude Code session afterward so the hooks, statusline, and
MCP stubs load. The bundled MCP servers (github, context7) are wired in
.mcp.json and start automatically — the github server derives its token from
your gh CLI auth (gh auth login), so there are no env vars to set by hand.
Statusline not showing? If the footer statusline doesn't appear after restart, add it manually: run
/configin Claude Code and setstatusLine, or add it directly to~/.claude/settings.json:{ "statusLine": { "type": "command", "command": "bash ~/.claude/plugins/cache/tamirs-plugins/tamirs-superpowers/<version>/statusline.sh" } }
Each skill lives at skills/<skill-name>/SKILL.md.
| Skill | What it does |
|---|---|
/tamirs-superpowers:plan-dev | Plan work into phases and create GitHub issues. |
/tamirs-superpowers:start-dev | Create worktree, implement, validate, push, and open a PR. |
/tamirs-superpowers:pr-dev | Drive a PR to merge — address review threads, fix CI, squash-merge after explicit approval. |
/tamirs-superpowers:plugin-compat | Make a repo compatible with Claude Code, Cursor, and OpenAI Codex — fetches latest platform docs and generates all required config files. |
/tamirs-superpowers:targeted-debug | Scope-bounded debug from a stack trace — reads only named files. |
/tamirs-superpowers:repo-polish | Scan a project for employer IP, scaffold repo infra, publish to GitHub. |
/tamirs-superpowers:repo-scaffold | Create a new private GitHub repo from scratch — README badges, docs, CLAUDE.md, .claude/ config, CI/CD, branch protection, and project skills. |
/tamirs-superpowers:mcp-builder | Build MCP servers (auto-invokes mcp-pagination for list/search tools). |
/tamirs-superpowers:find-skill | Search skill marketplaces and rank matches for a query. |
/tamirs-superpowers:skill-creator | Create, improve, and benchmark Claude Code skills. |
/tamirs-superpowers:session-report | Generate an HTML report of session token usage. |
/tamirs-superpowers:algorithmic-art | Generate algorithmic art with p5.js. |
/tamirs-superpowers:dark-terminal-doc | Generate polished HTML docs with a dark terminal design system. |
npx claudepluginhub tamircohen28/plugins --plugin tamirs-superpowersJob search CRM with pipeline, interviews, tasks, and Gmail/Calendar/Notion/Todoist integrations.
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
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
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.
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,561 supported skills.