architecture-tradeoff-reviewer
Internal Moonshot Architecture stage for comparing architecture options and selecting a justified recommendation.
architecture-option-generator
Internal Moonshot Architecture stage for generating architecture options from ASRs, constraints, and current evidence.
architecture-gate-reviewer
Internal Moonshot Architecture stage for reviewing whether an architecture package is ready for implementation handoff.
architecture-artifacts
Produce architecture artifacts and a provenance-bound Task Contract Seed before Kernel execution.
adr-c4-writer
Internal Moonshot Architecture stage for writing C4 model artifacts and ADRs from accepted architecture decisions.
moon-relay-kernel
Explicit-only entrypoint for Moon Relay Kernel task routing and adaptive workflow execution. Use only when the user explicitly names `moon-relay-kernel`, invokes `$moon-relay-kernel`, or explicitly asks to use the Kernel skill or Kernel mode for the current task. Do not infer activation from installed availability, AGENTS.md, track markers, repository context, or a task that merely concerns Kernel.
verification-contract-gate
Checks whether a downstream project has enough verification contract information and blocks strict completion when it does not.
verification-evidence-gate
Block completion claims in strict runs when fresh verification evidence is missing.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
workspace-isolation-gate
Use before implementation in strict runs to confirm isolated workspace setup and baseline evidence.
explain-diff-html
Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
ui-audit
Read-only UI quality analysis across accessibility, performance, responsive behavior, theming, and design anti-patterns.
test-driven-development
Enforce red-green-refactor evidence before behavior-changing implementation work.
teach-impeccable
Gather persistent design context for a project and save it to .impeccable.md so future UI work has real product context.
task-slicer
Split an execution plan into independently executable vertical-slice task documents.
session-logger
Record decisions, issues, and handoff notes during or after work.
qa-flow
Run a guided browser-based QA flow against a local or staging URL using the persistent browser runtime when available.
faceless
Create, render and publish AI faceless videos with Faceless.so. Use when the user asks about creating faceless videos, AI video generation from a script, auto-posting to YouTube, TikTok, Instagram or X, automated video series, scheduling short-form content across platforms, or checking Faceless credits and post analytics.
git-hex-conflict-resolution
>
git-hex-branch-cleanup
>
git-hex-pr-workflow
>
orchestrator
タスクの調整と他のロールへの委譲を行うコーディネーターロール
common
全ロール共通で使用できる基本ツール
aegis-architect
アーキタイプベースのスキャフォールドツール - プロジェクトの重さに応じた型を選択
code-reviewer
コードレビューとベストプラクティスの提案を行うスキル
browser-testing
ブラウザ自動化とE2Eテストを行うスキル
data-analyzer
データ分析と可視化を行うスキル
docx-handler
Word文書の読み取り、編集、作成を行うスキル
maker
Generate .NET Core data API code from model definitions using the Maker XML specification and CLI. Use when users need to: (1) Create Maker XML models from JSON objects, SQL scripts, or database schemas, (2) Generate .NET Core CRUD API endpoints from Maker XML, (3) Understand or validate Maker XML model definitions, or (4) Work with the Maker CLI tool for code generation.
dotnet-cqrs-api
Guide for building .NET APIs using CQRS pattern with MediatR, FluentValidation, and Carter modules
reindex-docs
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
repo-docs
Update and maintain core repository documentation files (README.md, CHANGELOG.md, LICENSE, CONTRIBUTING.md) before commits or releases. Use when users need to update documentation to reflect code changes, prepare for releases, or ensure documentation consistency.
aspose-slides
Comprehensive skill for manipulating Microsoft PowerPoint presentations using Aspose.Slides.NET library with modern C# patterns
measuring-pr-performance-impact
Measures GraphQL resolver latency changes before/after a PR merge using Datadog metrics. Use when analyzing PR performance impact, measuring latency changes, or comparing resolver performance before and after a code change.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-propose-change
Start a new OpenSpec change and create the first ready artifact for it. Use this when the user wants to propose a feature, fix, or structured change in this repository using the repo's OpenSpec workflow, or when a newly reported repo bug/feature is being translated into tracked work.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
repo-task-delivery
Use this when the user reports any problem, regression, warning, bug, improvement, or proposed repo change that is likely to result in a committed repository edit. Default to the full repo workflow: GitHub issue/project tracking, OpenSpec change, implementation, verification, pull request, merge, and closeout.
learning-app-remote-inspect
Step-by-step debugging workflow for the learning app through a phone's Chrome remote-inspect target. Use when the user has `chrome://inspect/#devices` open and wants a copy-paste command loop for Console/Elements/Network instead of direct automation.
learning-app-cdp
Inspect or debug the learning app in a real browser through the project-specific Windows Chrome CDP workflow. Prefer this skill for browser testing, browser debugging, console inspection, network capture, DOM/runtime inspection, and service-worker-aware refreshes against http://sprecha.localhost or https://sprecha.de. Commands: doctor, start-local/start-prod (launches Chrome with the debug port — use this when Chrome is down, never launch chrome.exe by hand), refresh-*, wait-* (--path/--selector), eval-* (--expression/--file), console-*, monitor-*, read, clear, stop.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
gh-project-workflow
End-to-end GitHub execution workflow for project delivery: create project items, assign available single-select fields (such as Status and optional Area), convert draft items to issues when needed, create and check out development branches via `gh issue develop`, then commit, push, create/merge pull requests, and run deployment commands on request. Use when the user explicitly asks to operate GitHub issue/PR lifecycle, or when another repo workflow skill delegates the GitHub tracking and delivery steps to it.
invoicing
Interact with the Eenvoudig Factureren API to manage clients, invoices, quotes, orders, and more. Use me when dealing with invoicing, clients, quotes, orders, deliveries, receipts, payments, stock items, or subscriptions.
Page 1548 of 1700 · 84990 results
