164건 · 관련도순
Choose between standard mileage rate and actual expenses for business vehicle deductions. Covers the IRS mileage rate, method lock-in rules, mileage log requirements, commuting rules, luxury auto limits, and heavy vehicle exceptions. Trigger on "mileage deduction", "standard mileage rate", "vehicle expenses", "car deduction", "business miles", "mileage tracking".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track independent contractor payments, collect W-9s, determine 1099-NEC filing requirements, and avoid penalties. Covers the $600 threshold (2025) and $2,000 threshold (2026), Jan 31 deadline, corporate exceptions, backup withholding, and penalty schedule ($60–$660/form). Trigger on "1099", "contractor payment", "do I need to file a 1099", "W-9", "independent contractor".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java/Kotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrates Sentry error tracking and performance monitoring into Flutter apps using `sentry_flutter`. Use when setting up crash reporting in Flutter, calling `SentryFlutter.init`, adding `SentryNavigatorObserver` to GoRouter, tracing HTTP requests with `sentry_dio`, capturing handled exceptions via `Sentry.captureException`, adding breadcrumbs, configuring session replay (`replay.onErrorSampleRate`), tuning `tracesSampleRate` or `profilesSampleRate`, controlling PII with `sendDefaultPii`, or setting user context after login and logout.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks how to "use VibeTags", "add VibeTags annotations", "set up AI guardrails", "protect code from AI", "configure AI platforms", asks about @AILocked, @AIContext, @AIDraft, @AIAudit, @AIIgnore, @AIPrivacy, @AICore, @AIPerformance, @AIContract, @AITestDriven, @AIThreadSafe, @AIImmutable, @AIDeprecated, @AIObservability, @AIRegulation, @AIArchitecture, @AILegacyBridge, @AIStrictClasspath, @AIInternationalized, @AIPublicAPI, @AISchemaSafe, @AIStrictExceptions, @AIStrictTypes, @AIParallelTests, @AIIdempotent, @AIFeatureFlag, @AISecure, @AICallersOnly, @AISandboxOnly, @AIMemoryBudget, @AIPure, @AIDomainModel, @AIExtensible, @AIInputSanitized, @AISecureLogging, @AIExplain, @AIPrototype, @AISunset, @AITemporary annotations, or wants to control how AI tools interact with Java code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions securely without exposing sensitive data, managing secrets at runtime, avoiding unsafe deserialization, and encoding output to prevent XSS. This should trigger for requests such as Review Java code for secure coding. Part of cursor-rules-java project
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement comprehensive error handling for Python code paths to keep services resilient and user-friendly. Use when failures are currently silent or exceptions leak through.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract proof-of-delivery number, recipient, delivery time, items, exceptions, and signature status from delivery receipts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), turn the issue into an Epic and split it into sub-issues when its work should ship as separate PRs (cc-epic-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compress an oversized SKILL.md to under 200 lines without losing effectiveness. Load when a skill exceeds 200 lines, when AGENTS.md triggers compression after a skill edit, or when the user asks to compress, shrink, slim down, or optimize a skill. Also triggers on "this skill is too long", "reduce skill size", "make this skill shorter". Applies to all skills including meta skills — the 200-line rule has no exceptions. Preserves hard gates, gotchas, output format, routing triggers, and at least one example. When genuinely CORE content cannot be compressed away, invokes split-skill instead of degrading the skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks what emergency equipment a CMV must carry under 49 CFR 393.95 — reflectorized triangles, flares, fire extinguishers, spare fuses, exceptions for buses/passenger CMVs, where to mount/store equipment, and what roadside inspectors check. Cite 49 CFR 393.95 + 393.97.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates PSR-11 Container implementation for PHP 8.5. Creates ContainerInterface with service resolution, autowiring support, and exceptions. Includes unit tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prefer a fresh matching specialist for a clear bounded non-trivial package when current capabilities and permissions permit it; use direct ROSE work only for accepted direct-work exceptions or a concrete block.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.