'glossary' 검색 결과

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 domain glossary from conversation context, choosing canonical terms and flagging ambiguity. Use when the user asks to define domain terms, build a glossary, clarify terminology, create a ubiquitous language, or mentions domain modeling or DDD.

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

코드 구조를 살펴 이해와 테스트를 어렵게 하는 부분의 개선안을 도표가 포함된 HTML 보고서로 정리합니다. 후보를 선택하면 제약과 설계 결정을 대화로 구체화합니다.

• 자주 변경하는 영역의 설계 검토
• 리팩터링 방안을 도표로 비교
• 테스트하기 쉬운 모듈 설계 검토

코드 검토자를 위한 풀 리퀘스트 본문을 작성합니다. 도식과 변경 비교, 변경 전후의 동작 증거를 담고 되돌리기 쉬운 정도와 영향 범위를 짧게 정리합니다.

• 풀 리퀘스트 본문 작성
• 파일 트리와 변경 비교로 구조 설명
• 화면 변경 전후의 증거 제시

기능 추가나 버그 수정을 실패하는 테스트와 최소 구현 순서로 진행합니다. 호출자가 쓰는 공개 인터페이스로 동작을 검증하고 내부 구조에 의존하지 않는 테스트를 만듭니다.

• 테스트를 먼저 작성해 기능 추가
• 버그 재현 테스트부터 수정 시작
• 통합 테스트 대상 인터페이스 선정

개발 스킬의 첫 사용에 앞서 작업 관리 위치, 분류 라벨, 용어집과 설계 결정 기록의 위치를 확인합니다. 사용자 검토를 거쳐 저장소 공통 설정 문서를 정리합니다.

• 개발 스킬의 초기 설정
• 작업 관리 위치와 분류 라벨 정리
• 용어집과 설계 결정 기록의 위치 결정

Maintain clear business definitions and relationships in an existing glossary or CONTEXT.md. Flag unresolved meanings and refer lasting design choices to the existing architecture decision record workflow, keeping terminology separate from decision rationale and task status.

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

• Document business terms that need repeated explanation
• Clarify terms with multiple meanings
• Track domain interpretations awaiting confirmation

Review HTML lists of terms and descriptions, finding dt and dd elements used without a containing dl. Help correct the structure so assistive technologies can associate each term with its description, and explain how to verify the fix.

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

• Check HTML structure in a glossary
• Review lists of metadata labels and values
• Fix dt and dd elements missing a containing dl

Translate selected pages or an entire English research paper into a simplified Chinese PDF made from images. It aims to preserve page layout, figures, and equations while retaining each original page’s dimensions and orientation.

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

• Reading an English paper in simplified Chinese
• Translating selected pages of a paper
• Keeping figures and equations alongside translated text

Helps build Python workflows for translating Word, PDF, Excel, PowerPoint, and other documents while preserving formatting. Covers Azure batch translation, multiple target languages, terminology glossaries, and checks for job progress and document errors.

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

• Translating batches of documents while preserving formatting
• Translating documents into multiple languages
• Applying a glossary for specialized terminology

Guide a development brief through specification, dependent tickets, implementation, review, and verification. Coordinate parallel work while keeping human approval at key decisions and recording agreed vocabulary, business rules, and the reasons behind technical choices.

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

• Turning a development brief into a specification and tickets
• Coordinating parallel implementation across dependent tickets
• Approving acceptance criteria and testing boundaries

Plan large sets of search-focused pages using templates and data, such as location guides, comparisons, and directories. Define unique content for each page, URL patterns, internal links, and quality checks before launch.

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

• Planning service pages for multiple locations
• Designing templates for product comparison pages
• Structuring a directory or industry glossary

Translate FastGPT documentation from Chinese into natural English for North American readers. Follow the shared product glossary, preserve document structure and code, synchronize navigation files, and check for missing translations or English pages that need updates.

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

• Updating English docs after changes to Chinese pages
• Translating a specified documentation folder
• Synchronizing English navigation with translated pages

Translate text and articles with three modes, from a direct translation to a workflow with review and polishing. Apply custom glossaries, tailor the tone to readers, and preserve Markdown formatting in the final translation.

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

• Translate short text quickly
• Translate articles with consistent terminology
• Review and polish translations for publication

Plan and audit large sets of pages generated from structured data. Assess source quality, template uniqueness, URLs, and internal links, then identify thin content and unnecessary search indexing with prioritized recommendations and staged publishing guidance.

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

• Plan directory or glossary pages from structured data
• Audit repetitive content across generated pages
• Design URL patterns and automated internal links

Add business knowledge missing from a Wren project's database definitions. Compare source documents with existing context, then add explanations, rules, SQL examples, and proposed metrics through guided questions or an automatic mode with an audit report.

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

• Documenting status codes, units, and NULL meanings
• Adding business knowledge from handbooks and glossaries
• Defining aggregation metrics such as ARR or DAU

Turn a codebase into a browser-based course for people without programming experience. Build interactive lessons with animated data flows, quizzes, glossary explanations, and code paired with plain English to explain how the project works.

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

• Understand how an app built with AI works
• Create a learning course from a GitHub project
• Learn data flow through animations and quizzes

Build features or fix bugs by writing one failing test, then the minimum code needed to pass it. Test agreed public interfaces, the boundaries callers use, to check behavior without depending on internal implementation details.

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

• Building a feature through test-first development
• Fixing a bug with a failing test first
• Writing behavior-focused integration tests

Draft or revise pull request descriptions that show the change, evidence of its behavior, and merge risks. Use concise diagrams, trees, or diffs alongside before-and-after results to help reviewers assess impact and how easily changes can be reversed.

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

• Draft a description for a pull request
• Explain a refactor with a tree or diff
• Present before-and-after evidence for a fix

Review a codebase for design friction and compare refactoring candidates in an HTML report with before-and-after diagrams. Then explore a chosen candidate through questions about constraints, module design, and testing.

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

• Find design problems in frequently changed code
• Compare refactoring candidates with diagrams
• Explore constraints and tests for a chosen improvement

Model and publish semantic definitions in Auto Ontology. Use for terms, relationships, measures, imports, and governed results—not deployment or querying.

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

[omh] Translated product or content release: make a product or content release locale-ready with terminology, cultural-fit, and quality-review guidance. Use when the user says: localization review, translation QA, locale glossary, 현지화 검토, 번역 QA, 용어집.

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

[omh] Unfamiliar repository needing a guided tour: create a repo map, reading path, glossary, risk map, and first-task runway for unfamiliar codebases. Use when the user says: codebase-onboarding, codebase onboarding, repo onboarding, repository onboarding, codebase tour, code tour, new repo orientation, understand this repo.

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

SUPERSEDED by /claudex-loop (formerly /crucible; its docs-aware mode covers this variant) — prefer that skill unless you explicitly want this one. Two-act plan hardening with living documentation. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan, one question at a time, challenging it against your project's existing domain model and glossary (CONTEXT.md), sharpening fuzzy terms, stress-testing with concrete scenarios, cross-referencing code, and updating CONTEXT.md + ADRs inline as decisions crystallise. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-with-docs-codex", "grill me against the docs then have codex review", "stress-test this against our domain model then get a second model on it", or is about to build something high-stakes in a project with established terminology/ADRs and wants alignment, documentation, AND a cross-model sanity check. Builds on Matt Pocock's grill-with-docs (MIT). NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.

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