635건 · 관련도순
Pre-release readiness review. Scans for debug artifacts, version mismatches, changelog gaps, git hygiene issues, breaking changes, and license compliance. Runs tests and build verification. Presents consolidated findings for human review before release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies rigorous adversarial analysis to generate, critique, fix, and consolidate solutions for any problem (technical or non-technical). Use when facing complex problems requiring thorough analysis, multiple solution approaches, and validation of proposed fixes before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Converts transparent or solid-background single-color PNG files and SVG files containing one embedded or local PNG into verified path-only SVG output. Removes pure-color backgrounds automatically. Uses Potrace threshold and parameter scans with alpha error metrics to preserve detailed logos, stamps, engravings, and line art. Use when the user asks to convert images to SVG, vectorize PNG, convert bitmap to true SVG, remove embedded raster data from SVG, 图片转矢量, PNG 转 SVG, 真矢量, or 位图描摹.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building content-heavy sites with Astro, deciding between SSG/SSR/hybrid, choosing client directives (idle/visible/load/media), structuring content collections with type-safe schemas, integrating React/Vue/Solid/Svelte components in the same project, or migrating from Next.js for marketing/docs. Triggers: client:idle vs client:load tradeoffs, content collections schema with zod, image optimization via @astrojs/image, view transitions, server islands, MDX layouts. NOT for SPA-style apps that need full interactivity (use Next/Remix), Astro internals/plugin authoring, or non-content sites where islands provide no benefit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DRY (Don't Repeat Yourself) review rules for code reviews: find the same knowledge — a rule, a constant, a parser, a validation, a protocol detail — implemented in several places that must change together, and tell it apart from code that merely looks alike. Use when reviewing a diff, a pull request or recent changes for duplication, on "DRY review", "is this duplicated", "copy-paste check", or when a review checklist asks for DRY. Pair it with the solid skill for design and with owasp-asvs for security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate repeated code and consolidate duplication when a shared abstraction improves correctness or maintenance. Use after introducing similar logic or when repeated changes reveal a missing source of truth.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Calls HLA class I and class II alleles at 2/4/6/8-field resolution from WGS/WES/RNA-seq/long-read data using OptiType, HLA-LA, T1K, Polysolver, HLA-HD, arcasHLA, StarPhase, or HIBAG imputation. Use when typing for HSCT, solid-organ transplant, neoantigen prediction, PGx screening (B*57:01, B*15:02, etc.), or disease-association studies, with reconciliation across tools and IPD-IMGT/HLA version mismatch handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast parallel codebase scouting. Spawns multiple Explore subagents to search directories simultaneously, returning a consolidated file map with architecture fingerprint, complexity estimates, and routing suggestions. Use before planning, debugging, or any task spanning multiple directories. NOT for reading a single known file in depth (use Read directly); NOT for semantic find-usages or go-to-definition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find deepening opportunities in a codebase, informed by the project's own domain language and prior design decisions. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform rough ideas into solid designs through structured questioning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when planning or upgrading an internal skill/workflow for business operations, especially when turning a messy idea into a structured skill plan, migration plan, acceptance checklist, or packaging decision. Particularly useful for Obsidian knowledge base consolidation, workspace migration, content library cleanup, and integrating multiple workbenches into one operating system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level environmental engineering covering water treatment, wastewater treatment, air quality, solid waste, site remediation, and environmental regulations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level CAD design covering parametric modeling, assembly design, drawing creation, FEA simulation, design for manufacturing, and PLM workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to improve architecture, consolidate tightly-coupled modules, or make a codebase more testable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user says 'create service', 'new service class', or needs a PHP service following SOLID principles with proper DI and repository usage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes or edits PHP code — controllers, classes, type hints, SOLID refactors, modern idioms — even without naming PHP. NOT for writing tests (use pest-testing) or explaining PHP concepts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use to consolidate multiple already-run judge verdicts into one report — consensus, conflicts, must-fix/should-fix with per-judge provenance. Consume-only, no opaque score, never auto-gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.