Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By popmechanic
Build applications where Claude Code CLI (claude -p) is the runtime — a server spawns Claude processes that read files, run commands, and return structured output, while a custom interface renders the results.
npx claudepluginhub popmechanic/loomUse when building a native desktop application that needs Claude Code CLI (`claude -p`) as its runtime, using ElectroBun (Bun + system webview). The Bun process spawns Claude directly via typed RPC — no HTTP server, no auth, no SSE formatting. Triggers: "desktop app with Claude", "native Claude tool", "ElectroBun Claude app", "local AI agent", "Claude on the dock", or any desktop application needing Claude's agentic capabilities through a native interface. NOT for web apps (use loom), direct Anthropic API, or chat replicas.
Use when building a local web application that needs Claude Code CLI (`claude -p`) as its runtime, using Bun as the server layer. The Bun server spawns Claude processes and streams results to the browser — no authentication, no deployment, no multi-tenancy. Triggers: "local Claude app", "Bun server with Claude", "claude -p web app", "local Claude-powered tool", "build a local app that uses Claude", or any local web app needing Claude's agentic capabilities through a browser interface. NOT for deployed/multi-user apps (use loom), desktop apps (use loom-desktop), or direct Anthropic API usage.
Use when building a web application that needs Claude Code CLI (`claude -p`) or the Agent SDK as its backend runtime — a server that spawns Claude processes to power a custom browser interface. Triggers: "build an app that uses Claude", "Claude as backend/runtime", "Claude-powered web app", "wrap claude -p in a server", "streaming Claude output to browser", or any web app needing Claude's agentic capabilities through a purpose-built interface. NOT for direct Anthropic API usage, simple chat replicas, or desktop apps (use loom-desktop).
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.
Interactive plugin builder for Claude Code - serves as both an example plugin and a tool to create new plugins through guided prompts with specialized builder skills for each component type
LLM application development with RAG, embeddings, LangChain, and prompt engineering
High-intelligence Claude Code copilot with deep code reasoning, evidence-driven planning, orchestration-first execution, model routing, context budgeting, CI/CD integration, enterprise security, plugin development, prompt engineering, performance profiling, agent teams, channels (event-driven autonomy with CI webhook, mobile approval relay, Discord bridge, and fakechat dev profile), interactive tutorials, LSP integration, security-hardened hook script library, MCP Prompts coverage, common workflow packs, runtime selection guide, computer-use patterns, checkpointing, scheduled-task blueprints, repo bootstrap scanner, hook policy engine (8 installable packs), layered memory deployment, role-based subagent packs (implementer, debugger, migration-lead, dependency-auditor, release-coordinator), 5 agent-team topology kits, autonomy operating mode (4 profiles + 3 gates), and a queryable 15-tool MCP documentation server with autonomy advisor.
CLI tool for running Claude Code SDK sessions with configurable modes
Real-time statusline HUD for Claude Code - displays context usage, tool activity, agent tracking, and todo progress
Expert Prompt Engineer with Context Engineering, Meta-Prompting, Chain-of-Thought, Few-Shot, Agent Design, 50+ Template Library, and A/B Testing
Julian project tools — deploy, manage, and interact with Julian instances
Vibes is for people who use Claude Code, but don't know how to code.
Autonomous, parallel, worktree-isolated execution of Superpowers plans via a committed Dynamic Workflow. Pairs with superpowers; invoke as /ultrapowers <plan-path> instead of subagent-driven-development.
Knowledge base + agent toolkit for Skylights NW operations. Voice-driven interviews, compiled wiki, Q&A CLI, lint/health checks, and Cowork-ready subagents.
A Claude Code plugin for building applications where claude -p is the runtime.
Claude Code is usually an interface — you talk to it, it writes code. But claude -p is something more general: a process with access to the filesystem, the shell, and a broad set of tools, capable of returning structured output conforming to any schema you define. It's an engine you can embed inside an application of your own design.
Loom teaches Claude how to build on top of that engine. The architecture is simple. A server spawns a claude -p process with a prompt and a JSON schema, then streams events to a frontend via SSE. What the prompt asks, what shape the schema gives, and how the interface renders it — those are yours to decide.
This is the shift from Claude Code as a coding interface to Claude Code as a runtime. You inherit everything Anthropic built into that harness — tool use, context management, streaming, model selection, cost controls — and point it at whatever you want to make.
[Interface] ←→ [Server] ←→ [claude -p]
↕
[filesystem, shell, tools]
Three decisions define each app:
The server is a thin relay. Claude does the work. Your interface gives it form.
For a deeper walkthrough of the architecture, patterns, and design decisions, open the interactive explainer.
Either:
/install-plugin popmechanic/loom
or:
/plugin install loom