toba

Runtime debugging for the MathViews Swift package using LLDB and xc-debug MCP tools. Use when: (1) Attaching LLDB to a running app that uses MathViews, (2) Setting breakpoints in typesetting, parsing, or font code, (3) Inspecting math rendering state at runtime, (4) Diagnosing layout, spacing, or glyph issues, (5) User says "debug", "breakpoint", "attach", "inspect", or asks to investigate runtime behavior.

LaTeX math domain knowledge for the math-views (SwiftMath) project. Use when: (1) adding new LaTeX commands, symbols, operators, or accents, (2) implementing structural commands (fractions, radicals, environments), (3) validating math rendering correctness or comparing against KaTeX, (4) working on MTMathAtomFactory, MTMathListBuilder, or MTTypesetter, (5) user mentions LaTeX, math rendering, TeX spacing, or atom types, (6) working on multiline/line breaking behavior in the typesetter.

Run and manage tests for the MathViews Swift package. Use when (1) running tests after code changes, (2) debugging test failures, (3) adding new tests, (4) understanding test infrastructure. Triggers on: test failures, writing tests, running tests, TDD workflow.

Write and maintain DocC documentation for the MathViews Swift package. Use when: (1) Creating a Documentation.docc catalog (2) Writing or editing documentation landing pages (3) Adding articles or guides (4) Documenting symbols with triple-slash comments (5) Organizing Topics sections (6) Fixing DocC build warnings or broken links (7) User mentions "documentation", "docc", "docs", or asks to document code

Create, modify, and diagnose Swiftiomatic rules. Use when: (1) creating a new rule, (2) modifying an existing rule, (3) debugging why a rule doesn't trigger or triggers incorrectly, (4) understanding the rule architecture, (5) creating test-related rules (XCTest, Swift Testing). Triggers on mentions of "rule", "lint rule", "format rule", "SyntaxLintRule", "SyntaxFormatRule", "diagnose", "finding", "TestSuiteDetection", rule file paths under Sources/Swiftiomatic/Rules/.

Write and maintain DocC documentation for Swift modules. Use when: (1) Creating new Documentation.docc catalogs (2) Writing or editing Main.md landing pages (3) Adding articles or guides to documentation (4) Documenting symbols with triple-slash comments (5) Organizing Topics sections (6) Adding images, diagrams, or code examples to docs (7) Fixing DocC build warnings or broken links (8) User mentions "documentation", "docc", "docs", or asks to document code

End-to-end testing of xc-mcp MCP tools against the Thesis macOS app from ../thesis. Use when: (1) user says "test", "test with thesis", "try the tools", "test harness", "test the tool", "/test", (2) verifying any MCP tool works end-to-end (interact_, debug_, screenshot, build, preview_capture), (3) running a full UI automation scenario (build → tree → click → screenshot), (4) launching the Thesis app for manual feature evaluation, (5) testing MCP tools via JSON-RPC over pipes (test-debug.sh), (6) debugging MCP tool failures by running the server directly.

Diagnose and resolve Xcode build system issues when programmatically creating or modifying Xcode project files via XcodeProj. Use when: (1) working on PreviewCaptureTool.swift or any code that injects targets into .xcodeproj files, (2) debugging xcodebuild failures for injected/preview host targets, (3) encountering linker errors like undefined symbols, missing dylibs, or empty framework bundles, (4) investigating .debug.dylib crashes or _relinkableLibraryClasses errors, (5) dealing with mergeable library issues or SPM transitive dependency linking failures, (6) user mentions "preview capture build", "inject target", or "xcodebuild linker error".

Write and maintain DocC documentation for Swift modules. Use when: (1) Creating new Documentation.docc catalogs (2) Writing or editing Main.md landing pages (3) Adding articles or guides to documentation (4) Documenting symbols with triple-slash comments (5) Organizing Topics sections (6) Adding images, diagrams, or code examples to docs (7) Fixing DocC build warnings or broken links (8) User mentions "documentation", "docc", "docs", or asks to document code

Intelligent Xcode development operations

Check upstream repos for updates. Use when user says "/upstream", "check upstream", "sync with upstream", or wants to see what's changed in the source repos this project was derived from.

Stage all changes and commit with a descriptive message. Use when the user asks to commit, save changes, or says "/commit".

EPUB 3.3 photo book generation from Lightroom Classic collections. Use when: (1) Working on internal/epub/ package code (2) Creating or modifying EPUB output (OPF, XHTML pages, navigation, CSS) (3) Debugging EPUB validation errors (epubcheck) (4) Adding fixed-layout (FXL) support for pre-paginated photo pages (5) Modifying the ZIP container structure (mimetype, META-INF, OEBPS) (6) Working with Dublin Core metadata or rendition properties (7) User mentions epub, photo book, ebook, opf, xhtml content documents, or epub packaging

Check upstream repos for updates. Use when user says "/upstream", "check upstream", "sync with upstream", or wants to see what's changed in the source repos this project was derived from.

Stage all changes and commit with a descriptive message. Use when the user asks to commit, save changes, or says "/commit".

Check upstream repos for updates. Use when user says "/upstream", "check upstream", "sync with upstream", or wants to see what's changed in the source repos this project was derived from.

Expert knowledge of the MusicBrainz Web Service API (ws/2). Use when: (1) writing or modifying code that calls the MusicBrainz API, (2) constructing search queries, browse requests, or lookup requests, (3) choosing correct inc= parameters, type/status filters, or pagination strategy, (4) debugging MusicBrainz API errors or unexpected responses, (5) adding new MusicBrainz entity types or endpoints to the codebase, (6) working with files in internal/integration/musicbrainz/, (7) user mentions musicbrainz, mb, mbid, release-group, or MusicBrainz API.

Coordinate work across sibling LSP repos (css-lsp, epub-lsp, sqlite-lsp, go-template-lsp). Spawns parallel agents to do work in each repo, then commits and pushes each. Use when: (1) user says /bro, (2) user says "update our LSPs", (3) user wants to bump the toba/lsp library version across sibling repos, (4) user wants to apply changes, fixes, or issue work across all sibling LSP repos simultaneously.

Check upstream repos for new changes that may be worth incorporating. Use when: (1) User says /upstream (2) User asks to "check upstream" or "what changed upstream" (3) User wants to know if upstream repos have new commits (4) User asks about syncing with or pulling from upstream sources

Check upstream repo for new changes that may be worth incorporating. Use when: (1) User says /upstream (2) User asks to "check upstream" or "what changed upstream" (3) User wants to know if upstream repos have new commits (4) User asks about syncing with or pulling from upstream sources

Stage all changes and commit with a descriptive message. Use when the user asks to commit, save changes, or says "/commit".

Stage all changes and commit with a descriptive message. Use when the user asks to commit, save changes, or says "/commit".