메뉴
Loads project context at session start (structure, governance, active jobs, enforced boundaries). Use for a new chat, ambiguous tasks, or before larger refactors. Not human onboarding (start) or pre-merge gates (validate gate depth).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | prime |
| description | Loads project context at session start (structure, governance, active jobs, enforced boundaries). Use for a new chat, ambiguous tasks, or before larger refactors. Not human onboarding (start) or pre-merge gates (validate gate depth). |
Load project context at the start of a new session. Build an understanding of this boilerplate’s structure, governance, and active state before tackling tasks.
When to use: New chat, ambiguous task, or before larger refactors.
Related: For architecture/quality gate, use .agents/skills/validate/SKILL.md (auto-selects gate depth). For planning features, use .agents/skills/plan/SKILL.md. For onboarding a human, use .agents/skills/start/SKILL.md.
Align with project rules and architecture so work does not violate enforced boundaries (ESLint boundaries, dependency-cruiser, structure whitelist).
git ls-files (large repos: in PowerShell use git ls-files | Select-Object -First 150 instead of head).ARCHITECTURE.md (folder layout, TanStack Query, layers, path aliases).documentation/DOC_INDEX.md (SSOT map, quick links).documentation/DOC_APP_VISION.md. If the vision status line is still DRAFT, state in Actionable insights that feature/plan ambiguity should be resolved by filling that file (or running .agents/skills/start/SKILL.md § App vision) before major product decisions.src/features/ — this boilerplate ships with auth and setup only; forks may add more. Do not use a fixed feature list from another repo.index.html, src/main.tsx, src/App.tsx (provider order: QueryProvider → AuthProvider → BrowserRouter)..cursor/rules/INDEX.md..cursor/rules/architecture/RULE.md (layers, path aliases @/*, import direction, structure whitelist)..cursor/rules/file-placement/RULE.md — validation uses projectStructure.config.cjs (not .js).package.json..dependency-cruiser.cjs (forbidden upward imports, hooks/services/utils rules, warnings on direct service use from components).git log -n 10 (full commit messages: subject and body; do not use --oneline)git status -sb (confirm branch: feature work should not be on main; see .cursor/rules/workflow/RULE.md)documentation/jobs/ for active work (e.g. documentation/jobs/temp_job_*/) when relevant.Deliver a concise, scannable summary:
package.json).package.json → version).src/features/ only (verified, not assumed).ARCHITECTURE.md and architecture rule.forbidden rules from .dependency-cruiser.cjs.documentation/jobs/ if relevant).documentation/jobs/.src/features/ changes; keep prime generic.pnpm validate:docs (cursor doc references). Prefer paths that exist in this repository.Not prime | Use instead |
|---|---|
| Human first-time setup | start |
| Product vision Q&A | grill-me |
Write DEVELOPMENT_PLAN.md | plan |
| Commit / push | finish / push |
Next: plan, plan § Refine, or grill-me per router gates — not implement alone.
Bundles all uncommitted work from multiple Cursor agent threads on the same branch and checkout into one finish commit, then pushes. Use when the user runs /bundle-ship, /finish-all, or asks to finish and push everything across threads on one checkout.
Interview the user until scope edges and interaction boundaries are aligned and the decision tree is resolved. Focuses on where the feature stops, what it will NOT do or touch, and how it meets other functionality. Chat-only alignment — authors no artifact. Use to stress-test scope/boundaries before feature or plan, or when the user says "grill me".
Picks the next action and skill, then invokes it (read that SKILL.md and execute the workflow in the same turn). Mid-thread: continue the logical next step on active work. Idle or new: fall back to gates and app-tasks.json backlog. Maps situations to project, user, and plugin skills; resolves overlaps. Product context SSOT: documentation/DOC_APP_VISION.md. Use when the user types /router, asks which skill to use, starts ambiguous work, or routes slash commands to SKILL.md files. Bare /router is next-action dispatch (not finish).
Challenges and simplifies a concrete feature to reduce steps, clicks, and cognitive load (flow and code modes by default). Use when the user targets a workflow and asks whether it is overbuilt, or runs /challenge.
Systematically audit the codebase for consolidation, abstraction, and redundancy removal opportunities across features. Use when the user asks to find duplication, consolidate code, audit for redundancy, reduce repetition, or identify shared patterns that should be unified.
Structured scientific debugging for runtime bugs, regressions, flaky behavior, frontend/backend failures, Supabase/RLS/Auth/Storage issues, and user-reported errors. Use when the user invokes /debug, asks to debug, reports an error, or describes inconsistent behavior.