القائمة
Create a new TanStack Router route file (web) that delegates to a domain. The route stays thin — the actual UI lives in the domain.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | scaffold-route |
| description | Create a new TanStack Router route file (web) that delegates to a domain. The route stays thin — the actual UI lives in the domain. |
The user wants a new web route. TanStack Router file-based, located in apps/web/src/routes/.
settings, tasks, agent.$agentId)_app for authed app routes; use empty/none for top-level routes like onboarding, settings)If anything is missing, ask once.
apps/web/src/routes/_app/<path>.tsxapps/web/src/routes/<path>.tsxThe path may include $paramName segments (TanStack convention) and . separators (which become / at runtime).
import { createFileRoute } from '@tanstack/react-router'
import { <DomainComponent> } from '@/domains/<domain>'
export const Route = createFileRoute('<route-pattern>')({
component: <DomainComponent>,
})
<DomainComponent> is whatever the domain's index.ts exports as its top-level view (often <DomainName>Page or just <DomainName>). Check the domain's README "Public surface" to find the right export name. If the domain has no view export yet, refuse — ask the user to add one first.
@/domains/<domain> — never relative paths.index.ts. If not, refuse and explain.pnpm typecheck to confirm the route compiles.@/domains/x/components/Foo). The eslint boundary rule will reject it.Generate a commit message that explains WHAT changed and WHY in plain language. No code references. Humans read these, not machines.
Generate a PR description that explains WHAT is being built, WHY, and the high-level approach. Written for humans who will not read the code.
Create a new domains/<name>/ folder following the Huxflux domain pattern. Targets web, server, mobile, or shared. For server domains, also creates the routes plugin and registers it.
Run the structural check (check-domains) against the monorepo or a specific domain. Use after editing a domain to verify it still conforms.
Enter discussion mode. No code is written, no files are created or edited. Read the codebase to ground the conversation, reason through trade-offs, surface edge cases, brainstorm. Use when the user wants to think before building.
Establish shared understanding of a task before writing any code. Restate the ask, surface ambiguity, ask 1-3 structured questions, propose an approach with trade-offs, get sign-off. Use at the start of any non-trivial task.