522건 · 관련도순
Use when working with Bazel — bazel build system management. Covers BUILD file analysis, target querying, dependency graphs, remote execution, caching configuration, and build performance profiling. Use when managing Bazel workspaces, debugging build failures, querying targets, or optimizing build performance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Azure Cdn — azure CDN management covering profiles, endpoints, custom domains, caching rules, origin groups, and performance analytics. Supports Microsoft, Verizon, and Akamai CDN providers within Azure. Use when managing Azure CDN endpoints, analyzing cache performance, configuring delivery rules, or troubleshooting content delivery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, configure, and deploy Netlify Edge Functions (Deno runtime at the network edge) in TypeScript/JavaScript. Use when adding request/response manipulation at the edge — auth middleware, geolocation redirects, A/B testing and personalization, content localization, redirects/rewrites, SSR at the edge, or transforming responses — or when configuring path routing, response caching, or edge error handling. Triggers on tasks like "add auth middleware", "geo-based redirect", "A/B testing at the edge", "rewrite requests", or editing files in netlify/edge-functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patterns. Use when working with REST APIs, downloading files, uploading data, WebSocket connections, pagination, retry logic, request middleware, caching, background transfers, or network reachability monitoring. Also use when handling HTTP requests, API clients, network error handling, or data fetching in Swift apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure a Next.js app for Vercel. next.config versus vercel.json, proxy (renamed from middleware in Next.js 16), images, redirects and headers, function duration and region, caching and static export pitfalls, and local verification. Use when editing next.config, vercel.json or routing for a Next.js project on Vercel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PWA design: production-level offline strategy, SW updates, caching. Use when implementing, reviewing or testing pwa design for React, Vite, Next.js or Perfect_AI projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize AgentDB performance with quantization (4-32x memory reduction), HNSW indexing (150x faster search), caching, and batch operations. Use when optimizing memory usage, improving search speed, or scaling to millions of vectors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify and avoid Adobe-specific anti-patterns: using deprecated JWT auth, not caching IMS tokens, ignoring Firefly content policy, missing async job polling, and leaking p8_ secrets. Real code examples with fixes. Trigger with phrases like "adobe mistakes", "adobe anti-patterns", "adobe pitfalls", "adobe what not to do", "adobe code review".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates, debugs, and optimizes GitHub Actions workflow YAML files. Recommends current action versions with SHA pinning from a daily-updated index of 120+ actions. Configures matrix builds, dependency caching, reusable workflows, OIDC authentication, secrets management, and runner selection. Reviews existing workflows for outdated actions, security issues, and performance problems. Use when the user asks about GitHub Actions, workflows, CI/CD, .github/workflows, any action by name (actions/checkout, setup-node, setup-python, etc.), or workflow optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. This should trigger for requests such as Review or improve Micronaut @Controller REST APIs; Add validation, error handling, or align controllers with the OpenAPI contract on Micronaut HTTP layer. Part of cursor-rules-java project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses. Part of cursor-rules-java project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI (OpenAPI Generator), controller advice, and problem details for errors. This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code. Part of cursor-rules-java project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Three-axis orchestrator: (1) clean section boundaries — naming, routes, views, ViewModels, DB ownership, cross-section access; (2) internal cohesion — no EF in service layer, caching in service only, proper interfaces, reusable ViewComponents, architecture-test coverage; (3) focused tests — grouped under the section, covering invariants/negatives/triggers, pruned of redundancy. Push-and-bot-review loop. Use when a sizable PR landed, a section shows arch drift, or /pr-review returned a non-trivial violation list. Camps is the gold-standard reference.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenAI API (developers.openai.com) の Responses API リファレンス。 text generation, embeddings, gpt-6-astra / gpt-6.1-sol / gpt-6-luna, structured outputs, streaming, function calling, programmatic / async tool calling, conversation state, prompt caching, prompt cache diagnostics, reasoning (configuration_update), background mode, compaction, multi-agent, WebSocket mode (mid-turn steering, stream_id), webhooks, error codes, rate limits, Realtime server controls, 公式 SDK (Python / JS / .NET / Java / Go / Ruby), openai CLI, Chat Completions / Assistants 移行, deprecations。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenAI API (developers.openai.com) の運用・管理リファレンス。 Administration API, admin API keys, RBAC, roles, groups, invites, projects, spend limits, audit logs, usage / costs API, Terraform provider (openai/openai), workload identity federation (WIF, OIDC / SPIFFE / X.509 / Idira), moderation API, misalignment monitoring, safety alerts / cases, safety best practices, under-18 guidance, ZDR Private Safety Processing (PSP), production best practices, deployment checklist, cost / latency optimization, fast / ultrafast mode, Realtime API costs。 rate limits・error handling・prompt caching・webhooks は openai-api-core、Codex WIF・管理は openai-codex。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude API (platform.claude.com) の Messages API リファレンス。 streaming (SSE), thinking (adaptive) / preserved thinking / effort, prompt caching, context editing, compaction (on-demand / threshold), structured outputs, Message Batches, token counting, vision / PDF, Files API, citations, embeddings (Voyage AI), errors, rate limits, beta headers, Bedrock / Vertex AI / Foundry 経由アクセス。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude API (platform.claude.com) のモデル・SDK。 model ID・選択基準、Fable・Mythos 5.1 / Opus・Sonnet・Haiku 5.5 移行・破壊的変更、 コスト最適化 (effort / caching / batch / advisor)、pricing、deprecation、用語集。 公式 SDK 7 言語 (Python / TypeScript / Java / Go / Ruby / C# / PHP)、 Claude API 用 CLI `ant` (Claude Code CLI とは別。quickstart / authentication / scripting、`ant apply` resources as code、Managed Agents session 接続)、 middleware、OpenAI SDK 互換、Apple Foundation Models。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add or modify a Flask endpoint in the Lyrion Dashboard. Use this whenever a task adds a new URL/route, a JSON API endpoint, or a page — anything that registers a handler in `routes/`. Covers the repo's route → service → test layering, input validation, caching headers, security headers, i18n wiring, and the exact test pattern, so a new endpoint matches how `routes/` already works instead of reinventing the structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.