Loading...
Loading...
Found 1,213 Skills
Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only.
Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnostic patterns before concrete implementation choices.
Build, integrate, and troubleshoot SharePlay GroupActivities features, including GroupActivity definitions, activation flows, GroupSession lifecycle, messaging and journals, ShareLink and SharePlay UI surfaces, and visionOS spatial coordination. Use when implementing or debugging SharePlay experiences across Apple platforms, especially visionOS.
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.
Orchestrate the full skill development lifecycle from idea to publication. Guides through ideation, requirements definition, skill implementation, and marketplace registration. Use when: "create a new skill end-to-end", "skill development workflow", "build and publish a skill", "スキル開発ワークフロー", "スキルを作って公開", "新しいスキルを開発".
Search auto-generated codebase documentation for function signatures, API docs, class definitions, and code comments. Use when the user asks to "search docs", "find documentation", "look up a function", "check the API", or before implementing changes to verify correct signatures and patterns.
Understand customer motivations through job theory. Use when defining product strategy, conducting user research, identifying competitors, writing user stories, or reframing features around customer progress.
WPILib and FRC robot programming best practices, design patterns, and code guidance for Java. Use when writing, reviewing, or explaining WPILib robot code—command-based project structure, subsystems, autonomous routines, RobotContainer layout, command definition patterns (inline, factory, subclass), or Constants organization.
Set up Tailwind v4 with shadcn/ui using @theme inline pattern and CSS variable architecture. Four-step mandatory pattern: define CSS variables at root, map to Tailwind utilities, apply base styles, get automatic dark mode. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui dark mode, or fixing colors not working, theme not applying, CSS variables broken, tw-animate-css errors, or migrating from v3.
Label taxonomy and triage workflow for GitHub issues. Defines type labels (bug/feature/enhancement/docs/chore), priority levels (critical/high/medium/low), status labels, and triage decision workflow. Use when categorizing and prioritizing issues.
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.