Tesseract
A Claude Code plugin marketplace.
In the Marvel universe, the Tesseract was a crystalline container that held the Space Stone — one of the six Infinity Stones, each holding power over a fundamental aspect of existence. Whoever possessed the Tesseract didn't just hold an object; they held the potential to reshape reality itself.
This Tesseract holds something similar. Not Infinity Stones, but plugins — each one a concentrated capability that transforms how you build software. The container is simple. What it holds is powerful.
What's Inside
| Plugin | What It Does |
|---|
| Shield | A unified software development lifecycle plugin — research, planning, project management integration, implementation, and continuous code review with specialist agents |
Deprecated Plugins
The following plugins have been consolidated into Shield and are no longer maintained as separate plugins:
| Plugin | Replaced By |
|---|
infra-review | Shield's domain-specific review skills (terraform/, atmos/, github-actions/) and multi-mode reviewer agents |
clickup-sprint-planner | Shield's PM adapter system (/pm-sync, /pm-status) with the ClickUp adapter at shield/adapters/clickup/ |
dev-workflow | Shield's general skills (/research, /implement, /plan) and superpowers integration |
If you have existing projects using these plugins (e.g., infra-plans/ directories with sprint-planner.json), run /shield init in your project to migrate. Shield detects old plugin config and offers to set up the new .shield.json marker and ~/.shield/ config structure.
Tesseract: The Marketplace
Tesseract is a plugin marketplace — a registry that contains one or more Claude Code plugins. You add the marketplace once, then install whichever plugins you need.
# Add the marketplace (one-time)
/plugin marketplace add infraspecdev/tesseract
# Install a plugin from it
/plugin install shield@tesseract
# Enable auto-updates to stay current
/plugin update --auto-update shield@tesseract
Each plugin in the marketplace is independently versioned and released. You can install one, some, or all of them.
Plugins
Shield
Named after Marvel's S.H.I.E.L.D. — the Strategic Homeland Intervention, Enforcement and Logistics Division — the organization that gathers intelligence, plans operations, assembles specialists, and executes missions.
Except here, the homeland is your codebase — and the existential threats are unreviewed pull requests, missing test coverage, security holes hiding in plain sight, and acceptance criteria so vague they'd make Nick Fury weep.
Shield assembles a team of specialist agents and orchestrates them through a structured engineering pipeline. A planner who breaks initiatives into executable stories with testable acceptance criteria. A security reviewer who thinks like an attacker. A cost analyst who's seen $10k/month NAT gateway bills in dev environments. An architect who's debugged cascading failures at 3 AM. An agile coach who ensures stories are sprint-ready. A developer experience engineer who ensures plans are clear enough to execute without questions.
It shields you from the mistakes that haunt on-call rotations — because the best incident is the one that never happened.
Design Philosophy
One pipeline, many domains. Shield follows a single workflow — research, plan, build, review — but adapts to the domain you're working in. Terraform gets provider-specific research and HashiCorp Configuration Language-aware review. Atmos gets stack hygiene checks. Future domains (Python, TypeScript, Kubernetes) slot in by adding a directory, not by rewriting orchestration.
Continuous review, not gatekeeping. Review isn't a phase at the end — it happens after planning (are the stories actionable?), after each implementation step (did we introduce issues?), and as a final consolidated check. You choose which findings to fix, which to defer, and which to discuss.
Project management as a pluggable adapter. The pipeline doesn't know about ClickUp or Jira. It knows about abstract operations — sync stories, get status, link to epic. Each project management tool implements these operations through its own adapter. Adding a new tool means writing an adapter, not touching any skill or agent.
Agents are specialists. Each agent has a clear domain (security, cost, architecture, operations) and operates in modes depending on context — lightweight checks when reviewing a plan document, deep checklists when reviewing Terraform code. One agent file, multiple depths.
Your config, your rules. The plugin adapts to your setup:
- Pick your domains (
terraform, atmos, or both)
- Pick your project management tool per project (
clickup, jira, or future adapters)
- Override which reviewers always run or never run per project
infraspecdev