Loading...
Loading...
Found 147 Skills
General .NET development workflow patterns. Use when implementing features, fixing bugs, or refactoring code.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Orchestrate autonomous AI development with task-based workflow and QA gates
Guides through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps document security properties for fuzzing/verification, and reviews manual security areas.
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Use before building anything new or when a plan needs review. Not for bug fixes or small edits.
Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.
Use this when you have a written implementation plan to execute in a separate session with review checkpoints.
Use this when you need to start feature development isolated from the current workspace, or before executing implementation plans — ensure an isolated workspace exists via native tools or the git worktree fallback mechanism