메뉴
Clarify and pursue a goal end-to-end. Use when the user states an outcome they want achieved ("make my portfolio showcase me as X", "get this shippable"). Restates the goal, defines success criteria, plans steps, executes, and verifies the goal was actually met.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Diverge then converge on ideas before building. Use when the user wants options, concepts, directions, or "ideas for X" — generates multiple distinct approaches, pressure-tests them against goals/constraints, then recommends one with rationale. Pairs well with ui-ux-pro-max and goal.
Verify code against current, real library documentation before using an API. Use when working with a specific library/framework version and you must not guess APIs. Encourages checking official docs/types for the installed version. NOTE - the real Context7 is an MCP server; see setup notes below to enable live doc lookup.
Translate a design intent into clean, idiomatic frontend code. Use when building or refactoring UI components — enforces composition, design tokens, responsive layout, accessibility, and matching the surrounding codebase's conventions. For React/Vue/Tailwind/CSS work.
A rigorous correctness-and-detail finishing pass. Use when the user wants work to be "impeccable", flawless, production-grade, or polished to a high standard — verifies builds/lints/tests pass, hunts edge cases, checks accessibility and consistency, and refuses to claim done without proof.
Apply restrained design taste to a UI. Use when the user wants the interface to feel tasteful, elegant, minimal, or "not overdesigned" — favors simplicity, whitespace, a tight palette, subtle motion, and removing decoration that doesn't earn its place.
Senior UI/UX craft pass for web frontends. Use when the user asks to upgrade, polish, redesign, or "make it premium/pro" — applies design-token systems, visual hierarchy, spacing rhythm, accessible color/contrast, motion restraint, and responsive layout. Best for React/Tailwind/CSS projects.
| name | goal |
| description | Clarify and pursue a goal end-to-end. Use when the user states an outcome they want achieved ("make my portfolio showcase me as X", "get this shippable"). Restates the goal, defines success criteria, plans steps, executes, and verifies the goal was actually met. |
Keep work anchored to the user's actual desired outcome, end to end.
Invoke when the user gives an outcome/objective rather than a single mechanical task — especially fuzzy goals like "make it showcase me well".
Restate the goal in one sentence, in concrete terms. If it's ambiguous, state the interpretation you're proceeding with (and ask only if a wrong guess would waste real work).
Define success criteria — a short, checkable list of what "done" means for THIS goal. Example for "showcase me as a Full Stack AI Engineer": role is unmistakable above the fold; AI/LLM work is foregrounded; proof (projects, awards) is visible; contact path is clear; site is fast and accessible.
Plan the minimal set of steps that satisfy the criteria. Sequence them; note dependencies.
Execute, keeping every change traceable to a criterion. Don't add scope that doesn't serve the goal.
Verify against the criteria, not against "did I write code". Walk the list and confirm each item is met, with evidence (build output, the rendered result, the specific lines).
Report: restate goal → criteria → status of each → anything left.
A goal isn't met because tasks were performed; it's met because the criteria are satisfied. Check the criteria, not the activity.
