simplecore

Use when reconciling implemented screens against a project's wireframe board frame by frame, when building screens from a board no code reaches yet, when working through or resuming a parity / remaining-screens list, or when setting a project up for such a walk — 보드 대조 · 화면 대조 · 프레임 대조 · SCREEN-PARITY · 처리할 화면 · 남은 화면 대조 · 한 구역을 처리한다. Requires a project that already has a wireframe board; the application itself need not exist yet. NOT for authoring or syncing a board (simplecore:wireframe-boards), and NOT for auditing one feature area in one sitting (the project's own e2e skill).

Use when building an application from a wireframe board in dependency order — chapter by chapter, foundation first — and when running the persona tests that close each chapter. Also for resuming a build across sessions, deciding which chapters may run in parallel, and generating or regenerating the chapter set from the board — 시나리오 개발 · 챕터 개발 · 단계별 개발 · 개발 순서 · 페르소나 시험 · 병렬 개발 · 어느 챕터부터 · 다음 챕터. Requires a wireframe board and a chapter set derived from it; the application itself need not exist yet. NOT for authoring or syncing the board itself (simplecore:wireframe-boards), and NOT for auditing one feature area in one sitting (the project's own e2e skill).

Use for virtually EVERY task — all user-facing output in this environment is Korean, and this skill governs ALL Korean output. Assistant replies and explanations, documentation, translations, proofreading, README/design docs/release notes, commit-adjacent prose, and Korean glossary (GLOSSARY.md) management. Invoke it even for ordinary answers with no document work, and always before writing, translating, reviewing, or auditing any Korean document. Also use when the user mentions 번역투, awkward Korean, terminology consistency, or asks to re-check documents against glossary rules. Covers UI copy as well — screen wording in i18n resources, message bundles, and wireframe board sources, including a full sweep of every screen string (화면 문구 검토 · 카피 검수 · UX 라이팅 · 문구를 자연스럽게). Text labels inside SVG diagram files (embedded or standalone) are audited and corrected to the same standard as the documents they illustrate. 한국어로 답변·설명·문서 작성·번역·교정·검수·용어사전 관리를 하는 모든 상황에서 사용한다 — 일반 답변도 예외가 아니다.

Create diagrams as SVG (also ASCII) — flowcharts, sequence/state/class/ER, system and architecture diagrams, pipelines, network and infrastructure layouts. Use when asked to draw, render, or diagram a system, flow, or structure. Covers hand-crafted SVG and JSON-spec auto-layout for precise architecture pictures, Mermaid auto-layout for structured diagrams from text, and SVG checks that catch missing or oblique arrowheads, text overflow, and clipped content before delivery. Also covers figures embedded in a document — one canvas width and one type scale across the whole set, with the generator versioned in the project rather than written to a scratch directory, and bundles the full Lucide icon set for marking a component inside a figure (an AI part especially). Triggers on "draw diagram", "create flowchart", "show architecture", "system diagram", "visualize flow", "SVG diagram", "ASCII diagram", "mermaid", "다이어그램", "아키텍처 그림", "도식화", "구성도", "그림 그려", "문서에 넣을 그림", "그림 규격 통일", "아이콘 넣어", "AI 아이콘".

Use when drawing or changing low-fidelity PHONE, TABLET, or DESKTOP/WEB wireframes as one self-contained HTML board — wireframes, screen mockups, lo-fi screens, UI sketches, a screen inventory or flow board derived from a design or spec document, 와이어프레임 · 화면 목업 · 로파이 · 태블릿 화면 · 웹 화면 · PC 화면 · 데스크톱 화면 · 관리자 화면 — including when the word "wireframe" is absent but the deliverable is screen layouts drawn before implementation. Also use when implementing a screen from a board, checking an implementation against one, syncing a board after a screen / dialog / state / flow changes, or reviewing a board as its personas (페르소나 검토 · 사용자 관점 검토 · 담당자 관점 · UI/UX 관점 · 화면 사용성 검토). Propose it when a substantial new UI effort has no board yet. NOT for high-fidelity visual design or production React components.