Skills
18,283 skills, most installed first.
Browse
tddpproencaTest-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing test-first approaches. Triggers on "write tests first", "test before code", "red green refactor", "test driven development". This skill does NOT cover Vitest framework specifics (use vitest skill) or API mocking with MSW (use msw skill).terminal-uipproencaTerminal User Interface (TUI) performance and UX guidelines for TypeScript applications using Ink and Clack. This skill should be used when building CLI tools, interactive terminal prompts, or developer tooling with TUI components. Triggers on tasks involving TUI components, CLI prompts, terminal rendering, keyboard input handling, or developer tooling.typescript-refactorpproencaTypeScript and TSX refactoring and modernization guidelines from a principal specialist perspective, current to TypeScript 6.0 and React 19. This skill should be used when refactoring, reviewing, or modernizing TypeScript or React/TSX code for type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving type architecture, narrowing, generics, discriminated unions, error handling, React component and hook typing, or migration to modern TypeScript features (satisfies, usiui-designpproencaUI/UX and frontend design best practices guidelines (formerly frontend-design). This skill should be used when writing, reviewing, or designing frontend code to ensure accessibility, performance, and usability. Triggers on tasks involving HTML structure, CSS styling, responsive layouts, form design, animations, or accessibility improvements.wxt-browser-extensionspproencaWXT browser extension performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring WXT browser extension code to ensure optimal performance patterns. Triggers on tasks involving WXT, browser extensions, content scripts, service workers, messaging, and extension APIs.zustandpproencaZustand state management best practices for React applications. Use when writing, reviewing, or refactoring Zustand stores to ensure optimal performance and maintainability. Triggers on tasks involving state management, stores, selectors, re-renders, and Zustand patterns.word-documentpracticalswanWord (.docx) manipulation via MCP server. Use for reading, creating, editing, formatting Word documents including tables, footnotes, comments, images, headers, styles, and PDF conversion.boxprathamdbybox when cloning, updating, listing, or searching an external git repository from its real local source.commitprathamdbycommit when saving scoped git changes with a message derived only from the committed diff, especially after tickets or reviews could bias the wording.deslopprathamdbydeslop when removing AI-generated bloat, needless defenses, foreign patterns, or avoidable complexity from a git diff without changing behavior.handoffprathamdbyhandoff when saving resumable session state or continuing work from an existing handoff document.make-prprathamdbymake-pr when publishing committed branch changes as a new pull request or updating the existing pull request for that branch.peer-reviewprathamdbypeer-review when deciding whether an implementation plan, design, or proposed change is ready to build.prath-modeprathamdbyprath-mode when routing goal-shaped work to a playbook that sequences prathamdby/skills leaves, including multi-step delivery chains.paper2codeprathamlearnstocodeConverts an arxiv paper into a minimal, citation-anchored Python implementation. Trigger when user runs /paper2code with an arxiv URL or paper ID, says "implement this paper", or pastes an arxiv link asking for implementation. Flags all ambiguities honestly. Never invents implementation details not stated in the paper.cinematic-script-writerpraveenspeaksapple-asoprisma-labs-devOptimize Apple App Store metadata in store.config.json for ASO (App Store Optimization). Use when working with store.config.json, App Store keywords, titles, subtitles, descriptions, or localizing app metadata. Helps maximize app visibility and downloads.apple-docs-indexprisma-labs-devIndex of Apple developer documentation for iOS, macOS, and related frameworks. Use when looking up what APIs exist in a framework, browsing available documentation, or deciding what docs to fetch. Covers SwiftUI, UIKit, Core Animation (QuartzCore), XCTest, HealthKit, Combine, SwiftData, and more.backgroundtasksprisma-labs-devAPI reference: BackgroundTasks. Query for BGTaskScheduler, app refresh, background processing.combineprisma-labs-devAPI reference: Combine. Query for publishers, subscribers, operators, async data streams.corehapticsprisma-labs-devAPI reference: Core Haptics. Query for CHHapticEngine, haptic patterns, tactile feedback.eventkitprisma-labs-devAPI reference: EventKit. Query for EKEventStore, EKEvent, EKReminder, calendar access.guide-macos-spm-packagingprisma-labs-devScaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.guide-swiftui-performance-auditprisma-labs-devAudit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.healthkitprisma-labs-devAPI reference: HealthKit. Query for HKHealthStore, HKQuantitySample, workouts, health data read/write.higprisma-labs-devFact lookup: Apple Human Interface Guidelines corpus (greppable markdown). Query on demand for accessibility and ergonomic minimums (hit-target sizes, Dynamic Type), platform terminology, system component capabilities, and App-Review-relevant conventions. Not design direction.ios-devprisma-labs-devStart here for any iOS or SwiftUI task. Coordinates best-practice guides, correctness checks, and full Apple API references. Use before navigating to other Apple skills — for building, reviewing, refactoring, or debugging iOS apps.ios-liquid-glassprisma-labs-devAPI reference: Liquid Glass (iOS 26+). Query for glass effects, navigation patterns, GlassEffect modifiers, design principles.mapkitprisma-labs-devAPI reference: MapKit for SwiftUI. Map view, Marker, Annotation, camera positions, map features.photosuiprisma-labs-devAPI reference: PhotosUI. Query for PhotosPicker, PHLivePhotoView, photo selection.storekitprisma-labs-devAPI reference: StoreKit 2. Product, Transaction, subscriptions, StoreView, SubscriptionStoreView.swift-concurrencyprisma-labs-devAPI reference: Swift Concurrency. async/await, Task, TaskGroup, actors, AsyncSequence, AsyncStream, continuations.swift-testingprisma-labs-devAPI reference: Swift Testing framework. @Test, @Suite, #expect, #require, traits, parameterized tests, migrating from XCTest.swiftdataprisma-labs-devAPI reference: SwiftData. Query for @Model, ModelContext, @Query, schema migrations.swiftuiprisma-labs-devAPI reference: SwiftUI. Query for views, layouts, navigation, @State/@Binding/@Observable, view modifiers, NavigationStack, iOS 26+ features.tipkitprisma-labs-devAPI reference: TipKit. Tip protocol, TipView, PopoverTipView, Tips.configure, inline and popover tips.uikitprisma-labs-devAPI reference: UIKit. Query for UIView, UIViewController, controls, table and collection views, navigation controllers, scenes, Auto Layout, images, colors, gestures, presentation, and SwiftUI hosting.usernotificationsprisma-labs-devAPI reference: UserNotifications. Query for local/remote notifications, triggers, notification content.widgetkitprisma-labs-devAPI reference: WidgetKit. Query for widget timelines, entries, providers, home/lock screen widgets.xcuitestprisma-labs-devAPI reference: XCUITest. Query for element queries, waiting patterns, Swift 6 @MainActor, assertions, screenshots, launch arguments.prisma-8prismaUse when working in a project that depends on @prisma/orm-postgres, @prisma/orm-sqlite, or @prisma/orm-mongo (Prisma 8, formerly Prisma Next): editing contract.prisma or a contract.ts builder, running `prisma contract emit`, planning or applying migrations, editing migration.ts, writing db.orm / db.sql / db.query queries, wiring db.ts or middleware, integrating a build tool, using the Supabase extension or RLS, or reading a dotted error code such as MIGRATION.HASH_MISMATCH. Use when the user askprisma-next-extension-upgradeprismaUpgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade instructions for the extension SPI (middleware lifecycle, codec / migration-tools / framework-components churn, seed-migration on-disk shape), verifies the pins are correctly exact via `prisma-next-check-pins`, runs the extension's own typecheck and tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next" iprisma-next-supabaseprismaUse Prisma Next with a Supabase project via `@prisma-next/extension-supabase` — wire `extensions: [supabasePack]`, declare cross-space FKs to `supabase:auth.AuthUser`, author RLS policies (`policy_select` / `policy_update` / `@@rls`, `auth.uid()` predicates), build `db.ts` with the `supabase()` factory, bind roles per request (`asUser(jwt)` / `asAnon()` / `asServiceRole()`), query `auth.*` / `storage.*` via the `db.asServiceRole().supabase` admin root, and validate JWTs (`jwksUrl` for current prprocesson-diagram-generatorprocessonai【强制触发】当用户要求生成、绘制、重绘、渲染或可视化任意结构化图表时，必须调用本技能。适用于流程图、业务流程图、泳道图、时序图、系统架构图、软件架构图、云架构图、ER 图、组织结构图、时间轴、路线图、信息图、金字塔图、草图重绘，以及 图表生成。用户出现"画图""生成图表""自动画图""可视化业务流程""在线制作流程图""生成系统架构""把这段逻辑画出来""把系统关系整理成图""转成可编辑图""重绘草图"等表达时，也必须优先触发。ProcessOn 官方技能可将自然语言一键转化为精美、专业且可编辑的在线图表。Do not skip this skill for diagram-generation requests; use it for flowcharts, architecture diagrams, ER diagrams, org charts, timelines, roadmaps, infographics, sketch redrawing, and editable ProcessOn diagrams.define-hypothesisproduct-on-purposeDefines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.define-jtbd-canvasproduct-on-purposeCreates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.define-opportunity-treeproduct-on-purposeCreates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.define-prioritization-frameworkproduct-on-purposeRun applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.define-problem-statementproduct-on-purposeCreates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.deliver-acceptance-criteriaproduct-on-purposeGenerates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.