Claude Code Skills · page 123

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

Analyzes and improves prompts using 31 frameworks across 7 intent categories. Use when a user wants to improve, rewrite, structure, or engineer a prompt — including requests like "help me write a better prompt", "improve this prompt", "what framework should I use", "make this prompt more effective", or any prompt engineering task. Recommends the right framework based on intent (create, transform, reason, critique, recover, clarify, agentic), asks targeted questions, and delivers a structured, high-quality result.

>-

>

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural

>

>

>

>

Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect,

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

Researches an open-ended question — options, possible solutions, prior art, trade-offs, or how something works — and

>

>

OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — ADVERSARIAL inline guidance variant. Worst-case anchor: ends with a final-sounding completion statement and gives NO instruction to return to the caller. Use only when a spike consumer skill invokes it.

OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.

OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

>

>

>

>

>

>

>

Guide for using ruff, the extremely fast Python linter and formatter. Use this

Guide for using ty, the extremely fast Python type checker and language

Guide for using uv, the Python package and project manager. Use this when

This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.

Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.

Prune and route AGENTS.md trees for durable, high-signal context.

Automatically benchmark your custom memory implementation against established systems like Supermemory. Set up a public benchmark, or create your own. Compare solutions against quality, latency, features and cost, easily, with a simple UI and CLI.

Maintain Signet's living ontology and memory substrate from transcripts, memory artifacts, source artifacts, notes, summaries, and imported records.

Use for Signet Dreaming development: inspect existing source, semantic-memory, retrieval, and inference architecture before changing it; prevent duplicate modules and ad-hoc providers.

Interactive interview to set up your Signet workspace (~5-10 minutes). Writes identity files to ~/.agents/ — does not access external APIs, send data anywhere, or execute arbitrary code. Use when user runs /onboarding or says 'set up my agent'.

Navigate Signet ontology and knowledge graph state from Codex.

Use Signet-specific recall and source search from Codex without confusing it with Codex native memory.

Save explicit notes into Codex native memory through Signet.

Search Signet transcript/session evidence from Codex.

>-

|

비개발자를 위한 Claude 대화 모범 사례 — 명확한 지시, 맥락 제공, 예시 활용, XML 태그 구조화. Claude 공식 프롬프트 엔지니어링 가이드 기반. "Claude한테 어떻게 물어봐야 잘 답해줘?" 질문에 즉시 활용.

|

>

>

>

>

>