kim-dh2417 User Guide Generator
Create end-user facing guides from the current implemented product.
Use This Skill When
- The user wants
사용자 가이드. - The document should help first-time users, not developers.
- The user wants PC and Mobile docs split.
- The guide should explain real current behavior: routes, flows, popups, loading, toasts, search, and key data shown.
Core Principle
Write from the user's perspective, not the builder's perspective.
Prefer:
- how to enter
- where to click
- what appears
- what data can be seen
- what happens on error
- what feedback appears
Avoid:
- internal implementation detail unless needed for clarity
- code identifiers unless they are useful for traceability
Recommended Document Split
PC_사용자가이드Mobile_사용자가이드
Recommended Content
접속 URL처음 진입 방식화면 기본 구조공통 사용 방법영역별 대표 화면 설명자주 보는 팝업/토스트/오류처음 사용하는 사용자용 추천 흐름
Detail Level
Include concrete behaviors such as:
- login without required fields opens a warning popup
- after confirm, inline errors appear
- search uses partial match behavior where applicable
- search shows loading state
- download shows toast
- detail popup shows specific fields
Source of Truth
Base the guide on the current implementation:
- live browser behavior first when possible
- current routes
- current menus
- current UI copy
Do not rely on old planning docs when they differ from the implementation.