Loading...
Loading...
Found 2,732 Skills
Jira project management including issues, sprints, boards, and workflows. Activate for Jira tickets, sprint planning, backlog management, and Atlassian integration.
Generates production-ready API clients with TypeScript types, retry logic, rate limiting, authentication (OAuth, API keys), error handling, and mock responses. Use when user says "integrate API", "API client", "connect to service", or requests third-party service integration.
Stripe payment integration with Node.js SDK. Covers Checkout Sessions, Payment Intents, Subscriptions, Customer Portal, webhooks, and Stripe Elements. Use when implementing checkout flows, payment processing, subscription billing, webhook handlers, or payment forms with Stripe Elements. Use for stripe, payments, checkout, subscriptions, billing, webhooks, payment intents, stripe elements.
Manual QA testing — verify features end-to-end as a user would, using every tool available (browser, macOS, bash, APIs). Focuses on what formal test suites cannot capture: visual correctness, UX flows, usability judgment, integration reality, edge cases, and failure modes. Standalone or composable with /ship. Triggers: qa, qa test, manual test, test the feature, verify it works, exploratory testing, smoke test, end-to-end verification.
Uniwind (Tailwind CSS v4 for React Native) best practices, setup, theming, styling, and HeroUI Native integration. Use when writing, reviewing, or fixing Uniwind code. Triggers on: uniwind, className on RN components, global.css with @import 'uniwind', withUniwindConfig, metro.config.js setup, dark:/light: theming, platform selectors (ios:/android:/native:/web:), data selectors, responsive breakpoints, CSS variables, useUniwind, withUniwind, useResolveClassNames, useCSSVariable, tailwind-variants, HeroUI Native with Uniwind, Uniwind Pro (animations, shadow tree, transitions), NativeWind migration. Also triggers on setup troubleshooting: "check my config", "styles not working", "className not applying", "audit Uniwind setup".
Master third-party API integration in ANY language with best practices and patterns
Use when adding payments, billing, checkout, subscriptions, invoices, webhooks, customer portal, Stripe Connect, metered/usage billing, tax, fraud/Radar, pricing page, payment intents, refunds, coupons, promo codes, or any Stripe integration in Next.js. Triggers: stripe, payment, checkout, subscribe, billing, invoice, webhook, portal, connect, marketplace, payout, metered, usage-based, SaaS pricing, paywall, plan, tier.
Complete full-stack development with Next.js 13+, React, Firebase, Tailwind CSS, and payment integration (Stripe, JazzCash, EasyPaisa). Build production-ready e-commerce platforms, SaaS applications, and scalable web applications. Comprehensive coverage of frontend architecture, backend API routes, database design, authentication systems, payment processing, form handling, error management, and optimization. Generate complete project structures, pages, components, API routes, database schemas, security rules, and deployment configurations using TypeScript.
Use this skill when spreadsheet files are the primary input or output. This means the user wants to: open, read, edit, or repair existing .xlsx, .xlsm, .csv, or .tsv files (e.g., add columns, calculate formulas, format, create charts, clean messy data); create new spreadsheets from scratch or from other data sources; or convert between spreadsheet file formats. Trigger this especially when the user references a spreadsheet file by name or path—even casually (such as "the xlsx in my downloads")—and wants to process it or generate content from it. It's also used to clean or reorganize messy tabular data files (rows with incorrect formatting, misaligned headers, garbage data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do not trigger this when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Run integration tests for component interactions
Analyze project briefs to resolve architectural ambiguity before tech stack selection. Determines greenfield vs brownfield, platform constraints, integration requirements, scale expectations, and team context. Produces architecture-context.json for downstream skills.
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.