Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
After coding work, sweep comments in changed files and sync only related durable guidance through WORTH → PLACE → SHAPE. TRIGGER when: user asks to update/sync durable docs, code comments, or AGENTS.md after work; an executor skill reaches close-out.
Analyze a stack trace, crash report, panic, or error log; find the failing frame and the root cause; then propose a fix and a way to verify it. Covers Kotlin/JVM/Android (coroutines, ANRs, R8-obfuscated traces), KMP/Compose Multiplatform, Flutter/Dart (FlutterError, RenderFlex overflow), Swift on iOS/macOS (.ips reports, EXC_BAD_ACCESS), Rust panics, C++ segfaults and sanitizer output, plus Python, JS/TS, Go and Java. Use when someone pastes a stack trace, crash log or panic—even with no question attached—or says “why does this crash”, “what does this error mean”, “debug this exception”, “root-cause this trace”, “symbolicate this crash”, “deobfuscate this trace”, or the Hungarian “miért crashel”, “mit jelent ez a hiba”, “elemezd ezt a stack trace-t”, “nézd meg ezt a crash logot”. Not for auditing a whole project for latent bugs (that is code-analyzer), nor for a red CI run whose log has not been fetched yet (that is github-fix-ci-error).
Escreve PRDs (Product Requirements Documents) — cria novos ou edita existentes que ainda não foram concluídos. Funciona no modo draft-first: gera o documento completo imediatamente a partir do que o usuário fornecer, marcando premissas inferidas inline para revisão pontual — sem entrevistas longas. Quando o input cobre múltiplas features, detecta automaticamente e propõe divisão em PRDs separados, criando-os em sequência na mesma sessão. Cada PRD é autocontido e foca em comportamento e regras de negócio; detalhes técnicos ficam em TRD/ADR. Use quando o usuário quiser criar ou editar um PRD, documento de requisitos, especificação de feature, planejar uma funcionalidade, definir escopo de uma entrega, documentar requisitos, ou avaliar a quebra/granularidade de um PRD — mesmo que não use o termo "PRD" explicitamente. Também quando mencionar "requisitos do produto", "spec de feature", "escopo da feature", "documento de requisitos", "refinar PRD", "ajustar PRD", "quebra de PRD", "granularidade de PRD", ou fornecer uma descrição longa de funcionalidades para especificar.
Executes exactly one planned Jira or GitHub work-item task after critique approval. Use when a numbered task should move through kickoff, implementation, documentation, requirements verification, clean-code, architecture, and security gates, targeted fix cycles, tracker finalization, and a final report without continuing to the next task. Does not plan tasks or select the next task.
(NS) Orchestrate partitioned version implementation slice-by-slice — dispatch one synchronous subagent per slice with small context, commit after each slice, and advance automatically without confirmation until all slices are done or a stop condition is hit. Use whenever a version has a version-roadmap.md with pending slices and the user asks to "run the orchestrated implementation", "execute all slices", "orchestrate the partitioned version", or drive a subversion roadmap to completion. Do NOT use for non-partitioned versions (execute tasks directly), ad-hoc coding (code-coder), or planning/partitioning (pm-version-partitioner).
Build production-ready MCP servers using FastMCP framework with proven patterns for tools, resources, prompts, OAuth authentication, and comprehensive testing. Use this when creating FastMCP-based MCP servers with features like Google OAuth, multiple resource types, testing with FastMCP Client, or complex tool implementations.
Help developers use FineUI forms: Form / SimpleForm containers, form fields (TextBox / TextArea / NumberBox / DatePicker / DropDownList / CheckBox / RadioButtonList and more), the Calendar inline calendar, field-level and whole-form validation, and reading field values. Covers F.js (JavaScript), Pro (WebForms), FineUI.Core MVC (Fluent API) / RazorForms / RazorPages (TagHelper), plus FineUI.Java (Spring Boot + Thymeleaf dialect tags, kebab-case). Trigger phrases: "FineUI 表单", "F.Form", "SimpleForm", "FormRow", "表单校验", "ValidateForms", "Required", "TextBox", "NumberBox", "DatePicker", "DropDownList", "RadioButtonList", "CheckBox", "CheckBoxList", "TimePicker", "Label", "Hidden", "FileUpload", "TriggerBox", "DropDownBox", "HtmlEditor", "MarkInvalid", "字段标签", "LabelWidth", "读取表单值", "下拉树", "文件上传", "富文本编辑器", "Calendar", "内嵌日历", "日期范围", "月份选择", "年份选择", "时间选择", "OnDateSelect", "FineUI.Java", "Spring Boot", "Thymeleaf", "@FineUIPage", "text-box", "simple-form", "form-row".
Help developers use FineUI's Grid component, covering F.js (JavaScript), Pro (WebForms), FineUI.Core's MVC/RazorForms/RazorPages, and FineUI.Java (Spring Boot + Thymeleaf dialect tags). Use for table configuration, column definition and rendering, data loading and binding, cell editing, row selection (checkbox multi-select/single-select), paging, sorting, summary rows, header filtering, multiple headers, row grouping, tree tables, column locking, cell merging, row expansion/row command/row events, drag-and-drop sorting, big-data tables, and toolbars. Trigger phrases: "FineUI 表格", "F.Grid", "Grid 列", "grid columns", "FineUI.Java", "Spring Boot", "Thymeleaf", "@FineUIPage", "f:grid", "render-field", "data-field", "RenderField", "RenderCheckField", "复选框多选", "EnableCheckBoxSelect", "选中行", "SelectedRowIndexArray", "GetSelectedDataKeys", "getSelectedDataKeys", "RendererFunction", "RendererArgument", "列渲染", "服务端分页", "loadData", "DataKeyNames", "表格排序", "AllowSorting", "合计行", "EnableSummary", "SummaryType", "表头过滤", "AllowFilters", "EnableFilter", "多表头", "GroupField", "行分组", "EnableRowGroup", "树表格", "EnableTree", "TreeColumn", "列锁定", "AllowColumnLocking", "单元格合并", "mergeColumns", "行扩展列", "RowExpander", "行命令", "RowCommand", "行单击事件", "OnRowClick", "拖拽排序", "EnableColumnMove", "大数据表格", "EnableBigData".
Help developers use FineUI's layout system — how a container's `Layout` property arranges child controls: Fit (fill) / Region (top, bottom, left, right, center regions) / HBox·VBox (flexbox) / Block (responsive grid) / Column / Anchor, plus viewport adaptation (IsViewPort / AutoSizePanelID). Covers F.js, Pro, FineUI.Core (MVC/RazorForms/RazorPages), and FineUI.Java (Spring Boot + Thymeleaf dialect tags, kebab-case, including the region-panel convenience control). Trigger phrases: "FineUI 布局", "Layout", "Region 布局", "区域布局", "RegionPosition", "HBox", "VBox", "BoxFlex", "弹性布局", "Fit 布局", "Block 响应式", "BlockMD", "栅格布局", "IsViewPort", "视口自适应", "Column 布局", "Anchor 布局", "FineUI.Java", "Spring Boot", "Thymeleaf", "region-panel", "region-position", "box-flex", "is-view-port".
Set or switch FineUI's existing built-in and custom themes, handling global configuration, PageManager overrides, and Cookie preferences. Covers the F.js, Pro, and Core modes and Java. For adding new themes, brand colors, and theme.config generation tasks, use fineui-custom-theme.
Help developers use FineUI's Tree component: tree container and nodes (TreeNode), static/backend node building, data binding, node icons, checkbox tree (cascade, reading checked nodes), node events (click/expand), asynchronous lazy loading. Covers F.js (JavaScript), Pro (WebForms), FineUI.Core's MVC (Fluent API)/RazorForms/RazorPages (TagHelper), and FineUI.Java (Spring Boot + Thymeleaf dialect tags). Trigger phrases: "FineUI 树", "F.Tree", "TreeNode", "树节点", "树控件", "EnableCheckBox", "enable-check-box", "复选框树", "CascadeCheck", "cascade-check", "级联选中", "GetCheckedNodes", "getCheckedNodes", "懒加载", "OnNodeLazyLoad", "on-node-lazy-load", "异步加载子节点", "节点点击", "nodeclick", "OnNodeExpand", "on-node-expand", "FineUI.Java", "Spring Boot", "Thymeleaf", "@FineUIPage", "f:tree", "f:tree-node".
Upgrade existing FineUI projects to a higher major version (**v10 and above only**), identify breaking changes, generate a migration checklist, and apply it item by item. Applies to F.js (JavaScript), Pro (WebForms), and FineUI.Core's MVC/RazorForms/RazorPages. (FineUI.Java starts at v16.0 with no historical upgrade path; only its shared F.js client breaking changes apply, see below.) Trigger phrases: "FineUI 升级", "升级 FineUI", "FineUI upgrade", "升级到 v1x", "破坏性变更", "不兼容", "迁移 FineUI", "EncodeText", "raw 标签", "DateParseString". Use this skill when the user wants to upgrade FineUI from an older version to a newer one, or asks "will the upgrade have any incompatibilities?".
Help developers use FineUI windows and message boxes: Window (inline content / iframe popup), opening/closing windows, iframe child page passing data back to the parent page (closeArgument), and MessageBox (Alert dialog / Confirm dialog / Notify box). Covers F.js (JavaScript), Pro (WebForms), FineUI.Core's MVC (Fluent API)/RazorForms/RazorPages (TagHelper), and FineUI.Java (Spring Boot + Thymeleaf dialect tags, kebab-case). Trigger phrases: "FineUI 窗口", "F.Window", "弹窗", "对话框", "MessageBox", "Alert.Show", "F.alert", "F.confirm", "确认框", "通知框", "Notify", "ShowNotify", "iframe 窗口", "关闭窗口", "回传数据", "closeArgument", "GetShowReference", "OnClose", "FineUI.Java", "Spring Boot", "Thymeleaf", "@FineUIPage", "f:window", "showAlert", "showNotify", "showConfirm", "ActiveWindow", "setHidden".
Runs a multi-step procedure as a Python DAG, so ordering, branching and retries are enforced by the runner rather than described in prose a model can generate past. Use for "run these steps in order and retry the flaky one until the check passes", "build a pipeline that fetches, validates, then skips the upload when nothing changed", "make sure these steps cannot be skipped", "resume from where it broke instead of redoing the expensive early stages", "run these independent calls at once and merge the results", or any procedure of 3+ steps with branches, input contracts, or side effects that must not block the critical path. Primitives are depends_on, when=, validate=, retry_until=, detached= and journal_path=. Not for a single sequential call, for steps needing reasoning between them that no predicate captures, or for async and distributed work. To audit whether one verification check can actually go red, use gating. To fan work out across many subagents, use a dynamic workflow.
Audit and improve Flutter accessibility, inclusive interaction, localization safety, and RTL behavior. Use for screen-reader semantics, focus and keyboard navigation, text scaling, contrast, touch targets, reduced motion, form errors, RTL, localization, or accessibility acceptance checks.
Data layer patterns for Flutter projects — DataSource interfaces and implementations, Repository, mapping DTOs to domain models, `fromJson` on freezed models, and reactive repositories built with `rxdart`'s `BehaviorSubject`. Triggered by phrases such as "create DataSource", "implement Repository", "repository", "local/remote data source", "BehaviorSubject", "stream repository", "DTO mapping", "fromJson".
How to set up get_it-based dependency injection in Flutter projects. Covers writing the `diSetup()` function, the registration order for DataSource/Repository/UseCase/ViewModel, choosing between singleton and factory, and the pattern of calling `getIt<T>()` in the Root widget. Be sure to use this skill when phrases such as "DI setup", "get_it", "registerSingleton", "registerFactory", "dependency injection", "register ViewModel", "diSetup", "getIt instance" come up.
Type-safe error handling patterns for Flutter projects — an `Error` marker interface, a freezed-based `Result<D, E>` sealed class, per-feature error enums, and handling success/failure with `switch` pattern matching. Triggered by phrases such as "Result wrapper", "error handling", "ResultSuccess", "ResultError", "NetworkError", "type-safe errors", "freezed sealed", "Result instead of exception".
Presentation layer patterns for Flutter projects — `ChangeNotifier`-based ViewModels, freezed `State` and sealed `Action`, separating Root/Screen widgets, observing with `ListenableBuilder`, and delivering one-off events through `StreamController`. Triggered by phrases such as "create ViewModel", "State/Action", "MVI", "ChangeNotifier", "separate Root and Screen", "onAction", "notifyListeners", "ListenableBuilder".
Flutter widget UI patterns — preferring StatelessWidget, `const` optimization, observing ViewModels with `ListenableBuilder`, `ListView.builder`/`IndexedStack`, reusing shared components, accessibility (Semantics), and handling dialogs and snack bars. Triggered by phrases such as "create widget", "create UI", "StatelessWidget", "ListView", "ListenableBuilder", "Scaffold", "snack bar", "dialog", "design token", "shared component".
Create distinctive, production-grade frontend UI with a bold, intentional aesthetic direction, purposeful layouts, meaningful motion, and strong accessibility. Prefer React + Next.js (TypeScript), but support vanilla HTML/CSS/JS when appropriate.
Frontend (including Electron desktop) performance optimization knowledge base, covering version-specific optimization knowledge for React 16-19, Angular 9-18+, and Electron 12-28+. Works together with the perf-workflow skill: perf-workflow drives the analysis process while this skill supplies frontend-specific quantitative standards, version-aware optimization strategies, bottleneck patterns, and tool references. Use when analyzing performance issues in Web frontend (React/Angular/Vue) or Electron desktop apps. Triggers — 「前端性能」「前端性能优化」「Electron 性能」 / frontend performance, frontend perf optimization, Electron performance.
Trigger: PRD, product requirements, definir producto, idear proyecto, armar spec de producto. Genera un PRD sección por sección conversando con el usuario — profundiza con preguntas, presenta alternativas cuando hay decisión real, y solo escribe `PRD.md` cuando cada sección está validada.
Fetch GitHub issues, understand their requirements, plan and implement the solution, then run verification—without committing, pushing, or creating a PR. Works one issue at a time: when several issues are named, or when no issue number is given at all (then it takes every open issue of the current repo as the queue), implement them sequentially so each one lands as its own commit and its own pull request, never bundled together. Use when someone says “work on issue #N”, “do #N”, “implement #N”, “fix issue #N”, “work through the open issues”, “do all the issues”, “dolgozz a #N-es issue-n”, “csináld meg a #12, #13 és #14 issue-kat”, “csináld meg az összes issue-t” or pastes GitHub issue URLs to implement. Not for an unattended run shipping a PR per issue (github-do-all-issues), or for creating, labeling or triaging issues (github-issues), or for committing and opening the PR (github-commit-pr, which runs once per issue afterwards). The user always reviews each issue's result and decides when to commit.
Installs and authenticates the GitHub CLI (gh) in a Claude.ai container, then runs gh commands against it. Use for "install gh", "gh auth", "create an issue or PR from the CLI", "gh is not authenticated", or any GitHub operation you want to issue as a gh command rather than a raw API call. This skill is the transport rather than the analysis. To understand what a repository does or contains, use exploring-codebases; to add a repo to the session, accessing-github-repos.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.
