Architect Playbook vs io.github.giancarloerra/socraticode
Architect Playbook is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Architect Playbook is a plugin bundle for AI coding tools published by Ben Sheridan-Edwards. No marketplace we read lists it any more. io.github.giancarloerra/socraticode is an MCP server published by giancarloerra. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.giancarloerra/socraticode | |
|---|---|---|
| Community marketplace bensheridanedwards/architectplaybook | Removed on 2026-10-18 Version: not stated Forks (GitHub): 5 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.16.1 Downloads/month (npm): 19 713 Downloads/week (npm): 2 291 Forks (GitHub): 432 Stars (GitHub): 3 342 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.11.0 Forks (GitHub): 432 Stars (GitHub): 3 342 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Architect Playbookno longer listed · | io.github.giancarloerra/socraticode |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 3 | 3 342 |
| Forks (GitHub) (differs) | 5 | 432 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (socraticode) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 6 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | 20 | 5 |
| Licence (differs) | MIT | AGPL-3.0-only |
| Repository (differs) | github.com/bensheridanedwards/architectplaybook | github.com/giancarloerra/socraticode |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Architect Playbook
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Plugin description Code quality review plugin based on Frontend Fundamentals 4 principles (readability, predictability, cohesion, coupling). Supports React and Angular with…
-
AI-powered architectural review and code quality analysis
-
Drop this plugin into any project and ask Claude to "review my architecture." It scans for clean architecture violations, SOLID breaches, code smells, and structural anti-patterns…
-
Produces a thorough, evidence-based software quality assessment of any git repository. Grades 16 dimensions — architecture, security, database design, observability, testing…
-
Multi-agent iterative code review until zero issues remain. Spawns up to 10 specialist reviewers (code quality, security, performance, test coverage, architecture, database, API…
-
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
What each says it does
Architect Playbook
Opinionated, evidence-verified audits of TypeScript and React codebases: architecture, testing, security, dependencies, quality gates, and more, with a Repository Quality Score.
io.github.giancarloerra/socraticode
MCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.
How to run each
Architect Playbook
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.giancarloerra/socraticode As a local MCP server: npm package
claude mcp add --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --env "LITELLM_API_KEY=<YOUR_LITELLM_API_KEY>" --env "LMSTUDIO_API_KEY=<YOUR_LMSTUDIO_API_KEY>" --env "OLLAMA_API_KEY=<YOUR_OLLAMA_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "QDRANT_API_KEY=<YOUR_QDRANT_API_KEY>" --transport stdio socraticode -- npx -y socraticodeRequires: GOOGLE_API_KEY (secret), LITELLM_API_KEY (secret), LMSTUDIO_API_KEY (secret), OLLAMA_API_KEY (secret), OPENAI_API_KEY (secret), QDRANT_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Architect Playbook publish no settings it asks for, so we do not compare settings.
What it can do: Architect Playbook · What it can do: io.github.giancarloerra/socraticode · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.