Coding standards, frameworks, refactoring, and code review (18.1K skills)
Embed API emulators inside a Nuxt app with the Nuxt adapter. Add catch-all server routes, direct OAuth requests to same-origin emulator paths, and optionally persist emulator state across server restarts or cold starts.
Test integrations against a local emulator of the Vercel REST API. It supports common project, deployment, domain, environment variable, OAuth, API key, and Blob storage workflows, with seeded test data and Vercel-style responses.
Run local versions of AWS S3, SQS, Cognito, IAM, and STS to try application integrations without calling real AWS APIs. Configure sample data, exercise storage and queues, test sign-in and tokens, and check user, role, and temporary credential flows.
Run a stateful local Stripe API emulator to test customers, products, prices, checkout sessions, payment intents, and webhooks. Your app receives realistic Stripe SDK responses while all payment activity stays local and no real charges are made.
Test Twilio integrations against a local emulator that handles common messaging, verification, voice, Conversations, and webhook flows. It lets you exercise REST endpoints and SDK requests without contacting Twilio, while providing simulation routes for inbound messages and status callbacks.
Develop and test Slack integrations against a local API emulator. It models common workspace activity, including channels, messages, users, files, views, OAuth, and incoming webhooks, so you can check application behavior without sending requests to the real Slack API.
Embed API emulators in a Next.js App Router app and route requests through the same origin. The adapter helps test OAuth flows in preview deployments, configure emulator routes and fonts, and optionally persist emulator state across cold starts.
Start local emulators for services such as GitHub, Google, Slack, AWS, Stripe, and Linear. Seed them with test data, point an app at local endpoints, and use the emulators in automated tests or CI environments that lack network access.
Use a local, stateful version of Linear’s GraphQL API to test integrations without contacting Linear. Seed teams, workflow states, issues, comments, and OAuth apps, then exercise supported queries, mutations, webhooks, and basic agent-session flows.
Use a stateful local GitHub REST API emulator to develop and test integrations with repositories, issues, pull requests, OAuth, GitHub Apps, webhooks, Actions, and checks. Seed test data and exercise API behavior without calling GitHub’s live API.
Test Microsoft Entra ID sign-in and OAuth or OpenID Connect flows locally. The emulator supports authorization code, PKCE, and client credentials flows, issues test tokens, provides OIDC discovery, and returns user information through Microsoft Graph `/me` without calling Microsoft's live services.
Build a custom local emulator for a third-party HTTP API with emulate. Define routes, state changes, validation, seeds, and tests, run it alongside built-in services, and package the implementation for reuse by other projects. Requires Node 24 or later.
Test Resend email workflows with a local API emulator that captures messages for inspection instead of sending real email. Use it to check transactional messages, magic links or verification codes, and manage test domains, API keys, audiences, and contacts.
Test Google sign-in and integrations with Gmail, Calendar, and Drive against a local emulator. It supports OAuth and OpenID Connect flows, seeded test accounts and data, and API requests without contacting real Google services.
Emulate Sign in with Apple locally to test authorization code and PKCE flows, OIDC discovery, token exchange, user information, and token revocation. Seed test accounts and point your app to the emulator to check Apple sign-in behavior without calling Apple’s live APIs.
Implement and debug onetcli connection importers packaged as WebAssembly components. The skill covers parsing application settings, manifests and packaging, host integration, local visibility, password handling, and import preview issues.
Create GPUI UI components that follow the project’s existing implementation and Shadcn UI styling patterns. Choose a stateless or stateful design, keep the component API consistent with other elements, and add documentation and stories for the new component.
Implement and debug onetcli SSH connection importers that read OpenSSH config and known_hosts. Trace why previews return no records, check candidate file access and manifests, and match serialized authentication data to the host protocol’s expected JSON shape.
Use this skill while building or maintaining GPUI applications. It provides focused references for framework APIs and patterns, including keybindings, async tasks, state, events, layout, focus, custom elements, and tests.
Design, implement, review, or debug onetcli IPC database drivers. Work from the `driver.json` manifest and JSON-RPC protocol contract through schema metadata, SQL-building methods, import and export, tests, and packaging, with guidance that applies across implementation languages.
Prepare and review bilingual Chinese and English release notes for Navop. Maintain `CHANGELOG.md` as the source of truth, then check that tagged entries provide consistent content for GitHub Releases and the R2 updater manifest when a release is published or synchronized.
Build GPUI interfaces with gpui-component by choosing suitable controls, handling component state and themes, and following its design and coding guides. The references also cover layout, interaction states, interface copy, and application structure.
Plan or review desktop app architecture for macOS and Windows, with optional Linux support, when native behavior matters. It explains platform shells, embedded system WebViews, shared UI, typed communication, and practical pitfalls such as hidden-window performance and memory measurements.
Review an XQUIC agent harness for duplicated guidance, overlapping skill triggers, broken references, and missing automated checks. Get prioritized findings, policy decisions, proposed document or script changes, and a record of validation performed or still needed.