136건(heyAyushh의 저장소) · 인기순
Turn the current conversation context into a PRD draft. Use when user wants to create a PRD from the current context; publish it to an issue tracker only after explicit approval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route Expo application, EAS, native module, styling, deployment, and upgrade work to focused Expo skills. Use when building or operating an Expo or Expo Router project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route code cleanup, maintainability, React diagnostics, and over-engineering review to focused review modes. Use when auditing code quality or asking for a particular review lens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides Rust performance optimization. Use when profiling, benchmarking, reducing allocations, improving cache locality, choosing between rayon/async/threads, or applying SIMD/parallelism.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route communication modes, learning workflows, retrospectives, output discipline, and perspective shifts to focused productivity skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Babysit a GitHub pull request during a user-approved monitoring window by polling review comments, CI checks/workflow runs, and mergeability state. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and report fresh review feedback. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review, commit, push, and create a pull request through the current branch's configured upstream. Use when you want to ship deliberate changes end-to-end without assuming a particular remote or base branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route visual design, frontend art direction, motion, image generation, branding, and redesign work to focused design skills. Use when the task is primarily about how an interface or brand should look and feel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only when the user explicitly types `/orchestrate goal` to decompose a large task, spawn a tree of parallel cloud-agent workers/subplanners/verifiers via the Cursor SDK, and collect structured handoffs; do not invoke autonomously.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides Rust error handling strategy. Use when choosing between Result/Option/panic, using anyhow vs thiserror, propagating errors with ?, or designing custom error types.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides type-driven design in Rust. Use when encoding invariants in types, applying newtype pattern, implementing type state machines, using PhantomData, or making invalid states unrepresentable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route architecture, shell, MCP, prototyping, planning, issue, and release-maintenance work to focused engineering skills. Use for specialized engineering workflows that are not language-stack specific.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
iOS and Swift/SwiftUI development guidance, including App Clips, haptics, UI patterns, Liquid Glass styling, performance audits, view refactors, Swift concurrency, and iOS debugging. Use when building or reviewing iOS apps, SwiftUI views, or troubleshooting iOS issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review, commit, and push local changes through the current branch's configured upstream. Use when you want to ship a deliberate commit without assuming a particular remote.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Commit reviewed local changes on the current branch using conventional commit messages. Use when you need to create one or more atomic commits without pushing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grilling session that challenges your plan against the existing domain model and sharpens terminology. Use when user wants to stress-test a plan against their project's language and documented decisions; propose documentation updates for approval as decisions crystallise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explain Ponytail's intended tradeoffs and measurement boundary. It does not estimate code, cost, or speed savings for the current repository. One-shot display, not a persistent mode. Trigger: ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", or "ponytail scoreboard".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a "product description" repo for a software product — a set of prose documents describing, from the outside in, what the user sees, what they can do, and exactly what happens when they do it, written from the code and tests, then verified against the running product and triaged into a bug list. Works for any product with a user (canvas editors, web apps, CLIs, chat products, mobile apps). Use when the user asks to "write a product description for X", "describe the user experience of X", "document how X behaves for the user", "make a behavior-spec repo", or wants a feature-by-feature, event-by-event account of an app's behavior rather than API docs. Also use to resume or extend an existing product description repo.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.