Implement product features in the chukchuk-haksa repository from a natural-language specification. Use for new screens, user flows, API-backed features, WebView counterparts, mocks, or feature-level refactors that must follow this repository's architecture, generated API boundaries, routing conventions, and verification commands. Do not use for a narrow one-line fix or review-only request.
Prepare and create a GitHub pull request for the current repository. Use when the user asks to commit, push, open a PR, write a PR description, or share changes for team review. Inspect the actual diff, include only authorized files, run proportionate verification, push the branch, and create a clear Korean PR that an IT Meister high school student can understand. Do not merge the PR unless the user explicitly asks.
Implement or refine frontend UI from a Figma node in the chukchuk-haksa repository. Use when a request includes a Figma URL, screenshot comparison, typography or color-token matching, responsive card/layout behavior, interaction variants, or pixel-level visual corrections. Do not use when the task is only to edit the Figma file rather than implement code.
Review current frontend changes in the chukchuk-haksa repository from product, architecture, React performance, accessibility, visual fidelity, API-contract, testing, mobile WebView, and operational perspectives. Use for pre-PR review, multi-perspective review, regression analysis, or requests to fix findings through a severity such as P1 or P2. When the user asks only for review, do not modify code; when they specify a fix threshold, implement and verify findings through that threshold.