kim-dh2417
- 15 skills
- 0 followers
- 6 hours ago last updated
- ▌ Agent Role Guide · kim-dh2417 bundleUse when the user wants clear sub-agent role separation for project work, especially around planning, design, development, and QA responsibilities. This skill defines what each role owns, which built-in agent type to use for each role, how to split work cleanly, and how to avoid overlap between parallel agents.
- ▌
- ▌ Prototype Builder · kim-dh2417 bundleUse when the user wants to build or expand a frontend prototype from planning, IA, and screen design docs, especially for requests like `프로토타입 만들어줘`, `문서 기반으로 화면 추가해줘`, `빠르게 시연용 화면 붙여줘`, or `IA 기준 누락 화면 메워줘`. This skill turns requirements and design docs into a runnable prototype by aligning routes, menus, representative pages, placeholder flows, and document updates.
- ▌ Enterprise UI Design · kim-dh2417 bundleUse when the user wants 기업형 디자인, 사내 시스템 디자인, 업무용 UI, 백오피스 UI, 관리자 화면, 운영 시스템 화면, or other internal business system screens with consistent enterprise UI standards. This skill enforces clarity of information, simplicity, visibility, user convenience, and consistency with desktop-first, workflow-oriented, table-and-filter-friendly, status-driven UI patterns.
- ▌ User Guide Generator · kim-dh2417Use when the user wants end-user guides, onboarding docs, 처음 사용자용 가이드, PC/Mobile usage guides, or practical screen-by-screen instructions based on the current implementation rather than planning documents.
- ▌
- ▌ Spec First Development · kim-dh2417 bundleUse when the user asks for actual frontend development or frontend changes based on approved planning, IA, design, or prototype screens, especially for requests like `프론트 개발해줘`, `이 화면 구현해줘`, `UI 수정해줘`, or `프로토타입 참고해서 실제 화면 만들어줘`. Update planning docs first when requirements changed, then design docs, then implement frontend code, verify locally, and keep backend work out of scope unless the user explicitly asks for a separate backend task.
- ▌ Cursor Prd Fsd Frontend · kim-dh2417 bundleUse when the user wants to follow or migrate a Cursor-style frontend rule pack into Codex, especially for `.mdc` or `.cursor/rules` based workflows. Covers PRD-first development, PRD -> test -> implement workflow, FSD architecture rules, shadcn UI conventions, Next.js/React best practices, Vitest/RTL testing standards, and PRD samples for auth, sidebar, equipment, notice, maintenance-intake, and work-permit screens. Triggers include requests about Cursor rules, Cursor settings migration, .mdc files, PRD 먼저, FSD, shadcn, frontend rule packs, and sidebar/auth/workflow PRDs.
- ▌ Prd Ia Checklist Review · kim-dh2417Use when creating or reviewing PRD, IA, screen inventory, or feature inventory from requirements documents and the user wants completeness, traceability, or no missing requirements. Build a PRD-based checklist first, then review IA/screens/features against it, and record statuses like 반영, 부분반영, 미반영, 재검토 before treating the document as complete.
- ▌ Developer Worklog Writer · kim-dh2417Use when the user wants a developer-style work log, daily engineering report, 업무일지, or progress summary that records work completed, changes made, validation performed, issues, risks, tools used, and next steps. Best for end-of-day summaries and OneDrive worklog updates.
- ▌ Responsive QA Playwright · kim-dh2417Use when the user wants responsive QA, mobile/desktop verification, viewport-based UI inspection, or iterative responsive fixes using Playwright. Best for checking layout breakage, sidebars, tables, forms, modals, and mobile interaction patterns.
- ▌ Phase Driven UI Refinement · kim-dh2417Use when the user wants UI or prototype work done phase-by-phase with a checklist, in strict order, including implement -> verify -> refine -> then move to the next item, and only after finishing a whole phase ask about the next phase.
- ▌ Feature Review · kim-dh2417 bundleUse when the user asks to review implemented features against planning, IA, or screen design docs, especially with prompts like `기능 검토해`, `화면 검토해`, `구현 잘 됐는지 봐줘`, or `누락된 기능 확인해줘`. This skill uses Playwright first when possible, then compares the live app, routes, menus, and pages against planning and design docs and reports missing screens, menu gaps, incomplete behavior, and implementation mismatches.
- ▌ Ask Before Push · kim-dh2417 bundleUse when work is complete and git actions may follow. Ask before any git commit or git push unless the user explicitly instructs commit and/or push in the current request.
- ▌