EGS Engineering Kit

Install & use the EGS Engineering Kit

Shared EGS skills, agents, and rules for Claude Code — one plugin and one MCP server per kit. Install in seconds with a single command — on macOS, Linux, or Windows.

Install

Kits

Operating system

Scope

curl -fsSL "https://acdc.eastgate-software.com/install.sh" | PLUGIN=dev bash
Each teammate runs the installer once in their own checkout. To update to the latest version, just re-run the same command.

Use MCP resources

Each kit serves its guides, reference docs, and EGS templates — including the Word proposal documents, the WBS spreadsheet, and the intro-deck slides — as MCP resources. In the Claude Code CLI, type @ in your prompt to browse them and drop one straight into context — no copy-paste, no file paths to memorise.

Pick a resource and it's pulled into your message before the agent starts — so "What’s our standard tech stack? @…" hands the agent the actual EGS reference to work from, automatically.

CLI only — and that one's on Anthropic, not us. 😅 The @-mention picker for resources currently lives in the Claude Code CLI. Claude Desktop and the VS Code extension happily run each kit's skills, agents, and tools — they just can't @-mention resources yet, because that bit of UI isn't wired into them upstream. The day Anthropic ships it, you'll get it for free.

Uninstall

Remove one kit

Uninstall a single kit's plugin (swap devkit for the kit you want gone):

claude plugin uninstall devkit@egs

Remove everything

Clean up all EGS kits at once — uninstalls every plugin, drops the marketplace, scrubs settings, and clears the on-disk cache:

curl -fsSL "https://acdc.eastgate-software.com/uninstall.sh" | SCOPE=project bash
Add DRY_RUN=1 to preview without changing anything, YES=1 to skip the confirmation prompt, or SCOPE=all to clean every scope at once. On Windows, set these as $env: variables (e.g. $env:DRY_RUN="1").

Release notes

devkit v0.1.0

Initial release of the Development kit — skills, agents (Tech Lead, Solution Architect, engineers, code reviewer), and coding rules, plus its per-kit MCP server.

Workflow skills

  • dev-spec — Generate a technical spec from requirements, with architecture decisions and data models.
  • dev-api-design — Design REST endpoints with an OpenAPI spec and error handling.
  • dev-code-review — Review changes for correctness, security, performance, and conventions.
  • dev-debug — Reproduce, isolate, diagnose the root cause, fix, and verify.
  • dev-migrate — Plan and run database, framework, or technology migrations.
  • dev-refactor — Spot refactoring opportunities and apply SOLID principles.
  • dev-ui-review — Audit UI for accessibility, responsive design, UX, and visual quality.
  • sa-system-design — Design system architecture with C4 diagrams, tech-stack decisions, and NFRs.
  • sa-diagram-redraw — Turn rough diagrams into polished HTML/SVG with real tech icons.

Reference guides

  • guide-engineering-standards — Coding standards, SOLID/DRY, git workflow, and reviews.
  • guide-solution-architecture — C4 model, ADRs, integration mapping, and NFRs.
  • guide-api-design — REST conventions, RFC 7807 errors, OpenAPI, and versioning.
  • guide-tdd — Red-Green-Refactor, the test pyramid, and BDD.
  • guide-security — OAuth2/OIDC, JWT, OWASP Top 10, and secrets.
  • guide-observability — Structured logging, correlation IDs, metrics, and tracing.
  • guide-nfr — Non-functional requirements checklist.
  • guide-microservices — Circuit breakers, saga, API gateway, and contract testing.
  • guide-spring-boot — Spring Boot 3.x / Java 17+ patterns.
  • guide-dotnet — .NET 8+ Clean Architecture with EF Core.
  • guide-python — FastAPI, Pydantic, and pytest.
  • guide-node — Express/Fastify with TypeScript and Prisma.
  • guide-typescript — Strict TypeScript, Zod validation, and type safety.
  • guide-react — React hooks, state management, Tailwind, and testing.
  • guide-ui-ux — Accessibility, responsive layout, and design quality.
  • guide-kafka — Spring Kafka producer/consumer patterns.
  • guide-redis — Caching, sessions, rate limiting, and TTLs.
  • guide-playwright — End-to-end testing with the Page Object Model.
  • guide-ai-engineering — LLM integration, RAG, agents, and MLOps.

Troubleshooting

Symptom Cause & fix
Error: PLUGIN is required The PLUGIN variable was not set. Add PLUGIN=<kit-name> before the pipe.
SCOPE is not set / install cancelled If you don't choose a scope, the installer asks for one in the terminal. When there's no terminal to ask (a CI job or other non-interactive run), it cancels rather than guessing — set the scope explicitly, e.g. SCOPE=project (macOS / Linux) or $env:SCOPE="project" (Windows).
Download fails / 404 The kit name or version doesn't exist. Check the spelling and try without a pinned version to get the latest.
marketplace.json not found Re-run the install command to fix this.
MCP tools don't appear in Claude Restart Claude Code after installing. If tools still don't appear, run claude mcp list to confirm the kit is active.
unzip: command not found (macOS / Linux) Install unzip — e.g. brew install unzip on macOS.
Expand-Archive errors / PowerShell too old (Windows) Update to PowerShell 5.1+ (ships with Windows 10/11). The irm … | iex form runs in memory, so it isn't blocked by the execution policy — no extra step is needed.
Access to the path is denied / install root not writable You're running from a directory you can't write to (e.g. C:Windowssystem32). Open a terminal in your project folder and re-run, or install for your user instead — add $env:SCOPE="user"; (Windows) or SCOPE=user (macOS / Linux).
claude: command not found / not recognized Install Claude Code first (code.claude.com/docs/en/quickstart), then re-run the install command.