菜单
Plan and review EveryGSM-client-v2 architecture, Feature-Sliced Design layering, route ownership, public exports, import direction, client/server boundaries, and minimal implementation scope. Use for any EveryGSM feature, refactor, routing, dependency, or architecture decision.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implement and review EveryGSM-client-v2 API/data flow: apiUrls, server apiFetcher, Axios client, TanStack Query hooks, query keys, Zod schemas, response types, initialData hydration, auth cookies, and client/server data boundaries. Use whenever a task touches backend contracts, requests, mutations, forms, or domain data.
Review EveryGSM-client-v2 changed files using dynamically discovered .claude/rules, FSD layering, UI conventions, API/data coherence, form/schema alignment, route/link checks, security basics, and validation results. Use for code review requests, staged diff review, pre-PR review, and after multi-file implementation.
Create actual EveryGSM Git commits by inspecting changed files, splitting logical units, staging the right files, and running git commit with project Conventional Commit messages. Use when the user explicitly asks to commit, make a commit, split commits, or commit staged/unstaged changes. Do not push.
Coordinate the EveryGSM-client-v2 agent team for frontend features, bug fixes, refactors, UI work, API/data work, QA, code review, debugging, branch names, actual commits, PR creation, PR review comment replies, routing, forms, TanStack Query, Zod, Axios, and FSD architecture. Use this skill for EveryGSM implementation tasks, reviews, reruns, updates, revisions, partial reruns, follow-up fixes, Git workflow tasks, and requests to improve previous results. Simple one-off questions may be answered directly.
Verify EveryGSM-client-v2 changes with pnpm format:check, pnpm lint, pnpm build, FSD import review, route/link coherence, API-hook-type coherence, form/schema alignment, and client/server boundary checks. Use after implementation, during reviews, for reruns, and whenever a task risks regressions.
Collect EveryGSM GitHub PR review comments, assess each comment against project rules, apply valid fixes when safe, optionally commit and push fixes, and post Korean replies with gh api. Use only when the user explicitly asks to address PR review comments or reply to review comments.
| name | frontend-architecture |
| description | Plan and review EveryGSM-client-v2 architecture, Feature-Sliced Design layering, route ownership, public exports, import direction, client/server boundaries, and minimal implementation scope. Use for any EveryGSM feature, refactor, routing, dependency, or architecture decision. |
Use this skill to keep changes aligned with the repository's layered structure and to prevent unnecessary refactors.
EveryGSM-client-v2 is a Next.js App Router frontend using:
Layer order:
app -> views -> widgets -> features -> entities -> shared
Imports must move downward through this stack. Do not add same-layer imports.
src/app.src/views.src/widgets.src/features.src/entities.src/shared.app: route files, layouts, metadata, guards, and server entrypoints.views: page-level composition.widgets: reusable page sections.features: user actions such as registration, sign-in, liking, and filters.entities: project and user domain models, API calls, query hooks, and domain UI.shared: reusable clients, hooks, stores, utilities, styles, constants, and assets.initialData to the relevant client query if the existing pattern supports it.Write a short plan that includes:
Avoid long file inventories unless the task spans many modules.