Przydatne Agent Skills ocenione według realnego użycia

You MUST use this when configuring, writing, debugging, running, migrating, or auditing Vitest tests in JavaScript/TypeScript projects - Vite, Vue, Nuxt, React, Next.js, Node libraries, workspaces, coverage, mocks, snapshots, flaky tests, CI parity, or Jest migration.

Instalacje / 1h: 5
GitHub Stars: 6
Aktualizacja: 1 lis

web-debug

You MUST use this when interacting with or testing local web applications with Playwright - verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser console logs.

Instalacje / 1h: 5
GitHub Stars: 6
Aktualizacja: 1 lis

Apache-2.011 Pliki

webapp-debugger

Experimental. User-invoked via /webapp-debugger only. Debugs and verifies a local web app through the agent-browser CLI - opens pages, interacts by accessibility refs, and collects console, page errors, network, and screenshots as evidence.

Instalacje / 1h: 5
GitHub Stars: 6
Aktualizacja: 1 lis

MIT3 Pliki

clayzo

clayzo-animation-authoring

Author or edit Clayzo animation documents and interactive animated components with the typed authoring package. Use for motion design, product microinteractions, pointer behavior, loops, 2.5D camera work, glass, dithering, custom shaders, previewing, and revision-bound self-review.

Instalacje / 1h: 5
GitHub Stars: 3
Aktualizacja: 28 paź

24 Pliki

clayzo

clayzo-animation-shipping

Ship an existing Clayzo animation as a web playback artifact, in an iOS or macOS app, or as rendered media. Use for renderer selection, React or Next integration, SwiftUI, assets and fonts, deployment, export preflight, loop verification, and approval of the exact revision being released.

Instalacje / 1h: 5
GitHub Stars: 3
Aktualizacja: 28 paź

6 Pliki

cr-received

You MUST use this when findings from a code review, pull request comments, CI or static-analysis output, or reviewer suggestions need a decision before any fix - a cr-request result, a spec or plan review, or a reviewer's message - in any programming language. Verifies each finding against the current tree, decides accept, reject, partial, defer, or escalate with evidence, fixes only what holds up, records the decisions in the plan's execution record or the spec's verification record, commits ea

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

MIT8 Pliki

cr-request

You MUST use this when a change needs an independent review before it moves on - a finished task, a feature branch, a pull request, work-in-progress or uncommitted changes since a given ref, or a spec or plan document that needs review - in any programming language. Replaces devflow review-request. Pins the exact target and its tree fingerprint, gathers intent and constraints, and dispatches a read-only reviewer that returns separate verdicts and evidence-backed findings.

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

finalize

You MUST use this when verified work awaits a decision on how it leaves the branch - merging it, pushing it, opening a pull request (PR), keeping the branch, discarding the branch, or cleaning up a worktree or workspace - in any repository. Not for work that is not verified yet (verify), open review findings (cr-received), a plain commit with no integration decision, or release work with its own checklist. Replaces devflow branch-finish.

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

implement

You MUST use this when an existing implementation plan is to be executed, either directly in the current session or through subagents, including resuming an interrupted execution from the plan's execution record, or when one or two edits with an obvious approach need doing without a plan. Covers task-by-task execution with evidence, drift handling and blockers, and a resumable execution record. Replaces devflow inline-plan-dev and subagent-plan-dev. Not for writing a plan (plan-craft), checking

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

MIT9 Pliki

plan-craft

