Loading...
Loading...
Found 18 Skills
Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documentation, high-level overviews, or technical specifications.
Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use when you need to understand HOW code works.
Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests
Comprehensive Azure Data Factory validation rules, activity nesting limitations, linked service requirements, and edge-case handling guidance
Cross-Layer Check
Comprehensive n8n workflow testing including execution lifecycle, node connection patterns, data flow validation, and error handling strategies. Use when testing n8n workflow automation applications.
Create interactive Sankey diagrams for flow visualization from CSV, DataFrame, or dict data. Supports node/link styling and HTML/PNG/SVG export.
Project analysis tool designed to analyze the system architecture and inter-module data flow of codebases. This skill applies when you need to understand project structure, generate architecture diagrams, analyze data flow between modules, or create sequence diagrams. It supports outputting visual charts using Mermaid syntax. Use cases: (1) Project architecture organization (2) Module dependency analysis (3) Data flow tracing (4) New team member project onboarding (5) Technical document generation
Manage data flow when producers outpace consumers. Bounded buffers, adaptive flushing, and graceful degradation prevent OOM crashes and data loss.
Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...
Design and architect Goldsky Turbo pipelines. Use this skill for 'should I use X or Y' decisions: kafka source vs dataset source, streaming vs job mode, which resource size (xs/s/m/l/xl/xxl) for my workload, postgres vs clickhouse vs kafka sink, fan-in vs fan-out data flow, one pipeline vs many, dynamic table vs SQL join, how to handle multi-chain deployments. Also use when the user asks 'what's the best way to...' for a pipeline design problem, or is unsure how to structure their pipeline before building it.
Verify cross-component wiring: exports are imported AND used, real data flows through connections, output shapes match input expectations. Use after /feature-implement, before /feature-validate, or standalone on any codebase. Use for "check integration", "verify wiring", "are components connected", "integration check", or "/integration-checker". Do NOT use for unit test failures, linting, or single-file correctness issues.