By GxFn
Local-first project memory, Recipes, Guard checks, and recoverable bootstrap jobs.
Submit new Alembic knowledge candidates from Codex when the user explicitly asks, or proactively only when the current project has a project-level Alembic knowledge skill or local Alembic knowledge base. Covers `alembic_submit_knowledge`, V3 fields, batch rules, and review boundaries.
Check code against Alembic Recipe standards with `alembic_code_guard` and explicit files, inline code, or a current workRef with scoped files when the current project has Alembic knowledge.
Use Alembic Recipes proactively only when the current project has a project-level Alembic knowledge skill or local Alembic knowledge base. For empty projects, use only when the user explicitly asks for Alembic Recipes or setup/status.
Discover Alembic project structure, ProjectContext graph orientation, and bounded project-internal relations when the current project has Alembic knowledge. For empty projects, use on explicit Alembic structure requests.
Use Alembic setup/status/diagnostics/bootstrap/rescan when the user explicitly asks for Alembic. When the current project has a project-level Alembic knowledge skill or local Alembic knowledge base, use the agent-facing intent, prime, work, Guard, and decision tools proactively. For empty projects, do not proactively prime unless the user explicitly asks for Alembic.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This repository is the Claude Code distribution shell for the Alembic
plugin. Its sibling, AlembicCodex,
is the Codex distribution shell. Each shell owns exactly one host
(per-host shells, user decision 2026-06-12); the actual runtime is the
pinned npm package @gxfn/[email protected], bootstrapped by
bin/alembic-start.mjs.
.claude-plugin/plugin.json — plugin manifest. MCP server is declared
inline in spec form (${CLAUDE_PLUGIN_ROOT} paths) because Claude Code
copies installed plugins into its cache and spawns MCP servers from the
session cwd, so relative paths do not resolve.skills/ — five skills (alembic, alembic-create, alembic-guard,
alembic-recipes, alembic-structure), auto-discovered at the plugin
root and namespaced as alembic:<skill>.bin/alembic-start.mjs — runtime bootstrap: ensures the pinned
npm runtime in a writable cache, then execs the MCP server over stdio.This repo doubles as its own marketplace (.claude-plugin/marketplace.json
at the repo root, the spec-default hosting shape; the plugin entry uses the
github source type pointing back at this repo):
claude plugin marketplace add GxFn/AlembicClaudeCode
claude plugin install alembic@gxfn
Alternatives considered and not used: a relative "./" self-source (works
only for git-cloned marketplace adds and makes the cache copy carry the
marketplace file ambiguity) and a separate catalog repo (an extra repo to
maintain for a single plugin). Revisit when more plugins join the catalog.
Claude Code negative-caches a failed MCP start in
<config>/mcp-needs-auth-cache.json and silently skips the server on later
sessions. If the very first connect failed (for example the pinned runtime was
not yet reachable), clear that negative cache once after the cause is fixed —
either run /mcp and choose Reconnect for the alembic server, or delete
mcp-needs-auth-cache.json under your Claude Code config directory and start a
new session. The runtime is pinned to an exact version
(@gxfn/[email protected]); reconnecting reuses the same pin.
claude --plugin-dir /path/to/this/repo
claude plugin validate . --strict passes on this tree.
Initial content is a byte-identical copy of the CC1-verified shell state
(AlembicCodex commit 05802b1): validate --strict PASS, live
scratch-profile load with 5 skills registered, stdio MCP connected, and a
26-tool surface matching the certification matrix. See
PLUGIN-SOURCE.json for the cross-shell sync rule and the recorded
host-wording debt (names/keywords/skill bodies still say "Codex";
renaming is owned by later CC2/CC3 waves). The marketplace catalog
(.claude-plugin/marketplace.json) is deliberately absent — that
decision belongs to the CC2 distribution sub-wave.
npx claudepluginhub gxfn/alembicclaudecode --plugin alembicUnattended control loops for multi-window agent work: controller state roots, task packages, direct-session delivery, evidence review, and Design/Test intake for Claude Code desktop and terminal.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls