Loading...
Loading...
Found 2,062 Skills
Semi-automated design quality review for Flows apps. Runs concrete repo probes (grep, lint, build) to propose a draft 1–5 score for each of the official 10 quality-guidelines questions from docs.cognite.com/cdf/flows/guides/quality-guidelines, then asks the user to confirm or override each score. Still requires the user to walk their tasks end-to-end in the running app (Step 2) since navigation and clickability feel cannot be measured statically. Writes reviews/design-review/feedback-round-<N>/design-review-report.md with an overall average and prioritized fix lists. Use when the user asks to run a Flows design review, run the design quality assessment, or run flows-design-review. Must be run AFTER flows-code-review reaches 0 Must Fix and BEFORE flows-external-app-submit.
Salesforce Data 360 automation with data actions, data action targets, DataObjectDataChgEvent, Data Cloud-triggered flows, activation-triggered flows, API activations, Flow orchestration, and event payload design. TRIGGER when: the user creates or debugs Data 360 triggered automation or downstream flows from DMO, calculated insight, engagement, segment, activation, or data action events.
This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release.
Prefect Flow Builder - Auto-activating skill for Data Pipelines. Triggers on: prefect flow builder, prefect flow builder Part of the Data Pipelines skill category.
Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.
Generate polished technical diagrams as SVG, and export PNG when local export tooling is available. Use when the user wants an architecture diagram, flowchart, data flow, sequence diagram, agent or memory diagram, comparison matrix, timeline, or concept map rendered as a visual artifact instead of Mermaid or a hand-drawn whiteboard. Trigger on requests like 画图、帮我画、生成图、 做个图、架构图、流程图、时序图、可视化一下, or English requests such as draw diagram, architecture diagram, visualize this system, generate a flowchart, or create a technical SVG. Prefer this skill when the user wants publishable SVG/PNG output, style selection, or AI/agent-system diagram conventions.
Create SVG infographics, architecture diagrams, and flowcharts in various styles. Be sure to use this skill whenever the user mentions any of the following scenarios: - Draw flowcharts, architecture diagrams, system diagrams, infographics, schematic diagrams - Use SVG to draw charts, visualize a process or concept - "Help me draw a diagram to explain...", "Generate an architecture diagram", "Draw a schematic" - Visualize text-described systems or processes into diagrams - Want illustrations in specific styles (Anthropic style, dark theme, etc.) Even if the user doesn't explicitly mention "SVG", this skill should be used whenever process/architecture/information visualization is involved.
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue — use customer-success-manager for that.
Expert guide for designing Git branching strategies including Git Flow, GitHub Flow, trunk-based development, and release management. Use when establishing team workflows or improving version control practices.
Use FlowR APIs correctly across Dart and Flutter projects. Use when writing or reviewing flowr_dart FlowR/FlowB code, flowr FrViewModel/FrBlocViewModel widgets, FrProvider setup, FrUnion state, stream helpers, or migration after FlowR breaking changes, even when the project has its own file layout.
Reviews React Flow code for anti-patterns, performance issues, and best practices. Use when reviewing code that uses @xyflow/react, checking for common mistakes, or optimizing node-based UI implementations.
Implements React Flow node-based UIs correctly using @xyflow/react. Use when building flow charts, diagrams, visual editors, or node-based applications with React. Covers nodes, edges, handles, custom components, state management, and viewport control.