1.1천건 · 관련도순
Collect and analyze on-device performance metrics and crash diagnostics using MetricKit. Use when setting up MXMetricManager, handling MXMetricPayload or MXDiagnosticPayload, processing crash/hang/disk-write diagnostics via MXCallStackTree, adding custom signpost metrics, or uploading telemetry to an analytics backend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify device legitimacy and app integrity using DeviceCheck (DCDevice per-device bits) and App Attest (DCAppAttestService key generation, attestation, and assertion flows). Use when implementing fraud prevention, detecting compromised devices, validating app authenticity with Apple's servers, protecting sensitive API endpoints with attested requests, or adding device verification to a backend architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up and configure WorkOS AuthKit authentication with Convex backend. Use when integrating AuthKit, configuring JWT providers, setting up environment variables, or implementing sign in and sign out flows with React and Vite. Supports Netlify deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements security controls at the API gateway layer including authentication enforcement, rate limiting, request validation, IP allowlisting, TLS termination, and threat protection. The engineer configures API gateways (Kong, AWS API Gateway, Azure APIM, Apigee) to act as a centralized security enforcement point that validates, throttles, and monitors all API traffic before it reaches backend services. Activates for requests involving API gateway security, API management security, gateway a...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides web exploitation techniques for CTF challenges. Use when the target is primarily an HTTP application, API, browser client, template engine, identity flow, or smart-contract frontend/backend surface, including XSS, SQLi, SSTI, SSRF, XXE, JWT, auth bypass, file upload, req
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tests APIs for injection vulnerabilities including SQL injection, NoSQL injection, OS command injection, LDAP injection, and Server-Side Request Forgery (SSRF) through API parameters, headers, and request bodies. The tester crafts malicious payloads targeting different backend technologies and injection contexts to extract data, execute commands, or access internal services. Maps to OWASP API8:2023 Security Misconfiguration and API7:2023 SSRF. Activates for requests involving API injection te...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates TanStack Query hooks for API features with authentication. Use when connecting frontend to backend endpoints, creating data fetching hooks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy a new LLM model via LiteLLM (GitOps) and/or Azure (Terraform + node backend), add it to the ai toolkit, create the required pull requests, and verify end-to-end. Use when rolling out a model to any environment, adding a model to the toolkit, troubleshooting "model not available" errors, or finding pricing/token limits/model ids for any provider.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for the infrastructure implementation phase after the backend follows the model — turning documents/infra-design decisions into infra/ (local container stack, production IaC), wiring cradle.json infra.up / infra.containers, adding IaC validate and image build steps to CI, and, once E2E passes, applying production once in a sandbox and recording it in the deployment table. Not for designing infrastructure (infra-design).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after the Lean model changed and before touching backend code — regenerates Kotlin from Lean, lists changed generated symbols, the hand-written files and contract tests that reference them, and golden regressions, so the blast radius is known before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or changing REST endpoints or the OpenAPI contract — deriving endpoints from the Lean commands and views, writing documents/codebase/openapi.yaml first, then regenerating the backend controller interfaces and the frontend client.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
バックエンド実装時に使用。DRY原則遵守。コーディング規約準拠。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go バックエンド開発ワークフロー全体のガイド。「Go」「バックエンド」「API サーバー」「golang」などのキーワードで自動適用。ビルド・テストはサブエージェント、品質・メンテナンスはスキルを推奨。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, refine, implement, or review application UI and user journeys with minimal controls, clear actions, shared components, realistic prototypes, and polished behavior. Use for product screens, forms, onboarding, navigation, settings, and chat/task interfaces; not backend-only work or general graphic design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds vendor-agnostic detection rules using the Sigma rule format for threat detection across SIEM platforms including Splunk, Elastic, and Microsoft Sentinel. Use when creating portable detection logic from threat intelligence, mapping rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific queries using sigmac or pySigma backends.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install DSH on a fresh Mac. Runs sovereign-setup-mac.sh, renders .env from secrets backend, applies full sovereign lockdown, probes machine, and pulls right-sized Ollama models — one guided flow that leaves the node hardened and ready for Phase-2 spore.sh activation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
After navigating and interacting in Cursor's built-in browser, use browser_network_requests to audit every fetch/XHR for failures, slowness, duplicate calls, and suspicious payloads. Use for API-heavy pages and after backend or client networking changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast in-memory DataFrame library for datasets that fit in RAM. Use when pandas is too slow but data still fits in memory. Lazy evaluation, parallel execution, Apache Arrow backend. Best for 1-100GB datasets, ETL pipelines, faster pandas replacement. For larger-than-RAM data use dask or vaex.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.