requirement-convergence
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins, or when "how far do we go/what's out of scope/is this worth it" is mentioned.
skill-optimization
Evaluates and optimizes skill file quality using 9 content patterns and 10 editing principles. Use when creating skills, refining skill content, or auditing skill quality.
subagents-orchestration-guide
Coordinates subagents through scale-based planning, approval, implementation, verification, and escalation flows. Use when routing work to subagents, executing an approved work plan, or resuming autonomous execution.
technical-spec
Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.
typescript-rules
Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types.
typescript-testing
Applies repository-aware TypeScript test design, behavior evidence, isolation, and mock-boundary criteria. Use when writing or reviewing unit tests.
api-design
RESTful API design best practices and conventions guide
code-quality-suite
代码质量综合技能包（代码审查 + 单元测试）
code-review
代码审查最佳实践指南
database-design
数据库设计规范与优化指南
git-commit-guide
Git 提交规范（Conventional Commits）
hello-skill
示例技能，用于 PluginRegistry 测试
java-best-practices
Java 编码最佳实践与设计模式
maven-troubleshoot
Maven 构建故障排查专家，擅长解决依赖冲突、编译错误、插件配置问题
unit-testing
Java单元测试编写指南（基于JUnit和Mockito）
weather
Get current weather and forecasts (no API key required).
maestro-bundle
Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.
maestro-coach
Decision support and grounded teaching for the human. Invoke when the user signals a message did not land ("wait, what?", "I don't understand", "explain it like I'm five", "which is better?", "I'm not sure") about a question or fork they have been asked, or when they hand over a locked decision, a lesson, or a bundle and want to learn the concept behind it. Also triggers on Vietnamese phrasings such as giải thích chi tiết, giải thích rõ hơn, rõ hơn, tôi không hiểu, cái nào tốt hơn.
maestro-council
Lead-only council for a hard-to-reverse fork - a neutral brief, sealed independent seats, one premise verifier on unanimity, bounded verifiers, one cross-examination round, a draft-verdict audit, and one binding verdict recorded as a decision with its dissent. Never inside a seat.
maestro-design
Resolve material unknowns blocking the next authorized slice, using research, grilling, prototypes, models, or wayfinding. Record durable decisions and apply the shared workflow tier rule.
maestro-diagnose
Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence. Read-only; an explicit fix request routes by target and tier instead, never here. Also triggers on Vietnamese phrasings such as root cause là ở đâu, nguyên nhân là gì, tại sao nó không.
maestro-explore
Answer an evidence question without touching production code - research external facts against primary sources, build or iterate a disposable prototype (its own bugfixes included), or baseline current repository behavior before deciding or implementing. Use when the question is answerable by reading, building, or measuring with no user decision required; unsettled decisions belong to maestro-design. Prototypes are throwaway. Also triggers on Vietnamese phrasings such as làm 1 vòng research xem, research xem.
maestro-graph
Drive a pre-known multi-agent path as a maestro graph - run it by name or from a file you just wrote, pull each agent node with graph next, spawn it as a sub-agent under its maestro-<profile> definition, hand the result back with graph result, repeat until the verdict. A sub-agent node is read-only scouting; a node that writes files or is accepted is opened as a pane instead. Author a new graph from the reference when no preset fits.
maestro-improve
Turn filed lessons into the smallest doctrine edit. Use when a Lead assigns improvement work for one target: group pending lessons, make one evidence-linked commit per target, return it for independent challenge, and process each accepted or rejected lesson without deleting history.
maestro-questionnaire
Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting. Also triggers on Vietnamese phrasings such as phỏng vấn đi, phỏng vấn tôi, interview tôi.
maestro-verify
Verify and close - cross-check coverage, run the VERIFY table, deliver the verdict, harvest durable lessons into decisions, close the bundle, and never claim remote state from local evidence.
maestro-work
Implement or fix one authorized unit with minimal edits and sufficient evidence. Reuse existing checks and add tests only for concrete uncovered behavior or risk.
backend-design
Elite Tier Backend standards, including Vertical Slice Architecture, Zero Trust Security, and High-Performance API protocols.
brainstorming
Design-first methodology. Explore user intent, requirements and design before implementation. Turn ideas into fully formed specs through collaborative dialogue.
browser-extension
Master specialized skill for building 2025/2026-grade browser extensions. Deep expertise in Manifest v3, Service Worker persistence (Alarms, Offscreen API), Side Panel API, and Cross-Browser compatibility.
clean-code
The Foundation Skill. LLM Firewall + 2025 Security + Cross-Skill Coordination. Use for ALL code output - prevents hallucinations, enforces security, ensures quality.
debug-mastery
Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards. No fixes without investigation.
frontend-design
Elite Tier Web UI standards, including pixel-perfect retro aesthetics, immersive layouts, and UX psychology protocols.
git-worktrees
Create isolated git workspaces for feature development. Smart directory selection, safety verification, and cross-platform support (Windows/Unix).
optimization-mastery
2026-grade Cross-Domain Optimization. Expertise in Interaction to Next Paint (INP), Partial Hydration, UUIDv7 indexing, and AI Token Stewardship. Performance is a feature, not an afterthought.
planning-mastery
Create concise, architectural implementation plans using the RFC-Lite format. STRICTLY LIMITED VERBOSITY.
ralph-wiggum
Surgical Debugger & Code Optimizer. Autonomous root-cause investigation, persistence-loop fixing, and high-fidelity code reflection. No new features, only fixes.
tdd-mastery
Test-Driven Development Iron Law. Write the test first. Watch it fail. Write minimal code to pass. No exceptions.
verification-mastery
Evidence before claims, always. No completion claims without fresh verification. The final gate before declaring success.
suggest-ai-ready-issues
Use when someone wants to know what to build next in a repository, asks Orbi to propose work, or runs orbi suggest. Reads the repository read-only and proposes at most three deliverable Issues, preferring an existing open Issue that already describes the change.
write-ai-ready-issue
Use when the user wants to turn the current discussion into a GitHub Issue, wants a task done without watching it, asks whether an Issue is clear enough for an AI agent to deliver, or wants to split a big task into several Issues. Reads the repository read-only first, drafts only what the person asked for, runs an independent fidelity pass, and hands the Issue to Orbi when Orbi already delivers the target repository.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
bugs-to-stories
Convert bug reports into prd.json user stories for autonomous fixing. Use after running test-and-break skill. Triggers on: convert bugs to stories, fix these bugs, add bugs to prd, create fix stories.
compound-engineering
Compound Engineering workflow for AI-assisted development. Use when planning features, executing work, reviewing code, or codifying learnings. Follows the Plan → Work → Review → Compound loop where each unit of engineering makes subsequent work easier. Triggers on: plan this feature, implement this, review this code, compound learnings, create implementation plan, systematic development.
docx
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
edge-cases
Analyze a PRD for edge cases, failure modes, and scenarios that might be missed. Use after creating a PRD to strengthen it. Triggers on: analyze edge cases, find edge cases, what could go wrong, edge case analysis.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
pytm
>
Page 443 of 1690 · 84471 results
