بنقرة واحدة
templatecentral-scaffold
Use when creating a new FastAPI, NestJS, Next.js, or Vite+React project from scratch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when creating a new FastAPI, NestJS, Next.js, or Vite+React project from scratch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding any capability to a FastAPI, NestJS, Next.js, or Vite+React project — auth, database, tests, components, logging, and more.
Use when running database migrations, migrating conventions, or extracting a Next.js backend to a dedicated service — FastAPI or NestJS.
Use when reviewing code quality, naming conventions, validation patterns, drift, or full-stack type contracts in a templateCentral project.
Use when auditing the templateCentral plugin repo itself — ecosystem accuracy, conventions, harness. Repo-internal contributor skill.
Use when writing or modifying files under skills/ — walks through CONVENTIONS.md authoring checklist. Repo-internal contributor skill.
| name | templatecentral:scaffold |
| description | Use when creating a new FastAPI, NestJS, Next.js, or Vite+React project from scratch. |
Step 0 — If the user did not name a stack: ask before assuming. Pose at most two questions ("Frontend, backend, or full-stack? Any language preference?"), then recommend from this table, state the one-line reason, and confirm before Step 1:
| Use case | Recommend |
|---|---|
| Interactive product UI, SSR, or full-stack web | nextjs |
| Client-only SPA or internal dashboard | vite-react |
| Python REST / async API | fastapi |
| Enterprise TypeScript API (DI, Swagger) | nestjs |
Full-stack → scaffold frontend and backend as two separate runs.
Step 1 — Identify the stack: fastapi, nestjs, nextjs, or vite-react.
Step 2 — Load in order. Replace <skill-dir> with this skill's own directory — Claude Code prints it as "Base directory for this skill" when the skill loads; substitute that absolute path (it is not a shell variable). Other Agent-Skills tools provide the skill's directory the same way.
cat "<skill-dir>/<stack>/config-files.md"
cat "<skill-dir>/<stack>/source-files.md"
Step 3 — Follow each loaded guide fully before proceeding to the next.