Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By xobotyi
Backend platform discipline: observability, API design, and service architecture practices
npx claudepluginhub xobotyi/cc-foundry --plugin backendObservability discipline: structured logging, metrics instrumentation, distributed tracing, and signal correlation. Invoke whenever task involves any interaction with observability concerns — adding logging, designing metrics, instrumenting traces, correlating signals, reviewing instrumentation, or understanding when to use which pillar.
OpenTelemetry tracing discipline: correct spans, propagation, and semantic conventions produce useful traces. Invoke whenever task involves any interaction with distributed tracing — span creation, context propagation, instrumentation, sampling configuration, or OpenTelemetry SDK setup.
Prometheus instrumentation discipline: right metric type, right name, right labels. Invoke whenever task involves any interaction with Prometheus metrics — instrumenting application code, writing PromQL queries, defining alerting or recording rules, choosing metric types, managing label cardinality, building exporters, or reviewing monitoring configuration.
StatsD metric instrumentation: push metrics over UDP, choose the right metric type, name consistently. Invoke whenever task involves any interaction with StatsD metrics — emitting counters, gauges, timers, histograms, sets, or distributions; configuring DogStatsD tags; tuning sampling rates; or integrating with Graphite, Prometheus, or Telegraf backends.
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.
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n<example>\nContext: Designing a new API\nuser: "We need an API for our social sharing feature"\nassistant: "I'll design a RESTful API with proper authentication and rate limiting. Let me use the backend-architect agent to create a scalable backend architecture."\n<commentary>\nAPI design requires careful consideration of security, scalability, and maintainability.\n</commentary>\n</example>\n\n<example>\nContext: Database design and optimization\nuser: "Our queries are getting slow as we scale"\nassistant: "Database performance is critical at scale. I'll use the backend-architect agent to optimize queries and implement proper indexing strategies."\n<commentary>\nDatabase optimization requires deep understanding of query patterns and indexing strategies.\n</commentary>\n</example>\n\n<example>\nContext: Implementing authentication system\nuser: "Add OAuth2 login with Google and GitHub"\nassistant: "I'll implement secure OAuth2 authentication. Let me use the backend-architect agent to ensure proper token handling and security measures."\n<commentary>\nAuthentication systems require careful security considerations and proper implementation.\n</commentary>\n</example>
Agents specialized in backend development, API design, and system architecture. Focuses on scalable server-side solutions and data management.
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Analyze Claude Code agent session transcripts to identify inefficiencies, anti-patterns, repeated mistakes, missing tooling opportunities, and user frustration signals for continuous improvement
Software engineering discipline: output styles, coding fundamentals, and universal development practices
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Infrastructure management discipline: Ansible automation, container orchestration, Proxmox virtualization, Unraid NAS, and network architecture
Open-source contribution discipline: issue writing, pull request creation, and contribution etiquette
PHP language discipline: conventions, modern idioms, type system, OOP, and testing
Git commit workflow: atomic commits, validation, conventions
Python language discipline: conventions, modern idioms, type system, packaging, testing, and LSP-powered code intelligence
Plugins that make Claude Code better at its job.
Claude Code is powerful out of the box, but it has gaps. It forgets skills mid-session. Commits are messy. Building AI artifacts is trial-and-error. Code ships without validation. These plugins fix that.
Add the marketplace, then install any plugin:
/plugin marketplace add xobotyi/cc-foundry
/plugin install <plugin-name>
Claude skips skills and forgets about them mid-session. This plugin injects a Skill Enforcement Framework via lifecycle hooks that forces Claude to evaluate which skills apply at every checkpoint: user prompt, after reading files, after editing, and after loading skills. Skills are treated as non-atomic — phase shifts (coding to testing) trigger re-evaluation of unread references from already-loaded skills.
/plugin install skill-enforcer
Messy commits — mixed changes, vague messages, wrong order. The /commit command enforces an 8-step pipeline: identify
logical units in the diff, plan commit order (style to refactor to fix to feature), run quality gates, self-review,
stage selectively, validate messages against conventions, commit, and verify. Each message runs through automated
validation before execution.
/plugin install git-commit
Planning is either too shallow or too detailed. This plugin provides a four-stage pipeline that produces artifacts consumable by both humans and agents: design documents (problem analysis and recommendation), technical designs (component mapping and sequencing), task decomposition (actionable hierarchies with acceptance criteria), and task creation (issue tracker items). Each stage builds on the previous with explicit approval gates.
/plugin install the-blueprint
Claude writes code before understanding what exists — guessing APIs, skipping tests, multiplying abstractions. This
plugin provides a coding skill that enforces a discovery-first workflow (Discover, Plan, Implement, Verify) and a
software-engineer output style with LSP-first navigation and engineering judgment. Runs before language-specific
skills as a prerequisite.
/plugin install the-coder
Code quality is checked manually or not at all. This plugin provides a two-level validation pipeline:
quality-validation checks that deliverables match the original request before completion, and
code-quality-evaluation orchestrates 8 specialized review agents (naming, complexity, comments, tests, error handling,
security, observability, documentation) that evaluate code in parallel. All agents are read-only — they report, you
decide.
/plugin install the-crucible
No visibility into context window usage, cost, or model. This plugin installs a 3-row status line to your user-level Claude configuration showing output style, model, session cost, context window remaining, cache hit rate, and current working directory. Color urgency increases as context approaches limits. Auto-syncs on every session start and survives agent directory changes.
/plugin install the-statusline
Agentic workflow mechanics — the foundational skills that make working with Claude Code effective across sessions and
teams. The claude-md skill applies prompt engineering principles to CLAUDE.md files: what belongs where, writing
instructions Claude actually follows, diagnosing why rules get ignored (buried, vague, stale, contradictory), and
systematic improvement. The handoff skill produces structured transfer documents when work crosses context boundaries
— session restarts, teammate delegation, async resumption — preserving decisions, constraints, and remaining work in
500-2000 tokens while dropping noise.
/plugin install the-workflow
Creating prompts, skills, agents, and output styles is guesswork without structured guidance. This plugin provides
skills encoding best practices for each artifact type: prompt-engineering (foundation), skill-engineering,
subagent-engineering, output-style-engineering, and claude-code-sdk (reference). All skills build on
prompt-engineering fundamentals. Includes an ai-engineer output style for collaborative artifact work.
/plugin install ai-helpers
Go has strong idioms that differ from other languages — premature abstraction, incorrect error handling, interface
misuse, and concurrency bugs are common pitfalls. This plugin provides a golang skill covering conventions, error
handling, interfaces, concurrency, testing, and project structure, plus a templ skill for type-safe HTML templating
with component composition, attribute handling, and JS integration.
/plugin install golang