개발 스킬

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing Vercel API integrations locally
• Trying project and deployment workflows
• Checking Vercel OAuth authorization and token exchange

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing outbound messages and verification codes locally
• Simulating inbound SMS and delivery status callbacks
• Checking Twilio SDK integrations without live requests

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing a checkout flow locally
• Trying payment intents without real charges
• Checking webhook handling for Stripe events

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing Linear issue and comment integrations
• Trying Linear OAuth flows locally
• Checking webhook payload handling

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Embedding GitHub or Google emulators in Nuxt
• Configuring same-origin OAuth for preview deployments
• Adding emulator catch-all server routes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing transactional email flows without delivery
• Checking magic link and verification code emails
• Inspecting captured email content in the inbox

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing Microsoft sign-in without a live identity tenant
• Checking PKCE and token exchange flows locally
• Trying OIDC discovery and Microsoft Graph /me requests

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing repository and issue integrations locally
• Trying OAuth sign-in with seeded users
• Checking GitHub App and webhook flows

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running local replacements for developer APIs
• Seeding test users, projects, and OAuth clients
• Testing integrations in CI without network access

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding emulator routes to a Next.js app
• Testing OAuth callbacks on Vercel previews
• Configuring Auth.js or NextAuth.js for local emulators

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing Apple sign-in in a local app
• Checking OIDC discovery and ID token handling
• Trying token exchange and refresh flows

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing S3 uploads and downloads locally
• Trying SQS message workflows without AWS
• Testing Cognito sign-up, sign-in, and tokens

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing Google sign-in and OAuth callbacks locally
• Checking OpenID Connect discovery and token exchange
• Testing Gmail messages, drafts, threads, and labels

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a local emulator for a vendor API
• Modeling stateful endpoints and custom seed data
• Packaging and testing a reusable emulator plugin

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing a Slack bot's messages and channel workflows
• Trying OAuth sign-in and token exchange locally
• Checking incoming webhooks and app views

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing layers for a cross-platform desktop app
• Investigating WebView flicker, stutter, or hidden-window freezes
• Planning typed communication across app components

Use the `gh` command-line tool to inspect GitHub issues, pull requests, and CI workflow runs. Check status and failure logs, retrieve specific repository data through the API, and filter structured JSON output for focused results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a pull request’s CI status
• Finding failed steps in a workflow run
• Listing recent repository workflow runs

Stage, commit, and push XQUIC changes with scoped Git checks. Review staged and unstaged files, confirm the branch and resolved remote target, preserve unrelated work, and follow repository commit conventions before publishing a branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Stage only the intended files
• Commit changes using repository conventions
• Check the push target before publishing a branch

Prepare and update concise pull request titles and bodies for alibaba/xquic, following its contribution format. Check that the summary matches the current code and validation evidence, create draft PRs from pushed branches, and verify state before moving a complete PR toward review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Formatting an alibaba/xquic pull request
• Updating a PR summary after new code is pushed
• Creating a draft PR from a pushed branch

Prepare and run a local XQUIC build on macOS or Linux. The skill checks the platform and build options, then uses the repository validation script to compile targets and report the build setup and any failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compile XQUIC locally
• Check whether the current platform supports the build script
• Choose a feature profile or TLS backend

Prepare a focused XQUIC bug report with reproducible steps, comparable expected and actual behavior, and an exact RFC or draft reference. It submits the report only after the separate issue-check workflow verifies the claim and other submission gates are clear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a reproducible XQUIC bug report
• Check a protocol claim before submitting it
• Prepare an RFC-linked issue for GitHub

Check whether a proposed XQUIC bug is supported by an applicable RFC or Internet-Draft and the current source behavior. The skill traces evidence, compares expected and actual logic, and returns a fail-closed decision that can gate issue submission.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify an XQUIC issue draft before submission
• Investigate a claimed QUIC or HTTP/3 protocol violation
• Check a QPACK or MoQT behavior claim

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Audit harness design after changing agent instructions
• Find overlapping triggers across skills
• Check harness references and validation gaps

Handle actionable review feedback on XQUIC GitHub pull requests. Classify comments, inspect the relevant code and callers, make the smallest needed edits, and report whether each item was fixed, already addressed, needs a decision, or could not be verified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Address requested changes on a pull request
• Review unresolved inline comment threads
• Triage stale, informational, or blocked feedback