architect-playbook

Plugin architect-playbook from marketplace architect-playbook in BenSheridanEdwards/ArchitectPlaybook. Commands read from the repo's manifest — 4 days ago.

Skills (30)

• pull-request-quality-contract

  Use before completing work or opening a pull request in this repository.

• gitnexus-cli

  Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\"

• gitnexus-debugging

  Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"

• gitnexus-exploring

  Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"

• gitnexus-guide

  Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"

• gitnexus-impact-analysis

  Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"

• gitnexus-refactoring

  Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"

• install-architect-playbook-globally

  Copy every architect-playbook skill into ~/.claude/skills/ so the slash commands are available in every Claude Code session on this machine.

• accessibility-audit

  Audit a TypeScript/React frontend against an opinionated WCAG 2.2 AA baseline (tooling, component patterns, application shell) with optional implementation plan.

• agentic-audit

  Audit a project's agentic instruction files (CLAUDE.md, AGENTS.md, .cursor/rules, .cursorrules, .github/copilot-instructions.md, Windsurf, Aider) and Claude Code settings (.claude/settings.json, .claude/settings.local.json) against an opinionated baseline covering project context coverage, operation

• architecture-audit

  Audit a TypeScript codebase's structure — import cycles and boundaries, module depth, change hotspots, and data-flow ownership — with verified evidence, then run a design session on the candidate you choose.

• audit-protocol

  Shared run protocol, scripts, and reporting rules that every Architect Playbook audit follows. Audits load it by path; it is not run on its own.

• ben-architect-review

  Perform a principles-based architectural pull request review using Ben's judgement, then ask whether to post it as pending or submit it on GitHub.

• bundle-build-audit

  Audit build pipeline and bundle output (static-first with optional --with-stats enrichment). Checks configuration, composition, hygiene, and performance with optional implementation plan.

• clear-thinking

  Think a piece of writing through before drafting it, then write and edit it so a busy reader can understand and act on it at once.

• dependency-audit

  Audit Node.js dependency tree (security, health, compliance, hygiene). Static-first with optional --with-network enrichment for vulnerabilities, outdated, and abandonment data. Optionally generates an implementation plan.

• documentation-audit

  Audit project documentation against an opinionated baseline spanning onboarding, architectural/decision docs, code-level docs, and operational documentation with drift detection. Static-first with optional --with-link-check. Optionally generates an implementation plan for the gaps.

• error-handling-audit

  Audit a TypeScript codebase's error-handling discipline against an opinionated baseline spanning throw and catch hygiene, async and network error handling, React error boundaries, and logging and observability. Static-only by design. Optionally generates an implementation plan for the gaps.

• install-architect-playbook-locally

  Copy every architect-playbook skill into the current project's .claude/skills/ directory so the slash commands are available inside this project only.

• linting-audit

  Audit a TypeScript project's lint configuration against an opinionated baseline spanning configuration shape, rule coverage, strictness and enforcement, and suppressions hygiene. Auto-detects ESLint or Biome. Static-first with optional --with-run enrichment. Optionally generates an implementation pl

• performance-audit

  Audit runtime performance patterns in a TypeScript/React frontend (render, network/data, assets/CWV, main-thread). Static-first with optional --with-lighthouse-results enrichment and implementation plan.

• pre-audit-setup

  One-time, idempotent preparation before audits. Verifies graphify is installed and builds the project knowledge graph that audits read for orientation, without changing settings or tracked files.

• preflight

  Detect optional enrichment tooling for architect-playbook audits and optionally install missing development dependencies and scaffold project configuration. Read-only by default; mutation is gated behind --install and --scaffold-configs and prompts before every change.

• quality-gates-audit

  Audit pre-commit, pre-push, and CI/CD quality gates against an opinionated baseline. Reports present/partial/missing/violation gates and optionally generates an implementation plan.

• react-audit

  Audit React correctness for the React 19 and compiler era — effects that should not exist or leak, duplicated and boolean state, server-client boundary leaks, and hooks lint, toolchain, and export facts from a deterministic collector.

• repository-quality-score

  Calculate an explainable Repository Quality Score from Architect Playbook audit outputs. Use after audits finish, whenever a user asks for a repository score, audit roll-up, quality summary, category comparison, or assessment coverage.

• security-audit

  Audit a TypeScript, React, or Next.js codebase for exploitable weaknesses — server access control, injection and unsafe output, secrets and browser hardening, and large-language-model features — tracing each finding from an attacker's entry point.

• system-self-improve

  The meta-improvement layer of the architect-playbook. Reads a review's gap report (or a user-supplied gap, or audit-history patterns), locates the affected SKILL.md and adjacent files, and proposes a minimal reversible edit to the playbook so the same class of gap is more likely to be caught next ti

• testing-audit

  Audit whether a JavaScript or TypeScript project's tests would fail if the product broke — runner, lint, and coverage facts from a collector, a pre-filter for hollow tests, risk-ranked judgement, and optional mutation testing.

• typescript-audit

  Audit a TypeScript project's type discipline against an opinionated baseline spanning compiler configuration, type quality in source, type system usage, and type safety at IO boundaries. Static-first with optional --with-run enrichment from tsc --noEmit. Optionally generates an implementation plan f

Similar plugins