디자인 스킬

Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every other. Also catches missing keyboard navigation, bullet-dump / wall-of-text failure modes, broken self-containment (external link/script/img). Patches the file in place; never changes the original content (slide text, numbers, named entities are the author's work, not yours).

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

Use when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content. Generates a polished single-file HTML deck in the Editorial Monocle visual direction (warm cream background, serif type, brick-red accent) — designed to be opened in a browser, full-screened, and shared. Does NOT apply to generating skills (that's `openkb skill new`), long-form research reports, or interactive prototypes.

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

Help users transform abstract ideas into actionable project specs that align engineering and design teams on the problem and success metrics.

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

Help users design and maintain a high-performing culture by balancing radical transparency, psychological safety, and a relentless focus on customer delight.

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

Help users design and execute a press strategy that moves beyond vanity metrics to achieve specific business goals like funding, user acquisition, or B2B credibility.

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

Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.

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

Help users reach their first moment of core value by optimizing the first-run experience, removing friction, and aligning product design with psychological triggers.

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

Help users navigate the path from junior product manager to executive leadership by focusing on ownership, cross-functional influence, and intentional career design.

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

Help users navigate the manual, unscalable journey of finding and closing their first B2B customers. This guide focuses on leveraging personal networks, co-creating with design partners, and obsessing over early user success.

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

Help users design and execute a high-signal interview process that prioritizes real-world performance over superficial charisma or pedigree.

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

Help users design high-performing product and engineering organizations by choosing the right reporting models, team sizes, and cross-functional partnerships. It focuses on reducing friction and maximizing ownership through structural clarity.

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

Help users interact with probabilistic models by designing interfaces that manage fluidity, intent, and agency while maintaining trust and control.

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

경영 회의와 제안용 슬라이드를 설계 규칙과 62종 HTML 구성 요소로 만듭니다. 배치를 검사해 HTML과 PDF로 제공하며, 요청하면 기존 자료의 서식에 맞춘 PPTX도 만듭니다.

• 경영 회의용 발표 자료 만들기
• 제안 수치를 표와 그래프로 설명하기
• 기존 PowerPoint에 페이지 추가하기

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", "check my site against best practices", or "web interface guidelines".

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

Implements error handling patterns, structured logging, retry strategies, circuit breakers, and graceful degradation. Use when designing error handling, setting up logging, implementing retries, adding error tracking, or when asked about error boundaries, log aggregation, alerting, or resilience patterns.

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

Designs REST and GraphQL APIs including endpoints, error handling, versioning, and documentation. Use when creating new APIs, designing endpoints, reviewing API contracts, or when asked about REST, GraphQL, or API patterns.

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

Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.

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

Designs database schemas, indexing strategies, query optimization, and migration patterns for SQL and NoSQL databases. Use when designing tables, optimizing queries, fixing N+1 problems, planning migrations, or when asked about database performance, normalization, ORMs, or data modeling.

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

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

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

用户要一份文档时用：报告、提案、计划、简历、求职信、信件、合同、制度、表单、模板、作文、手册、指南、操作说明、速查表这类要保留、共享、评论、导出或打印的文字。用 docs_* 工具在工作目录建一份文档，先发骨架再一节一节填，线程里出现文档卡片，用户在功能区编辑与评论。也用于按文档评论或请求改已有文档。聊天里问的计划、对比、摘要留在聊天；幻灯片用 slides，视觉设计用 design。

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

用户要做界面、网页、海报、图表或信息图、示意图、原型这类视觉设计稿时用：在工作目录写一份设计稿（canvas.json 加每块画板一个 .dc.html），校验通过后线程里出现设计稿卡片，用户在功能区预览、编辑与标注。也用于按用户的意见或设计稿标注改已有的设计稿。幻灯片不用它（用 slides），视频画面里的字卡与动效也不用它（用动效图形）。

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

用户要建立或修改设计系统时用：品牌的颜色、文字样式、间距与圆角 tokens，给智能体看的品牌手册 README，bundle 与预览，标志、图标与字体。在工作目录写一个设计系统目录（design-system.json 加 tokens.json、README.md、components/、assets/、fonts/），可以从代码仓库或设计工具里的真实来源整理；图片、视频与 PDF 导入设计系统的素材库，校验通过后线程里出现设计系统卡片，用户在功能区预览与编辑；做好的设计系统可以装进设计稿。

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

Compare interface designs and find structural friction. Use when: a change spreads across modules or a boundary is unclear. For code changes, use Refactor.

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

Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.

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