tapps-brain

Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.

Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.

Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.

Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.

Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.

Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.

Frontend/UX TAPPS workflow: playbook, UI library docs, and quality gate on scored files. Use when building UI components, accessibility fixes, or client-side routing changes.

Security-focused TAPPS workflow: playbook, library docs, security scan, and CVE check. Use when implementing auth, secrets, input validation, or pre-release security passes.

Testing-focused TAPPS workflow: playbook, pytest docs, diff impact, and validation. Use when adding tests, fixing test gaps, or validating affected tests after refactors.

Run the end-of-task TAPPS pipeline in one shot — validate_changed, then checklist, then an optional memory save for anything architectural or patterned learned this session. The recommended final step before declaring work complete. Use when you have finished implementing a task and want to validate, run the checklist, and save learnings in one shot.

Standard feature/bugfix development flow via the shared TAPPS pipeline. Use when starting daily implementation work and you want session start, lookup docs, quick_check loop, and finish-task without a domain specialist.

QA/review flow: parallel review pipeline or single-file review ending in checklist. Use when reviewing PRs, audit findings, or validating another agent's changes.

Look up when to use each TappsMCP tool. Full tool reference with per-tool guidance for session start, scoring, validation, checklist, docs, experts, and more. Use when you need guidance on which TappsMCP tool to call for a given situation.

Frontend/UX TAPPS workflow: playbook, UI library docs, and quality gate on scored files. Use when building UI components, accessibility fixes, or client-side routing changes.

Security-focused TAPPS workflow: playbook, library docs, security scan, and CVE check. Use when implementing auth, secrets, input validation, or pre-release security passes.

Testing-focused TAPPS workflow: playbook, pytest docs, diff impact, and validation. Use when adding tests, fixing test gaps, or validating affected tests after refactors.

Run the end-of-task TAPPS pipeline in one shot: validate changed files, verify the checklist, and optionally save learnings to memory. Use when you have finished implementing a task and want to validate, checklist, and save learnings in one shot.

Standard feature/bugfix development flow via the shared TAPPS pipeline. Use when starting daily implementation work and you want session start, lookup docs, quick_check loop, and finish-task without a domain specialist.

QA/review flow: parallel review pipeline or single-file review ending in checklist. Use when reviewing PRs, audit findings, or validating another agent's changes.

Look up when to use each TappsMCP tool. Full tool reference with per-tool guidance for session start, scoring, validation, checklist, docs, experts. Use when you need guidance on which TappsMCP tool to call for a given situation.

Create, lint, validate, or triage Linear issues and epics for agents. MANDATORY for all Linear writes — never call plugin save_issue directly. Routes to docs-mcp generator/validator/triage tools and the Linear plugin by user intent. Use when creating, linting, validating, or triaging a Linear issue or epic.

Post a structured Linear project update document on a version release. Orchestrates tapps_release_update → docs_validate_release_update → save_document → cache invalidation. Use when posting a release announcement to Linear after shipping a new version.

Bootstrap a fresh session from the last handoff by reading session-handoff.md, optional Linear context, and TAPPS session start — without pasting a long manifesto. Use when the user says continue, pick up where we left off, resume, or start a new session on an existing task (optional TAP-#### argument).

Bootstrap documentation for a new or under-documented project: README, CONTRIBUTING, onboarding, completeness check. Use when creating a README, onboarding guide, or initial doc scaffold (Anthropic documentation skill parity).

End-of-doc-work validation bundle: drift, links, cross-refs, completeness, optional release gate. Use when documentation edits are complete and you need a pass/fail verdict before merging or releasing.

Quick doc generation: README, llms.txt, changelog. Use for a minimal generate pass; prefer tapps-docs-bootstrap for new projects.

Full documentation refresh workflow: cross-refs, narrative docs, API/diagrams, validation suite. Codifies docs/tutorials/05-docs-refresh-workflow.md. Use when refreshing project docs, auditing doc health, or preparing docs before a release.

Generate a documentation quality report. Runs project scan, completeness check, and Diataxis balance analysis. Use when you need a doc health dashboard or audit summary.

Validate documentation quality. Checks drift, freshness, links, and Diataxis balance. Use for a lighter validation pass than tapps-docs-finish-task.

Change the TappsMCP enforcement intensity (high, medium, or low). Controls which quality tools are mandatory vs optional. Use when you want to switch between strict, balanced, or advisory enforcement modes.

Bootstrap TappsMCP in a project. Creates AGENTS.md, TECH_STACK.md, platform rules, hooks, agents, skills, and MCP config. Use when setting up TappsMCP in a new or existing project for the first time.

Manage shared project memory via tapps-mcp CLI and session notes. Use when saving cross-session decisions, searching prior patterns, or checking brain bridge health. For chat handoffs use tapps-handoff-session.

Function-level refactor workflow using call graph tools (Epic 114). Use before changing a symbol's signature, deleting a function, or refactoring callers — maps blast radius via tapps_call_graph and diff_impact.

Look up library documentation and research best practices for the technologies used in this project. Use when writing code that uses an external library or when you need API reference or version-specific guidance.

Orchestrate a parallel review-fix-validate pipeline across multiple changed files. Spawns tapps-review-fixer agents in worktrees for parallel processing. Use when you have multiple changed Python files that need parallel review, scoring, and quality gate fixing before declaring work complete.

Run a comprehensive security audit including vulnerability scanning and dependency CVE checks. Use when reviewing security-sensitive changes, before a security audit, or before a production release.

Upgrade tapps-mcp / docs-mcp in this project to the latest version. Reinstalls global CLIs, restarts the MCP servers, refreshes scaffolding via `tapps-mcp upgrade` (dry-run preview + timestamped backup), and verifies via doctor + checklist. Use when a new tapps-mcp or docs-mcp version is available and the project scaffolding needs to be refreshed.

Post a structured Linear project update document on a version release. Orchestrates tapps_release_update → docs_validate_release_update → save_document → cache invalidation. Use when posting a release announcement to Linear after shipping a new version.

Bootstrap README, CONTRIBUTING, onboarding for new projects. Use when creating a README, onboarding guide, or initial doc scaffold.

Doc-work finish bundle: drift, links, cross-refs, completeness, optional release gate. Use when documentation edits are complete before merge/release.