A Claude Code plugin that automates a multi-agent software development pipeline from feature spec to reviewed PR.

Command-line tools for working with Architecture Decision Records

✍️ Architecture Decision Records (ADR) management and publication tool

🦀 Agentic RAG for drug intelligence · 57 skills · 15 task categories · DTI · ADR · DDI · PGx · Repurposing · Powered by LangGraph

A community plugin marketplace providing workflow skills and slash commands for Gajae Code, compatible with Claude Code and Codex.

ADR-driven documentation workflow skill for AI coding agents to scaffold and manage Architecture Decision Records.

Curated collection of AI agent skills for Hermes and other agent frameworks

Documentation maintenance rules — which docs map to which code areas, the thin-pointer/no-drift rule, and the graphify-update step. Owned by project-steward. Load for /update-docs and the docs-sync step of the implement-workflow.

DORMANT (ADR-0017, 2026-07-20) - the TERMINAL VELOCITY scroll-film was retired and apps/landing is a static site with no GL surface; this skill is preserved for any future WebGL rebuild (conventions, verified version pins, playhead/scroll-rig/VAT/Gerstner/post-chain patterns, budgets, gate + semantic-layer machinery). Do not load for current apps/landing work - the static site routes to project-steward.

Use when the user wants to write, draft, or author an RFC (Request for Comments) / technical design doc for a feature, change, or architectural decision. Interactively interviews the user, grounds the proposal in the actual codebase, presents 2-3 concrete API/code-snippet approaches to choose from, then writes a review-ready RFC. Triggers on "write an RFC", "draft an RFC", "RFC for X", "design doc for X", or /rfc.

Writes an Architecture Decision Record (ADR) documenting a decision, its context, the options considered, and its consequences. Use to record a decision that's already been made so future readers understand why.

Architectural governance for this project. Use this skill when the user asks about project decisions, architectural constraints, or wants to enforce / record / review decisions. Also use whenever Claude Code is about to make a non-trivial edit and the project has a `.mneme/` directory — check relevant decisions first.