Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By xobotyi
Structured planning pipeline: discovery, design documents, technical designs, task decomposition, task creation, and technical diagramming
npx claudepluginhub xobotyi/cc-foundry --plugin the-blueprintTechnical design documents — problem analysis, solution exploration, architectural decisions. Invoke whenever task involves any interaction with design documents — creating, updating, reviewing, comparing options, or capturing architectural decisions.
Technical diagram creation with visual design principles: format selection, layout, readability, and aesthetics. Invoke whenever task involves any interaction with diagrams — creating, reviewing, or improving visual representations of systems, processes, data flows, or relationships using Excalidraw or Mermaid.
Adversarial requirements elicitation — stress-test ideas through systematic questioning before committing to design. Invoke whenever task involves priming understanding of a problem, feature, or idea before design work — exploring requirements, "grill me", "let's think this through", or starting the blueprint pipeline.
Task creation for issue trackers — structured descriptions, acceptance criteria, field categorization, and tracker linking. Invoke whenever task involves creating work items in any issue tracker — bugs, features, stories, tasks, or any tracked work from standalone requests or decomposition documents.
Convert technical designs into actionable, tracked task hierarchies with sizing, dependencies, and acceptance criteria. Invoke whenever task involves any interaction with work decomposition — breaking down features into subtasks, slicing work items, creating task lists, or writing decomposition documents.
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.
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation
Focused agentic engineering workflow: design-doc, spec, plan, implement, tdd, refactor, review, address-pr-feedback, browser-verify, explain-visually, compress, branch, and commit.
Blueprint-driven Claude Code autopilot. Smart preparation over endless iterations - AI analyzes patterns, creates solid implementation plans, delivers working code in 15 minutes.
AI artifact engineering: prompts, skills, subagents, and output styles
Blueprint Development methodology - structured feature development with PRD/PRP workflow, three-layer architecture (plugin/generated/custom), and documentation-first development
Workflow skills and shared instructions for coding agents.
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