코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.8만건)
Guides generic vs trait object decisions in Rust. Use when choosing between static and dynamic dispatch, designing traits, handling E0277/E0038, or deciding between enum and dyn Trait.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides concurrency and async decisions in Rust. Use when encountering Send/Sync errors (E0277), choosing between threads vs async, designing shared state, or debugging deadlocks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides Rust performance optimization. Use when profiling, benchmarking, reducing allocations, improving cache locality, choosing between rayon/async/threads, or applying SIMD/parallelism.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides Rust error handling strategy. Use when choosing between Result/Option/panic, using anyhow vs thiserror, propagating errors with ?, or designing custom error types.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert TypeScript engineering with advanced patterns, architectural design, performance optimization, testing strategies, and production-grade code quality. Use when building scalable TypeScript applications, implementing complex type systems, optimizing performance, designing maintainable architectures, or when the user asks for TypeScript engineering excellence, advanced patterns, or professional-grade code practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when finishing a feature, fixing a bug, before committing React code, or when the user asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture, regression checks, and local triage with React Doctor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
50 core Rust coding conventions covering naming, data types, strings, error handling, memory, concurrency, async, and modern crate recommendations. Use when reviewing code style or setting up project conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Microsoft Pragmatic Rust Guidelines for implementing, reviewing, and documenting idiomatic Rust. Use when working on Rust APIs, error handling, unsafe code, concurrency, async code, performance, testing, documentation, or agent-facing design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove AI-generated code slop and clean up code style
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Streamline code by removing redundancy and aligning with repo style. Use when you need to consolidate logic, reduce indirection, clean up repeated patterns, or make code more concise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifies and fixes common Rust anti-patterns. Use during code review, when seeing excessive clones/unwraps/index loops, or when code fights the borrow checker instead of working with it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor code to improve quality while maintaining functionality. Use when you need to improve code structure, eliminate duplication, optimize performance, or enhance maintainability without changing behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides Rust coding best practices for structure, patterns, performance, and error handling. Use when writing or reviewing Rust code, or when the user asks for Rust style guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.