swiftiomatic

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.