2.9천건 · 관련도순
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Visual inspection of live websites to find and fix design issues. Use when reviewing UI layout/design, checking responsive design visually, detecting visual inconsistencies, or diagnosing CSS/accessibility problems at the source code level. Not for automated E2E testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling `connect()`), configuring connection pools, troubleshooting connection errors (ECONNREFUSED, timeouts, pool exhaustion), optimizing performance issues related to connections. This includes scenarios like building serverless functions with MongoDB, creating API endpoints that use MongoDB, optimizing high-traffic MongoDB applications, creating long-running tasks and concurrency, or debugging connection-related failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing or writing LLM, RAG, MCP, tool, or agent code for OWASP-aligned security issues; triggered by "owasp my code", "owasp this PR", AI security review, PR review, or changes to AI system code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ship the day's work in one repo: triage new issues, review every open PR (description, visual recap, adversarial reviewer, shipping pre-flight and quality gate), merge only after GO, then post a status recap. Use for "ship it", "ship day", "merge the ready PRs", "end of work block".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive design guide for web and mobile applications. Use when designing new UI components or pages, choosing color palettes and typography, or reviewing code for UX issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Move issues and external PRs through a state machine of triage roles, categorise, verify, and write agent-ready briefs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Use when writing new React components or Next.js pages, implementing data fetching (client or server-side), or reviewing code for performance issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Linear issues, projects, and teams
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Core Swift development workflows for Xcode and Swift tooling, including project setup, dependency management, concurrency guidance, language/runtime best practices, and troubleshooting build or package resolution issues. Use when working on Swift tasks across a codebase, especially package/tooling/runtime work and cross-cutting Swift conventions (mutation semantics, naming, enum/file rules, import hygiene), including in SwiftUI projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit UIKit-based screens for accessibility issues with concrete VoiceOver and Dynamic Type fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and improve SwiftUI runtime performance. Use when diagnosing slow rendering, janky scrolling, high CPU, memory usage, excessive view updates, layout thrash, body evaluation cost, identity churn, view lifetime issues, lazy loading, Instruments profiling guidance, and performance audit requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and optimize React component performance issues (slow renders, re-render thrash, laggy lists, expensive computations). Use when asked to profile or improve a React component, reduce re-renders, or speed up UI updates in React apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured 3-phase peer review of a diff or PR — intent, issues by severity, then pointed merge-readiness questions and a verdict. Use for general code review. Not for AI workflow self-fix-and-edit (ai-systems-review) or no-edit devil's-advocate threat models (adversarial-challenge). Phase 3 asks questions only; it is not the adversarial-challenge skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.