코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.8만건)
Analyze codebases using a graph database instead of reading source files. Use when understanding code architecture, finding functions or call patterns, tracing data flow, checking dependencies, or answering "where is X used?" questions. Grafema builds a queryable code graph from static analysis — prefer querying the graph over reading files manually.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Force `rust-embed` to re-embed assets from `$GRAFEMA_UI_DIST` (or any env-driven path) when cargo's incremental compilation skips the macro re-expansion. Use when: (1) you rebuilt the GUI bundle but the rust-server binary still serves the OLD bundle, (2) `cargo build --release` finishes in seconds (incremental hit) and `strings target/release/binary | grep <new-hash>` finds nothing, (3) any rust-embed pipeline where assets live outside the cargo source tree and are picked up via env var or symlink. Cargo only re-runs the proc macro when the rust file declaring `#[derive(RustEmbed)]` changes — env var changes alone don't trigger it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build all packages, reinstall VS Code extension, commit and push. Use when: user says "ship", or wants to build+install+commit+push in one go.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix scattered/torn regions in hex-grid simulated annealing layouts that use "competitive flood-fill" (one tile per region per outer iteration). Use when: (1) regions of >20 tiles end up dispersed instead of forming compact blobs, (2) maxDist/sqrt(N) dispersion ratio is 10×+ worse than the ideal compact blob, (3) tiles assigned to one region show up in multiple disconnected fragments across the layout, (4) the visualization has a "trypophobia ring" pattern at the perimeter where some regions spill into a perimeter spiral, (5) an overflow spiral fallback exists in the layout code and frequently kicks in for large regions, (6) bigger regions look worse than smaller ones (small regions stay compact, big ones shred). Root cause: interleaved competitive flood-fill (round-robin one tile at a time across all regions) lets large regions get boxed in by neighbors before they finish growing — the unfilled remainder is dumped into the overflow spiral at the perimeter, far from the seed. Fix: replace with sequential region-by-region BFS — process regions in size-descending order, fully claim each region's N contiguous tiles before moving to the next.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when researching Claude Code or Codex upstream releases, selecting adaptations, or preparing Harness upgrades. Local-only; not for distribution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when running Plans.md tasks on a scheduled cadence (fresh context per wake-up, sprint-contract flow, plateau detection, flock guard). Do NOT load for: single-task work (harness-work), planning, review, release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for writing, configuring, and debugging Claude Code hooks. Use when adding, writing, or debugging hooks — including silent failures and permission errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing, executing, or running Plans.md tasks — single task, parallel workers, or full team/breezing run. Accepts specific task numbers or ranges. Do NOT load for: planning, review, release, or setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when running the full team/breezing flow end-to-end — all tasks with parallel workers. Do NOT load for: single-task implementation, planning, review, release, or setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract verifiable engineering evidence from a GitHub repository and grade its quality. Use this when a candidate provides a GitHub URL to generate evidence-backed resume bullets with confidence scores and source citations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured evidence schema for capturing project and experience context before generating resume bullets. Separates implementation, execution, ownership, and impact evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured evidence schema for capturing rich project context before generating resume bullets. Use this to build the evidence foundation that all bullet generation, confidence scoring, and interview defensibility checks depend on. Technology-agnostic — works for any engineering domain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Linear issues, projects, cycles, initiatives, and teams via the `linear` CLI (schpet/linear-cli)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creating TypeORM database migrations. Use when schema changes are needed (new columns, tables, indexes, constraints).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Self-review local changes before creating a PR. Use when the user says "review", "review my code", "check my changes", or wants confidence before submitting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create temporary PR-specific screenshots and short GIF demos without committing scene code to the product branch. Use automatically when a visually meaningful frontend change materially benefits from visual review, and when the user requests PR media. Do not use for backend-only, non-visual, or already-sufficiently-proven changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug backend runtime errors (500s, crashes, unexpected behavior). Use when something is broken at runtime — not for writing new code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend development with NestJS, TypeORM, and hexagonal architecture. Use when creating, modifying, or debugging backend code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work a Linear ticket end-to-end — read it, mark it started, implement and validate it, submit and finish its PR unless local-only was requested, summarize the outcome, proactively suggest follow-up tickets, and hand code work off for release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Frontend development in ayunis-core. Use when creating, modifying, or debugging frontend code (React, Feature-Sliced Design, API client).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ayunis Core backend specifics — module boundaries, key files, and project conventions. Complements the nestjs-hexagonal-backend skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix OpenAPI schema drift between backend and frontend. Use when CI fails with "API Schema Drift" or "API client is out of date", or after adding/changing backend controllers or DTOs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Frontend form patterns — form types in model/, useForm setup, and end-to-end backend validation with field-level error display. Use when adding or modifying any form (page or dialog) that submits to the API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.