GitHub
work-issue
Core implementation logic for working on a single GitHub issue. Used by both /work command and /work-all subagents to ensure consistent behavior.
Skills IA Blockchain
Découvrez les skills Blockchain, comparez leurs dépôts et consultez leurs instructions.
Catégories: Blockchain
Blockchain Effacer les filtres
Explorer
GitHub
javascript-standards
JavaScript and TypeScript coding standards, conventions, and best practices. Use when writing, reviewing, or testing JS/TS code.
GitHub
workflow-orchestration
Defines the autonomous development workflow. Use when orchestrating work between agents, managing issue lifecycles, or understanding the development loop.
GitHub
css-standards
CSS, SCSS, and styling conventions. Use when writing, reviewing, or debugging styles and layouts.
GitHub
user-stories
Guidelines for writing effective user stories with clear acceptance criteria. Use when creating issues from discovery findings.
GitHub
project-commands
Manages project-specific commands for development, testing, and deployment. Use when needing to run project commands or when setting up commands for a new project.
GitHub
notifications
System for alerting the user when attention is needed. Use when you need to get the user's attention for questions, approvals, or when stuck.
GitHub
github-workflow
Manages GitHub workflow including issues, PRs, labels, and reviews. Use when working with GitHub issues, creating PRs, or coordinating reviews.
GitHub
github-issues
Best practices for breaking down work into GitHub issues, proper sizing, and milestone organization. Use during discovery/planning phases.
GitHub
infrastructure-standards
Infrastructure, cloud, and DevOps standards. Use when setting up new projects, configuring cloud resources, or working with IaC.
GitHub
agent-coordination
Patterns for invoking and coordinating Automatasaurus agents. Use when delegating tasks to specialist agents.
GitHub
requirements-gathering
Discovery questions, checklists, and techniques for gathering requirements. Use during discovery to ensure thorough understanding before creating issues.
GitHub
code-review
Best practices for performing thorough, constructive code reviews. Use when reviewing PRs to ensure quality feedback that improves code and helps developers grow.
GitHub
python-standards
Python coding standards, conventions, and best practices. Use when writing, reviewing, or testing Python code.
GitHub
flutter-worktrees
Use when starting feature work that needs isolation from current workspace - creates isolated git worktrees with Flutter project setup
GitHub
flutter-parallel-agents
Use when facing 2+ independent Flutter tasks that can be worked on without shared state or sequential dependencies
GitHub
flutter-subagent-dev
Use when executing Flutter implementation plans with independent tasks in the current session
GitHub
start-flutter-craft
Use when starting any conversation - establishes how to find and use Flutter development skills, requiring Skill tool invocation before ANY response including clarifying questions
GitHub
design-polish
디자인 레퍼런스 기반 폴리싱. 트렌드 검색, Gap 분석, WCAG 접근성 체크, 개선안 도출. /design-polish 명령으로 실행.
GitHub
flutter-debugging
Use when encountering any bug, test failure, or unexpected behavior in Flutter - requires systematic investigation before proposing fixes
GitHub
flutter-finishing
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of Flutter development work by presenting structured options
GitHub
flutter-executing
Use when you have a written implementation plan to execute with review checkpoints
GitHub
flutter-verification
Use when about to claim work is complete, fixed, or passing - requires running Flutter verification commands and confirming output before making any success claims; evidence before assertions always
GitHub
flutter-brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation using Clean...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.