1.6천건 · 관련도순
Structured methodology for adversarial thinking — generating attack scenarios, abuse cases, race conditions, and security edge cases against specs and implementations. Produces spec-level gap items, not code-level fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proactive self-monitoring of infrastructure, services, and health. Tracks disk/memory/load, service health, cron job status, recent errors. Auto-fixes safe issues. Triggers on: health check, heartbeat, monitor status, service status, infrastructure check.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous build-ship-verify loop that ends with code committed, deployed, and confirmed live. Triggers on: "$ownership", "execute X with ownership", "build this overnight", or any request for an autonomous product loop with no human checkpoints until production is verified. NOT for: one-off tasks, quick fixes, or supervised dev work (use devprocess for those).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured build workflow: branch, delegate to coding agent, test, screenshot, and commit. Triggers on: "$devprocess", "build this properly", "use the coding agent workflow", or any feature/refactor/infrastructure change that is too large for a direct edit. NOT for: one-line fixes, doc edits, prompt tweaks, or simple config changes — do those directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Overhaul one app's UI against an audit: UX audit and UI review of the running app, current versus proposed design tokens, a before/after visual plan, a startcycle build, point fixes, accessibility and browser tests, delivered as a PR after GO. Use for "redesign this app", "design overhaul", "audit and fix the UI", "give the app a new look".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn one reference image into a cleaned, scaled 3D asset: your own image-to-3D ComfyUI workflow makes the mesh, Blender decimates it to a poly budget, fixes scale, origin and material, and exports a .glb. Use for "image to 3D", "make a 3D model from this picture", "photo to glb".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose slow React components and suggest targeted performance fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A prototyping skill that generates a local HTML mock with a built-in feedback layer, allowing users to drop visual comments (red dots) for UI fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit UIKit-based screens for accessibility issues with concrete VoiceOver and Dynamic Type fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit SwiftUI views for accessibility (iOS + macOS) with patch-ready fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed up Xcode builds, wants a full build audit, or needs a recommend-first optimization pass covering compilation, project settings, and packages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stops "just one more" small tweaks that add scope without changing the outcome. Use when named (just-stop), or when about to implement extra polish, cleanup, or drive-by fixes beyond the stated goal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Devil's-advocate attack on AI workflow designs — threat model, assumption challenges, code critiques, and hypothetical redesigns with no file edits. Use for "attack this design", devil's advocate, or hostile challenge on agents/tools/summarization/tokens. Not for PR peer review (code-review) or self-review that applies fixes (ai-systems-review). Prefer: this skill → decide → ai-systems-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hostile self-review of recently written AI workflow code that then applies fixes (agents, tools, chat context, summarization, tokens, attachments). Use after generating AI systems code, or when asked to self-review and harden it. Not for PR peer review (code-review) or no-edit devil's-advocate attacks (adversarial-challenge). Prefer: adversarial-challenge → decide → this skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.