코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.7만건)
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review code for quality, bugs, and improvements. Use when user wants code review or quality assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claudeデスクトップアプリ（Codeタブ）の全セッションを見回り、名前の先頭の絵文字で「⏳作業中／👀確認中／📤送信待ち／🔴要確認／✅完了」を表し、「絵文字【フォルダ】内容」の形に付け直すスキル。自分の判断が要るものだけを一覧にまとめ、完了したものは夜にまとめてアーカイブする。「セッションを整理して」「どのセッションが自分待ち？」「セッションに絵文字を付けて」「session triage」等で使う。定期実行（15分おき）に載せると、サイドバーを見るだけで状況が分かる状態を保てる。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Self-improve AI Factory skills based on project context, accumulated patches, and codebase patterns. Analyzes what went wrong, what works, and enhances skills to prevent future issues. Use when you want to make AI smarter for your project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up agent context for a project. Analyzes tech stack, installs relevant skills from skills.sh, generates custom skills, and configures MCP servers. Use when starting new project, setting up AI context, or asking "set up project", "configure AI", "what skills do I need".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cut a versioned LoreWeave release — draft the CHANGELOG.md entry from what shipped since the last tag, confirm the SemVer bump and pre-release/release decision with the user, then tag and push to trigger the automated build + GitHub Release. Use when the user says "cut a release", "publish v...", "ship v0.1.0", "make a release", or asks what's changed since the last version.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a standalone read-only rules compliance gate against changed files or a git ref. Use when you need a dedicated project-rules check without a full review or verify pass.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforce the anti-slop contract when duplicate helpers, fake modularization, or oversized-file pressure show up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a slice shows duplicate helpers, fake modularization, oversized-file pressure, or AI-shaped code slop that needs explicit cleanup discipline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up agent context for a project. Analyzes tech stack, installs relevant skills from skills.sh, generates custom skills, and configures MCP servers. Use when starting new project, setting up AI context, or asking "set up project", "configure AI", "what skills do I need".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a standalone read-only rules compliance gate against changed files or a git ref. Use when you need a dedicated project-rules check without a full review or verify pass.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Self-improve AI Factory skills based on project context, accumulated patches, and codebase patterns. Analyzes what went wrong, what works, and enhances skills to prevent future issues. Use when you want to make AI smarter for your project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate an evidence-gated electronic product and PCBA workflow from an idea, circuit description, schematic, netlist, PCB, BOM, or fabrication package through a reviewed order. Use for end-to-end requests, multi-stage hardware projects, workflow recovery, gate tracking, change invalidation, or deciding which specialist skill is required next.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js client - configuring the client, pinging, inserting rows in JSON or raw formats, selecting and parsing results, binding query parameters, managing sessions and temporary tables, working with data types or customizing JSON parsing. Do NOT use for browser/Web client code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SurrealFS virtual filesystem for AI agents. Rust core + Python agent (Pydantic AI). Persistent file operations backed by SurrealDB. Part of the surreal-skills collection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SurrealDB MCP for AI agents: built-in server (SurrealDB 3.1+ `surreal mcp`) and standalone surrealmcp (surrealdb/surrealmcp v0.4.0). Part of the surreal-skills collection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain governance artifacts without implementation work. Use when: (1) Accepting or refining ADRs, (2) Clarifying or amending RFCs without code changes, (3) Governance-only docs/check/render updates
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adopt govctl in an existing project. Discovers undocumented decisions, backfills ADRs/RFCs, annotates source code. Use when: (1) Project has no governance yet, (2) User mentions migrate, adopt, onboard, or brownfield
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix silent failures when parsing Grafema semantic IDs that are in URI format instead of legacy arrow format. Use when: (1) code splits semantic IDs by "->" but gets the whole string back because IDs are grafema:// URIs, (2) file path extraction from semantic IDs returns empty or wrong values, (3) derived edges (DEPENDS_ON, etc.) produce 0 results despite source edges existing, (4) any code that processes semantic IDs after the analysis pipeline's to_uri_format() has run. The grafema:// URI format uses # fragments with percent-encoded characters instead of -> separators.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix missing theorem proof terms when analyzing Lean 4 environments via importModules. Use when: (1) ConstantInfo.value? returns none for theorems despite TheoremVal.value being Expr, (2) building code graph / dependency extractor for Lean 4 and getting 0 proof dependency edges, (3) Lean 4.30+ project where theorem proofs appear missing from loaded environment, (4) analyzing Mathlib or any Lean 4 project and proof terms are empty. Root cause: breaking change in Lean 4.30 — value? treats theorems as opaque by default.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix intermittent `{:no_translation, :unicode, :latin1}` crashes in Elixir escript daemons that use length-prefixed framed IPC on stdin/stdout. Use when: (1) daemon worker crashes only on some input files, usually ones with non-ASCII bytes (kanji, cyrillic, emoji); (2) error surfaces as `Protocol error` from daemon's error branch or as garbled frame-length bytes seen by the orchestrator/client side; (3) standalone one-shot mode works fine on the same input but multi-request daemon mode fails; (4) `IO.binread(:stdio, N)` returns `{:error, {:no_translation, :unicode, :latin1}}` despite the "bin" prefix suggesting it should be encoding-agnostic. Root cause is the escript default `:standard_io` encoding — it's `:unicode`, and `IO.binread` still routes through the io_server, which translates bytes to codepoints and errors when raw binary frames contain invalid UTF-8 sequences.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.