'claude-code' 검색 결과

Knowledge base for Claude Code formats and patterns. Use when creating or improving commands, agents, skills, or hooks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Claude Code hook system for pre/post tool execution. Triggers on: hooks, PreToolUse, PostToolUse, hook script, tool validation, audit logging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Troubleshoot Claude Code extensions and behavior. Triggers on: debug, troubleshoot, not working, skill not loading, hook not running, agent not found.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run Claude Code programmatically without interactive UI. Triggers on: headless, CLI automation, --print, output-format, stream-json, CI/CD, scripting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Delegate coding to Claude Code CLI (features, PRs).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze prompts and offer depth / token-budget options BEFORE answering. Use this skill when the user wants to control token usage, tune response depth, choose between short and long answers, or optimize their prompt. Triggers on: "tokens", "token budget", "depth", "consumption", "short vs long answer", "how many tokens", "save tokens", "answer at 50%", "give me the short version", "I want to control how much you use", "tune your response", "presupuesto de tokens", "profundidad", "responde al 50%", "dame la versión corta", or any equivalent phrasing in English or Spanish. If the user wants to control length, detail or depth -- even without mentioning tokens explicitly -- this skill applies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up Claude Code git safety guardrails that block dangerous git commands before execution. Use when the user asks to prevent git push, hard reset, git clean, destructive checkout/restore, or branch deletion from Claude Code hooks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing a course, assessment, or student-feedback workflow and deciding where AI assistance is acceptable, when grading or feedback must stay within academic-integrity and FERPA/KVKK boundaries, or when AI-use rules for students need stating.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a researcher asks where to start, which project skill fits the current stage of a study, or in what order literature scoping, source access, vault upkeep, drafting, citation verification, disclosure, and review response should run.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when choosing or configuring MCP servers for research work, when a literature, reference manager, or scholarly search server needs a trust check before installation, or when an existing research tool stack needs a data flow and permission audit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a draft in Turkish, English, or both reads as AI-generated and needs revision that removes machine writing patterns and translation calques while preserving meaning, citations, statistics, and the author's voice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when paired tr.md and en.md files need a parity verdict, when titles, frontmatter, headings, or DOI sets may have drifted between languages, or when a bilingual document is approaching release and its translation coverage needs an audit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a systematic, scoping, or rapid review needs a reproducible pipeline: protocol framing (PICO/SPIDER/PCC), a logged search string, title/abstract and full-text screening with recorded exclusion reasons, and PRISMA flow counts, with the human as the deciding screener.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a reference list needs APA 7 cleanup, when DOIs must be confirmed real against Crossref or PubMed, when the user asks whether AI-suggested citations actually exist, or when a manuscript needs a citation hygiene pass before submission or defense.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a research proposal needs work packages, milestones, deliverables, a timeline, a risk register, and budget-justification scaffolding, while keeping scientific claims and feasibility honest and human-owned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a construct, scale, or key term crosses Turkish and English and conceptual equivalence must be audited: translation and back-translation, construct drift, and culturally bound meaning, before measurement or cross-cultural claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when coding interviews, focus groups, or open-ended responses with AI assistance, when a codebook needs building or auditing, when intercoder reliability must be computed, or when qualitative quotes need integrity checks before publication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when authoring a new manuscript, thesis chapter, or abstract from scratch in Turkish and English in parallel — building the claim skeleton first, then drafting Turkish and re-authoring English — not for auditing parity between existing versions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a complete research workflow — its instructions, skills, data boundaries, and tool connections — must be assessed for portability across AI agents or environments, so each component is explicitly mapped before migration rather than assumed to transfer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building slides, a poster, or a lightning talk from a manuscript, when a presentation must exist in Turkish and English, or when conference visuals need a traceability check so every number on a slide matches the analysis behind it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when choosing a journal for a finished or nearly finished manuscript, when index status in Scopus, SSCI, ESCI, or TR Dizin must be confirmed, when a venue looks predatory, or when a cover letter needs drafting from the manuscript's actual claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when selecting a statistical test with AI consultation, when assumptions need checking against the actual data, when an analysis plan or decision log must be written before running anything, or when results need APA-style reporting with effect sizes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a Claude Code session loops, drifts from scope, claims a fix that CI rejects, hits context, PATH, or permission walls, or fails in a way another retry will not solve and a root cause diagnosis is needed instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.