Backend Plugin Architecture

Use when the user asks about a plugin system, extension points, SPI, plugin loader, hot-plug or dynamic loading, plugin sandboxing or plugin manifests. Produces a plugin host design with lifecycle and isolation. Not for micro-frontends (use microfrontend).

45 stars 6 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill backend-plugin-architecture
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/plugin-architecture ~/.claude/skills/backend-plugin-architecture

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Backend Plugin Architecture

## Purpose
Design extensible backend systems where third-party code (plugins) can be loaded dynamically at runtime through well-defined extension points and service provider interfaces (SPI). A plugin architecture enables the host application to be extended without modifying its core code.

## Agent Protocol

### Trigger
Exact user phrases: "plugin system", "plugin architecture", "extension point", "SPI", "service provider interface", "hot-plug", "modular design", "plugin loader", "extensible", "plugin API", "custom extension", "plug-in", "dynamic loading".

### Input Context
- What the host application does and where extensibility is needed.
- Language/runtime (supports dynamic loading?).
- Security requirements for plugin isolation.

### Output Artifact
Plugin system design or implementation code. No file unless requested.

### Response Format
```
Extension Point: {name}
SPI: {interface/contract}
Loading: {dynamic|compile-time|classpath}
Isolation: {classloader|process|container}
```

### Completion Criteria
- [ ] Extension points defined and documented.
- [ ] SPI interface created for each extension point.
- [ ] Plugin loader implemented.
- [ ] Plugin lifecycle (load, init, start, stop, destroy) managed.
- [ ] Isolation and security boundaries established.

### Max Response Length
3 lines per extension point. 20 lines for full system.

## Architecture Decision Tree

### Should I Build a Plugin System?
Read the full skill on GitHub

Details

Skill name
backend-plugin-architecture
Path
skills/backend/universal/plugin-architecture/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Backend Plugin Architecture skill do?

Use when the user asks about a plugin system, extension points, SPI, plugin loader, hot-plug or dynamic loading, plugin sandboxing or plugin manifests. Produces a plugin host design with lifecycle and isolation. Not for micro-frontends (use microfrontend).

How do I install the Backend Plugin Architecture skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-plugin-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Backend Plugin Architecture popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Backend Report Generation

45

j4flmao/agent-skills

Use when the user asks about PDF report generation, Puppeteer or Playwright PDFs, Excel/CSV export, async report jobs, scheduled reports or exporting large datasets. Produces a report pipeline with templates, queued generation and delivery. Not for live dashboards (use data-bi-tools) or bulk import (use backend-bulk-import).

Software Development

Backend Multi Tenancy

45

j4flmao/agent-skills

Use when the user asks about multi-tenancy, SaaS where each customer must only see their own data, tenant isolation, row-level security, schema or database per tenant, tenant context or tenant provisioning. Produces an isolation model with enforcement code. Not for Supabase RLS specifics (use supabase).

Software Development

Backend Resilience Patterns

45

j4flmao/agent-skills

Use when the user asks about a circuit breaker around a flaky service, retries with backoff and jitter, timeouts, bulkheads, fallbacks, Resilience4j or Polly. Produces fault-tolerance config and code per dependency. Not for API request throttling (use rate-limiting).

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.