'understand' 검색 결과

Explain any topic, code, concept, or error tailored to a specific audience's level of understanding. Use this skill whenever the user says 'explain like I am', 'ELI5', 'explain this to my', 'break this down for', 'dumb it down', 'simplify this for', or asks you to explain something to a specific person or audience type (e.g., 'explain this to a manager', 'how would I explain this to my mom', 'make this understandable for a 5th grader'). Also trigger when the user mentions wanting to understand something at a particular level, or asks for an explanation targeting a non-technical audience. Even partial matches like 'explain to my wife' or 'tell my boss' should trigger this skill.

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

After the learner demonstrates understanding of a concept, present near-transfer and far-transfer challenges. Use to test whether learning is portable or task-specific — this is what separates understanding from familiarity.

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

Design a checking-for-understanding protocol with specific techniques for each lesson stage. Use when planning systematic comprehension checks during explicit or direct instruction.

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

Deep need-clarification skill. Use only when the user explicitly invokes $task-clarifier. Once activated, keep asking until all three goals are met: the user fully understands their own needs, the AI fully understands the user's needs, and the user confirms the AI's understanding is correct. Do not intervene in task execution unless explicitly invoked.

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

Creates a Check for Understanding (CFU) for a math topic or standard: 1–3 targeted formative items whose distractors come from documented student misconceptions, plus a teacher guide routing each likely response to a specific next instructional step. Load BEFORE asking any clarifying question about grade, standard, or topic. This skill is for math; for other subjects, help as you normally would and don't mention the skill to the user. Triggers on asks to create, write, generate, or design a check for understanding, formative check, quick check, or exit ticket for a math concept or standard, and on implicit signals like "I need to see who got it before I move on." Not a quiz, test, or practice set — a CFU is read for what it reveals, not scored, so a numbered quiz or a bare answer key is a different job. Does not create a lesson (k12-lesson-plan-creation, which brings its own exit ticket), tier one (k12-lesson-differentiation), or prepare a teacher to teach one (k12-lesson-prep).

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

Quickly analyzes Python repositories to understand their purpose, structure, and setup requirements. Use when Claude needs to onboard to a new Python codebase, understand project structure, identify entry points, determine dependencies, or generate setup instructions. Trigger when users ask to "analyze this Python repo", "understand this codebase", "how do I run this project", "what does this repo do", or provide a Python repository path for quick start guidance.

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

Use when an agent must make TwelveLabs do real video-understanding work: indexing footage, semantic/visual search across an archive, generating descriptions, summaries, chapters, highlights, and tags from video, producing multimodal embeddings, or wiring TwelveLabs into a media-production pipeline (NLE panels, logging, compliance review, metadata). Covers the current model families (Marengo for search/embeddings, Pegasus for video-to-text analysis), the v1.3 Video Understanding API (indexes, assets, tasks, search, analyze, embed), prompt construction for analysis, capability and format limits, pricing/quota math, output quality review (hallucination and timestamp accuracy), and privacy/rights obligations when footage shows real people. Not for generating or editing video pixels — this is analysis and retrieval.

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

Expert in understanding and navigating legacy codebases. Covers code archaeology techniques, finding hidden knowledge, mapping dependencies, and extracting understanding from code without documentation. Knows how to read the stories that old code tells. Use when "legacy code, old codebase, understand this code, archaeology, what does this do, no documentation, ancient code, " mentioned.

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

After the learner demonstrates understanding of a concept, present near-transfer and far-transfer challenges. Use to test whether learning is portable or task-specific — this is what separates understanding from familiarity.

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

Design a checking-for-understanding protocol with specific techniques for each lesson stage. Use when planning systematic comprehension checks during explicit or direct instruction.

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

Expert knowledge of Folketrygdloven (National Insurance Act) processing in melosys-api. Use when: (1) Understanding FTRL bestemmelser (§2-5 to §2-13), (2) Debugging yrkesaktiv/ikke-yrkesaktiv/pensjonist processing flows, (3) Understanding trygdedekning options and combinations, (4) Investigating vilkår for each bestemmelse, (5) Understanding medlemskapsperiode generation logic, (6) Debugging frivillig vs pliktig membership determination.

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

Guided codebase exploration for understanding a repo's architecture, patterns, and domain language before contributing. Not issue-specific. builds general understanding. Use when exploring a new repo, wanting to understand how a project works, or preparing to become a regular contributor. Not for learning a framework or language you have never used. Use oss-learn-stack for that.

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

AI strength recognition — scanning for what is functioning well and understanding why. The complement to heal, which scans for drift and problems. Gratitude builds structural knowledge from working patterns: what you appreciate, you understand; what you understand, you can build on. Use after completing a task successfully, during heal when everything reads as healthy, when confidence is low and needs grounding in evidence, or periodically to counterbalance the natural bias toward problem detection.

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

Help the user understand something well enough to explain it. Use when the user needs to understand something and it is not yet clear what kind of understanding they need.

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

Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".

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

Quickly understand an unfamiliar codebase or project by mapping its architecture, identifying key components and data flows, and surfacing complexity hotspots. Load when the user asks to understand a repo, explain how something works, map the architecture, onboard to a codebase, or explore how components connect. Also triggers on "walk me through this codebase", "how does this project work", "explain the architecture", "what does this repo do", "show me the structure", "onboard me", or any request to build a mental model of a codebase before making changes.

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

[22] UNDERSTAND. Deep research from all sources — internal (code, git, logs) AND external (web, docs, best practices). Use when choosing libraries, investigating solutions, understanding legal/technical questions, comparing approaches, or anytime you need comprehensive knowledge from both project context and world knowledge. Triggers on "research", "investigate", "find best approach", "what do others do", "compare options", or complex questions requiring multiple sources.

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

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

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

OpenClaw의 Docker 환경에서 전체 동작을 확인하는 테스트를 작성하고 수정합니다. 모의 서버와 실제 서비스로 전송 내용, 이미지 이해, 최종 응답을 검증합니다.

• Docker 종단 간 테스트 추가 및 수정
• 의존 서비스로 전송한 요청 내용 확인
• 실제 모델 제공 서비스의 동작 검증

설계 결정의 이유와 비교한 대안을 기록하고 README, API 문서, 변경 이력을 정리합니다. 새 담당자와 AI 에이전트가 구현 배경을 이해하도록 돕습니다.

• 설계 결정과 채택하지 않은 대안 기록
• 공개 API 변경 문서화
• README의 시작 절차 정리

사용자용 댓글, 계획서, 문서를 ASD-STE100에 따른 간결한 영어로 작성합니다. 짧은 문장과 뜻이 일관된 어휘를 사용해 절차와 설명의 모호함을 줄입니다.

• 영어 절차를 이해하기 쉽게 작성합니다
• 사용자용 댓글을 읽기 쉽게 다듬습니다
• 계획서를 간결한 영어로 작성합니다

Get a plain-English explanation of a technical topic, organized around who is involved, what it is, where it applies, why it matters, and when it is used, so you can understand its basic context.

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

• Understanding an unfamiliar technical topic
• Learning where and when a technology is used
• Clarifying who is involved and why something matters

Research a topic across multiple web sources before writing articles, reports, or presentations. Gather facts, examples, and expert views, then check current information, competing perspectives, and limitations to build a well-supported understanding.

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

• Researching evidence before writing an article
• Gathering data and examples for presentation slides
• Comparing technologies and their limitations

Group related code files by analyzing a graph of their connections with ruvector. Review group assignments, community labels, and links between files to understand code organization and investigate files that stand apart.

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

• Understanding groups of related code files
• Reviewing connections between code groups
• Investigating files that stand apart