continue-diagram
Continue working on an existing diagram. Load, review, and modify persistent diagrams across sessions.
What this skill does
# Continue a Diagram Continue working on diagrams from previous sessions. ## Finding Diagrams **List recent diagrams:** ``` list_diagrams() ``` **Filter by scope:** ``` list_diagrams(scope: "project:my-app") ``` **Search by content:** ``` search_diagrams(query: "notification architecture") ``` ## Loading a Diagram **By ID (exact):** ``` get_diagram(id: "abc-123") ``` **By title (fuzzy match):** ``` get_diagram(title: "notification flow") ``` **With version history:** ``` get_diagram(id: "abc-123", include_history: true) ``` ## Updating Diagrams When you modify a diagram, the previous version is automatically saved to history. **Update content:** ``` update_diagram( id: "abc-123", mermaid: "flowchart TD\n A --> B --> C", note: "Simplified the flow" ) ``` **Update metadata:** ``` update_diagram( id: "abc-123", title: "New Title", context: "Updated context explaining changes", tags: ["architecture", "v2"] ) ``` ## Version History Diagrams track their evolution. Each update creates a version snapshot. To see history: ``` get_diagram(id: "abc-123", include_history: true) ``` History shows: - Previous Mermaid content - Timestamp of each version - Notes explaining what changed ## Exporting **As Mermaid file:** ``` export_diagram(id: "abc-123", format: "mermaid") ``` **As SVG (via Mermaid CLI):** ``` export_diagram(id: "abc-123", format: "svg") ``` **For draw.io:** ``` export_diagram(id: "abc-123", format: "drawio") ``` ## Cleanup **Delete a diagram:** ``` delete_diagram(id: "abc-123") ``` ## Workflow Tips 1. **Start each session** by checking for relevant existing diagrams 2. **Update, don't recreate** — build on existing work 3. **Use notes** — explain what changed when updating 4. **Export for sharing** — generate files others can view ## Related Skills - **capture** — Create new diagrams during brainstorming
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.