You MUST use this when a spec the user approved, an accepted design, or requirements already agreed in the conversation have to be turned into an ordered, multi-step implementation plan before any code is written - including a spec from specify, work with no spec yet, and a plan revision after a document review. Replaces devflow plan-crafting. Covers whether a plan is needed, task order, acceptance-criteria coverage, and the execution choice. Not for open design (specify) or executing a plan (im

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

MIT4 Pliki

resolve-issue

You MUST use this when the user asks to take a GitHub issue through the agentflow workflow, with manual stage approvals or a single --auto invocation. Owns intake, clarification, planning, implementation, review, handoff and resumable orchestration. Delivery consumes the installed owner's G3 helpers through explicit current project callbacks and proofs; unknown delivery contracts block their actions. Not for writing a standalone spec, executing an existing plan without issue orchestration, or by

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

session-learnings

You MUST use this when lasting learnings from the current session should be recorded for future agents - pitfalls hit, mistakes the user corrected, conventions found, or commands that finally worked, whatever the conversation language - including when the user asks to write down what the session taught and at the end of the agentflow chain after finalize. Records them without asking in the project's gitignored docs/session-learnings/AGENTS.md; on a separate request, triages the accumulated notes

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

MIT6 Pliki

specify

You MUST use this when work has to be designed before any code is written - a new feature, a product, UX, or architecture change, unclear success criteria, or a choice between materially different approaches - including a spec revision after a document review. Turns the request into an evidence-backed spec with checkable acceptance criteria behind an explicit approval, then starts plan-craft. Replaces devflow scope-triage. Not for a fully specified mechanical change or a fix whose expected behav

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

MIT4 Pliki

verify

You MUST use this when anyone - you, a subagent, or the user - is about to state that work is done, fixed, ready, or mergeable, and before a merge, opening a pull request, or a handoff report, including work that has no plan. Covers every promise behind the claim - spec criteria, plan tasks, record entries, accepted review fixes, and the caller's words - proven with fresh checks on the committed tree and given one verdict, without editing code. Not for fixing failures (implement) or reviewing (c

Instalacje / 1h: 5
GitHub Stars: 4
Aktualizacja: 1 lis

MIT8 Pliki

ejirocodes

svelte5-best-practices

Svelte 5 runes, snippets, SvelteKit patterns, and modern best practices for TypeScript and component development. Use when writing, reviewing, or refactoring Svelte 5 components and SvelteKit applications. Triggers on: Svelte components, runes ($state, $derived, $effect, $props, $bindable, $inspect), snippets ({snippet}, {@render}), event handling, SvelteKit data loading, form actions, Svelte 4 to Svelte 5 migration, store to rune migration, slots to snippets migration, TypeScript props typing,

Instalacje / 1h: 5
GitHub Stars: 6
Aktualizacja: 25 cze

MIT8 Pliki

agents365-ai

drawio-skill

Create and edit draw.io/diagrams.net diagrams as editable .drawio files. Covers architecture, UML/ERD/sequence, BPMN, network, and swimlane views authored from a description or converted from code, IaC, SQL, and API schemas, plus sync, query, test, review, export, and publish of existing diagrams. Use when the user asks for draw.io/diagrams.net or an editable diagram; prefer Mermaid/PlantUML when diagrams-as-code is enough.

Instalacje / 1h: 5
GitHub Stars: 10,5 tys.
Aktualizacja: 1 lis

MIT79 Pliki

danyuchn

asd-ste100

Use when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and misreading has a real cost, or when text reads as dense, hedged, or easy to misparse. Triggers: disambiguate, STE100 rewrite, apply Simplified Technical English, plain-language rewrite, controlled-language rewrite, rewrite so an agent cannot misread this. Not for creative or marketing copy.

Instalacje / 1h: 5
GitHub Stars: 5,9 tys.
Aktualizacja: 2 lis

MIT9 Pliki

mickadesign

fluid-functionalism

Build React UIs with Fluid Functionalism — a shadcn/ui registry (@fluid) of animated components with a shared motion system: three spring speeds, a hover highlight that glides from item to item under the cursor, labels that change weight without layout shift. Use whenever the user mentions Fluid Functionalism, @fluid, or fluidfunctionalism.com, asks for UI with satisfying/fluid/polished motion in a React, Next.js, shadcn, Radix, or Base UI project, builds any interface (settings dialogs, sidebar

Instalacje / 1h: 5
GitHub Stars: 1,1 tys.
Aktualizacja: 2 lis

MIT9 Pliki

wind-alice

wind-alice

调用万得 Alice Agent（A2A 协议，SSE 流式）执行指定 Skill 并获取分析结果的 CLI 工具。当用户要求"用 Alice 跑某个 Skill"、"出一份某公司的调研问题清单"、"做一页纸投资备忘"、"核验一段金融信息"等需要点名 Alice 子 Skill 的场景使用。

Instalacje / 1h: 5
GitHub Stars: 147
Aktualizacja: 30 paź

7 Pliki

capacitor-angular

Guides the agent through Angular-specific patterns for Capacitor app development. Covers project structure, adding Capacitor to Angular projects, using Capacitor plugins in Angular services and components, NgZone integration for plugin event listeners, lifecycle hook patterns, dependency injection, routing with deep links, and environment-based platform detection. Do not use for creating a new Capacitor app from scratch, upgrading Capacitor versions, installing specific plugins, Ionic Framework

Instalacje / 1h: 5
GitHub Stars: 54
Aktualizacja: 20 paź

MIT1 Pliki

capacitor-app-creation

Guides the agent through creating a new Capacitor app from scratch. Covers project scaffolding with the Capacitor CLI, configuring the app (appId, appName, webDir), adding native platforms (iOS, Android), and syncing. Includes decision points for Ionic Framework integration, live updates, and CI/CD setup. Do not use for upgrading existing Capacitor apps, migrating from other frameworks, or plugin installation.

Instalacje / 1h: 5
GitHub Stars: 54
Aktualizacja: 20 paź

MIT1 Pliki

capacitor-app-development

Guides the agent through general Capacitor app development topics. Covers core concepts (native bridge, plugins, web layer), Capacitor CLI usage, app configuration (capacitor.config.ts, splash screens, app icons, deep links), platform management (Android, iOS, Electron, PWA), edge-to-edge and safe area handling on Android, live reload setup, storage solutions, file handling, security best practices, CI/CD references, iOS package managers (SPM, CocoaPods), and troubleshooting for Android and iOS.

Instalacje / 1h: 5
GitHub Stars: 54
Aktualizacja: 20 paź

MIT19 Pliki

capacitor-app-spm-migration

Guides the agent through migrating an existing Capacitor app project from CocoaPods to Swift Package Manager (SPM) for iOS dependency management. Covers prerequisite checks, inventorying installed Capacitor plugins, backing up customized iOS project files (Info.plist, AppDelegate.swift, Assets.xcassets, Base.lproj, App.entitlements, GoogleService-Info.plist, .xcconfig files, signing configuration), deleting the existing ios/ folder, re-scaffolding with npx cap add ios --packagemanager SPM, resto

Instalacje / 1h: 5
GitHub Stars: 54
Aktualizacja: 20 paź

MIT1 Pliki