개발 스킬

Create a shared API contract that defines endpoint routes, request and response schemas, TypeScript interfaces, pagination, and error formats. It helps frontend and backend agents implement against the same agreed specification.

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

• Defining request and response schemas for a new endpoint
• Aligning frontend and backend work around one API specification
• Standardizing pagination and error responses across endpoints

Set up local development for Apify Actors, programs that automate data collection. Create a project, define inputs, run it with the Apify CLI, and inspect stored results while repeating edits and tests before deployment.

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

• Creating an Actor project from a template
• Running repeated tests with a saved input file
• Inspecting collected data in local storage

Troubleshoot common Apify Actor and API failures by matching the exact error signature to a catalog entry. Get likely causes, copyable fixes, and commands to verify recovery for authentication, rate limits, builds, proxies, payloads, and anti-bot blocks.

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

• Diagnosing a failed or timed-out Actor run
• Understanding an Apify API status code
• Investigating proxy or anti-bot failures

Learn the basic Apify integration pattern: call a public Actor, wait for its run to finish, check its status, and retrieve scraped records from the default dataset using apify-client.

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

• Trying a first Apify Actor run
• Checking Apify API connectivity
• Retrieving scraped records from a dataset

Manage Apify API request limits during bulk operations by tuning retries, batching dataset writes, and queuing calls. It helps build integrations that control request frequency and respond to rate-limit headers.

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

• Troubleshooting repeated Apify API 429 errors
• Batching large dataset uploads
• Controlling concurrent API reads

Use these TypeScript patterns to build Apify Actors with Crawlee or call Actors through apify-client. Examples cover crawler choice, datasets and key-value stores, proxies, typed wrappers, and handling failed requests without stopping a crawl.

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

• Choosing Crawlee for static or JavaScript-heavy pages
• Building an Actor with request error handling
• Reading Actor datasets from an application

Set up the Apify tools needed for a project: the client for calling Actors, the SDK for building them, Crawlee for crawling, or the CLI for deployment. Configure an API token and verify that the connection works.

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

• Starting a new Apify project
• Choosing packages to call or build Actors
• Configuring an Apify API token

Design Apify data collection systems using a standalone scraper, a multi-stage pipeline, or an application integration. Get directory layouts, TypeScript skeletons, input validation, configuration patterns, and health checks suited to the chosen structure.

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

• Designing a standalone Apify scraper
• Connecting discovery, scraping, and cleanup stages
• Integrating Apify data into an application

Set up the official Anthropic SDK for Python or TypeScript, configure the ANTHROPIC_API_KEY environment variable, and make a small Messages API request to check authentication. Includes package installation steps and notes for proxy and deployment environments.

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

• Starting a Python Claude API project
• Adding Claude SDK authentication to a TypeScript service
• Checking that an API key works

Assess whether an Anima and Figma design-to-code pipeline is ready for production. Review credentials, source traceability, generated-code and visual checks, monitoring, and rollback evidence, then produce a go/no-go record for release owners.

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

• Preparing a Figma-to-code pipeline for launch
• Checking generated components before release
• Rehearsing rollback for a design automation service

Build Claude assistants that call functions or APIs through the Messages API. Define tools with JSON inputs, execute returned tool requests in your code, send results back to Claude, and control repeated calls with a bounded agent loop.

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

• Connecting Claude to a weather or database API
• Building a support assistant that looks up orders
• Returning function results to Claude

Convert an authorized website into React or HTML code with Anima, then adapt the generated files to your project. Apply customization rules, map colors and spacing to shared design values, and organize components and styles for review.

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

• Turning an authorized website into React code
• Adapting generated code to project conventions
• Mapping colors and spacing to design system values

Upgrade Anima SDK integrations or move manual Figma exports into automated code generation. Compare generated files against a baseline, validate changes in staging, and document the package version, test results, and rollback reference.

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

• Upgrading to a reviewed Anima SDK version
• Automating manual Figma plugin exports
• Checking generated code changes after an upgrade

Analyze PostgreSQL or MySQL index usage and query patterns to find missing, unused, and overlapping indexes. Get prioritized CREATE or DROP recommendations with estimated storage impact and trade-offs between faster reads and added write overhead.

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

• Finding indexes behind slow database queries
• Reviewing unused indexes before cleanup
• Choosing column order for composite indexes

Build a review-driven pipeline that scans approved Figma components, generates React code with the Anima SDK, and detects design changes. It confines generated files to approved paths and prepares a change for review before code is accepted.

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

• Automating handoff from Figma components to React
• Generating code for an approved design system
• Detecting Figma revisions and preparing review changes

Plan and carry out a controlled migration of an Algolia JavaScript client from v4 to v5. Inventory package versions and API usage, update method calls and waits against the installed types and official migration guidance, run compatibility checks, and document remaining gaps and rollback steps.

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

• Finding v4 client calls and mixed package versions
• Migrating initIndex and related method usage
• Checking compatibility and preparing a rollback

Generate React or HTML from a selected Figma frame using the Anima SDK. Explore styling options, inspect the generated files, and check formatting, types, dependencies, and appearance before bringing the code into an existing project.

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

• Try code generation from a single Figma frame
• Compare React and HTML output settings
• Inspect generated filenames and component structure

Implement and validate Algolia search interaction events such as clicks, conversions, and views, while keeping them distinct from database-to-index updates. Use it to define event identity and consent handling, then check retries, duplicates, and reconciliation behavior.

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

• Adding Algolia Insights click and conversion tracking
• Attributing search interactions with query IDs
• Building a separate database-to-index sync flow

Manage rate limits when generating code from Figma designs with Anima. Set bounded waits and retries, track successful and failed nodes, and resume only the failed work, using the account’s documented quota instead of assumed limits.

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

• Batch code generation for design components
• Handle Figma rate limit responses
• Resume only failed generation items

Build a backend API that uses the Anima SDK to generate code from approved Figma files and nodes. The skill covers an Express wrapper and deployment options such as Vercel serverless functions and Cloud Run, with access and secret safeguards.

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

• Deploying an internal design-to-code API
• Generating code from approved Figma nodes
• Running Anima as a serverless function

Create a focused JSON diagnostic bundle for Anima SDK or Figma integration failures. It records SDK and Node.js versions, token presence without token values, and connectivity status, so you can review and redact evidence before attaching it to a support request.

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

• Preparing reviewed diagnostic evidence for an Anima support ticket
• Checking whether a staging Figma connection is reachable
• Investigating an Anima SDK loading or code generation failure

Examine an application's network requests and their latency to locate communication bottlenecks. Get practical recommendations such as parallel requests, batching, connection reuse, or timeout adjustments to improve API and page load performance.

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

• Finding slow API requests
• Reducing page load delays
• Reviewing serial requests for parallel work

Investigate slow queries in PostgreSQL, MySQL, and MongoDB using execution plans, which show how queries run, and performance metrics. Produce index suggestions, query rewrites, and configuration recommendations ranked by likely impact and implementation effort.

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

• Investigating slow dashboard queries
• Reviewing missing and unused indexes
• Finding repeated queries on list pages

Build a workflow that uses Figma webhooks, notifications sent when designs change, to queue Anima code generation. Handle approved sources, duplicate events, retries, and rate limits, with approval required before generated code is merged or deployed.

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

• Regenerating components when a Figma version is saved
• Connecting design updates to a CI workflow
• Handling duplicate events and failed generation