Discover blockchain project management skills, compare source repositories and read the instructions for each workflow.
GitHub development workflow best practices. Use when creating commits, pull requests, branches, reviewing code, managing issues, or any git/GitHub operations. Provides standards for commit messages, PR descript...
Canonical workflow for clarifying requirements, executing work, and verifying correctness.
TODO
Conducts an audit of a Pull Request, merges it into main, and synchronizes the local environment. Use this skill when a PR is ready for final review and integration.
TODO
TODO
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design,...
Always orient work in the LabTrackSimple repo by reading `implementation_plan.md` to identify pending tasks and proceed. Use when deciding next steps, interpreting project scope, or validating work against the...
Clear manually-set title, reverting to auto-generated task summary. Triggers: "/clear-title", "clear title", "reset title"
Subagent-based collaborative analysis. Launch 4-6 specialist subagents in parallel to analyze a topic from different perspectives, then cross-pollinate and synthesize. Usage: /multi-mind [rounds=3]
Resume work on a project - discover state, verify health, clean up stale docs, suggest next tasks. Use when: (1) starting work at beginning of day, (2) after a long agent work loop completes, (3) user asks "wha...
Use when executing implementation plans with independent tasks in the current session
タスクのビジネス的背景・目的を体系的に定義し、チケットに記載する。
タスクの現状分析と次に進むべきロードマップ提案を行う。ユーザーが明示的に「roadmap」スキルの使用を指定した場合にのみ使う。
タスクの実装を作業ステップに分解し、順序と粒度を計画する。
gh CLIでGitHub Issueを作成するスキル。現在の動作/期待する動作/再現手順/環境情報などの最小入力から、AIが作業可能な構造化Issue（調査・修正・検証の手順と受け入れ条件付き）を作成する。Codex/Claude/Gemini/Cursorで共...
REQUIRED for git/GitHub operations: Use `mael gh create-pr` for PRs, `mael sync` before work. Also covers Linear task management and Sentry debugging. Always invoke /mael before commits or PRs.
Guidelines for building "Skill Modules" that the G-Pilot Architect can plan and the Executor can deploy.
Creates structured implementation plans from feature requirements. Use when planning new features, multi-phase projects, or when the user asks for an implementation plan, build plan, or development roadmap.
Creates structured feature requirement documents for software features. Use when defining new features, writing requirements, specifying CLI commands, API endpoints, or when the user asks for feature documentat...
Required workflow for implementing phases from plans in requirements/implementation/. Enforces status tracking (Pending → 🔄 In Progress → ✅ Complete), GitHub issue comments, branch naming (feat/{ID}-summary),...
Product Manager persona for business vision and strategy. ACTIVATE when messages contain PRD, roadmap, business impact, ROI, metrics, stakeholder, product vision, business strategy, business case, go-to-market,...
Code Reviewer persona for technical code analysis. ACTIVATE when messages contain review code, analyze code, code quality, best practices, refactor, improve code, check code, code review, look at code, feedback...
Guide for creating commit message. This skill should be used when you try to create a commit message.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.