'glossary' 검색 결과

구체적인 사례와 코드 대조로 프로젝트의 업무 용어와 개념 경계를 명확히 합니다. 합의한 정의를 용어집에 기록하고 필요에 따라 중요한 설계 결정의 이유도 남깁니다.

• 모호한 업무 용어 정리
• GLOSSARY.md 생성과 갱신
• 업무 정의와 코드의 일치 여부 확인

Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.

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

• Clarifying ambiguous project terminology
• Creating or updating GLOSSARY.md
• Checking concept boundaries against code and edge cases

Ask an agent to restate an unclear message with more background, using the conversation's language and the project's glossary. It applies simplified technical writing guidance to help explain how the discussion reached its current point.

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

• Asking for a clearer explanation of the previous message
• Adding background to understand the reasoning
• Aligning explanations with project glossary terms

직전 설명을 이해하기 어려울 때 배경을 보충해 다시 설명합니다. 간소화된 기술 영어 표준과 프로젝트 용어집을 따라 대화의 흐름을 전달합니다.

• 직전 설명을 이해하기 쉽게 다시 듣기
• 대화 흐름을 이해할 배경 설명 받기
• 프로젝트 공통 용어로 설명 받기

Sets up shared project rules and a glossary so people and AI agents work from the same context. It preserves existing documents, introduces additional records when needed, and provides a check mode to audit inconsistencies.

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

• Setting up shared rules for a new development project
• Moving project knowledge out of chat history
• Preparing documentation for new contributors

Translate English skill documentation into Simplified Chinese while preserving commands, code, paths, and identifiers. Follow a shared glossary, refresh changed content, and review document structure and public indexes to keep the localized edition consistent.

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

• Translate a skill file or README into Simplified Chinese
• Refresh localized documents after upstream content changes
• Apply approved terminology consistently across documents

계획이나 설계를 깊이 묻는 질문으로 구체화하면서 설계 결정 기록과 용어집도 작성합니다. 하나의 대화에서 검토와 문서화를 함께 진행할 때 사용합니다.

• 질문에 답하며 계획 구체화
• 대화로 설계 심층 검토
• 검토 중 설계 결정 기록

Update Chatbox Pro interface translations by reviewing code changes and the surrounding screen context. The skill identifies affected translation keys, follows a shared glossary, and edits language JSON files while preserving placeholders and formatting tags.

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

• Translate interface text added in uncommitted changes
• Update translations for a specific commit range
• Refresh translations after English text changes

Turn talk scripts, slides, and concept notes into reference sheets with section navigation, definitions, shareable links, a glossary, and six to ten anticipated questions with short answers for live Q&A and attendee follow-up.

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

• Preparing short answers for a talk's Q&A session
• Creating a reference sheet to share with attendees
• Keeping definitions handy during a live presentation

Use when building reusable Obsidian glossary notes from an existing paper source manifest, optionally with a raw-sections override, especially when a reader needs a reviewed shortlist before glossary notes and article links are changed.

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

Deprecated compatibility entry for Glossary Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Glossary Page.

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

This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", "map", "travel times", "routes", "calendar", "moons", "seasons", "naming language", "conlang names", "trade routes", "supply lines", "magic cost", "add a glossary term", "glossary", "invented word", or wants to develop any aspect of a story's world and setting. NOT for a glossary for translators (use adaptation).

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

Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term definitions, avoid-aliases, and relationships so agents use consistent, concise language. This skill should be used when starting a new project, when domain terminology is inconsistent across sessions, when the user says "build a glossary", "define our terms", "shared vocabulary", or "domain language", or when an existing CONTEXT.md needs updating after new domain concepts emerge.

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

Draft a pull request description from existing project records and verification results. Present the change with a compact visual, before-and-after evidence, rollback details, and its wider impact so reviewers can assess the work.

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

• Drafting a pull request description
• Explaining a refactor with a compact diagram
• Presenting existing before-and-after check results

Turn a plain description of a web animation into the matching term from a curated glossary. Get a short definition and distinctions between similar effects so you can describe the motion to an AI or designer.

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

• Find the name of an animation you have seen
• Describe a desired motion effect in an AI prompt
• Distinguish between similar animation terms

Refine a plan or design through an ongoing interview while creating documentation. The skill combines grilling and domain-modeling to produce architectural decision records, which capture design decisions, and a glossary of relevant terms.

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

• Refine a plan through follow-up questions
• Explore a design through an interview
• Record design decisions during discussion

Doctrine for drafting and keeping working-group docs under `docs/wg/**` — RFC/RFD specs and findings/research/glossary. A WG doc is a language-agnostic, code-agnostic study of a domain: it argues *why* and defines *what*, never *how in our code*. Use when writing or editing anything under `docs/wg/`, an RFC/RFD, a spec, a design note, a glossary, or research findings — including "write up the design", "document the spec", or "capture what we learned". Not for plans/TODOs (untracked `*.plan.md`), user docs, or SDK API refs — use `docs` to route those.

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

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

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

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

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

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

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

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

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

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

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

Use this skill when a set of policies, procedures, plans and registers has grown in pieces and someone asks "check our documents for contradictions", "are our policies consistent", "the retention periods don't match", "which severity scale is right", "harmonise our ISMS documents", "cross-check the incident plan against the policy" or "clean up our documentation before the audit". Extracts the checkable facts from every document (periods, deadlines, scales, roles, labels, references), finds contradictions, naming drift and broken references, proposes which document owns each fact, and drafts a glossary and a fix list for the owners.

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

Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.

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