dagster-init
Initialize a dagster project using the create-dagster cli. Create a dagster project, uv virtual environment, and everything needed for a user to run dg dev or dg check defs successfully. (project)
发现 区块链 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Initialize a dagster project using the create-dagster cli. Create a dagster project, uv virtual environment, and everything needed for a user to run dg dev or dg check defs successfully. (project)
Create a custom Dagster Component with demo mode support, realistic asset structure, and optional custom scaffolder using the dg CLI. Use this skill if there is no Component included in an existing integration...
Expert guidance for Dagster data orchestration including assets, resources, schedules, sensors, partitions, testing, and ETL patterns. Use when building or extending Dagster projects, writing assets, configurin...
Manage backlog and archive completed work. Use for backlog operations, archiving phases, or keeping active plan focused. Curates plan organization.
Guide architectural decisions and PLAN.md updates using Flow framework. Use when user discusses "architecture", "how should we architect", "design patterns", "how should we structure", "how do we structure", "t...
Navigate Flow projects with dashboard-first pattern. Use when user asks about status, current work, what's next, or project progress. Read-only skill.
Verify plan consistency, generate summaries, maintain plan health. Use for review, verification, summaries, or plan maintenance. Mostly read-only with maintenance operations.
Document findings and maintain task notes using Flow framework. Use when user says "document", "document this", "document finding", "add notes", "add this to notes", "write this down", "summarize", "summarize t...
Use multiple Claude agents to investigate and fix independent problems concurrently
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
Systematically trace bugs backward through call stack to find original trigger
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Run verification commands and confirm output before claiming success
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
Name code by what it does in the domain, not how it's implemented or its history
Design features through brainstorming and make architectural decisions. Use when user wants to brainstorm, design approach, make architecture choices, or update PLAN.md.
Initialize Flow projects from scratch, migrate existing docs, or update old structures. Use when user says "start flow", "initialize", "migrate to flow", "set up flow project".
Each routine does one thing and does it well - extract when routines have multiple responsibilities
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Try 2-3 different approaches before implementing - don't settle for first design you think of
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。