스킬 찾기

Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health

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

Expo Framework-specific guidelines. Includes best practices for Views, Blueprints, and Extensions.

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

Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.

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

Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.

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

Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly across many functions. Covers Inngest middleware lifecycle, creating custom middleware, dependencyInjectionMiddleware, @inngest/middleware-encryption, @inngest/middleware-sentry, and custom middleware patterns.

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

Pino, Axiom, Sentry installation - one-time project setup for logging and error tracking with source maps upload

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

Pino logging, Sentry error tracking, Axiom - structured logging with correlation IDs, error boundaries, performance monitoring, alerting

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

Implements features in vertical slices, always starting with homepage. Enforces anti-placeholder rules — no lorem ipsum, no TODO stubs, no gray boxes. Real content, real images, real interactions. TypeScript strict mode, Zod validation, and structured file organization.

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

Full instrumentation from day one. PostHog consolidates product analytics + feature flags + error tracking (one platform, one bill). GA4 via GTM (14-step automation, custom dimensions over events, server-side tagging). Sentry (deep error tracking + performance). Stripe (webhook-first with idempotent processing). Listmonk on Coolify (newsletters via Amazon SES SMTP relay). PLG 7-layer framework. Programmatic SEO (5 page types). Incident auto-remediation via Sentry→Inngest pipeline. AI search (GEO) awareness. Local business conversions (phone_click, direction_click, form_submit, booking_click) with CRO patterns for both SaaS and local.

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

One-line-prompt → cinematic, gorgeous, functional, well-tested, deployed website. Pre-hydrated SPA + full PWA kit + JSON-LD rich snippets + third-party integrations. React 19+Vite default (Angular optional). 100 concrete improvements grouped into 10 categories that EVERY single-prompt site build must satisfy before being marked done. Trigger whenever the user says 'make a website for X', 'build a site for X', 'rebuild X.com', or any equivalent one-liner.

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

Sentry Unity SDK integration patterns for error tracking, performance monitoring, transactions, spans, and custom instrumentation.

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

Audit whether a product is ready for enterprise sales. Use when you need to assess SSO/SAML/SCIM support, RBAC maturity, multi-tenancy data isolation, audit logging coverage, public API quality, SLA operational readiness, SOC2/ISO27001 certification gaps, GDPR data residency controls.

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

Analyze mobile app analytics implementation including event tracking completeness and naming conventions, SDK configuration audit (Firebase Analytics, Amplitude, Mixpanel, PostHog), attribution tracking with AppsFlyer/Adjust/Branch and SKAdNetwork conversion values.

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

Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.

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

Django + Celery async task patterns — configuration, task design, beat scheduling, retries, canvas workflows, monitoring, and testing. Use when adding background jobs, scheduled tasks, or async processing to a Django app.

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

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

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

Design resilient React error handling with Error Boundaries, Sentry integration, recovery UI, retry patterns, and graceful degradation. Activate on: error boundary, crash recovery, Sentry, error fallback UI, retry logic, unhandled exceptions. NOT for: form validation errors (use form-validation-architect), API error codes (use api-architect).

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

Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).

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

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.

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

54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.

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

Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.

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

Use when the user shares a Sentry URL, says "check Sentry", or wants to investigate production errors. Uses Sentry MCP tools for deep analysis.

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

Use on a bug, test failure, crash, or unexpected behavior — enforce reproduce → isolate → hypothesize → verify before any fix; fires even on 'this is broken' / 'quick fix'.

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

Use when extracting Voice-of-Customer themes from existing artefacts — GH issues, PR threads, Sentry patterns. Triggers on 'what are users saying', 'recurring complaints', 'top themes'.

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