Skill

role-fullstack:fullstack-scaffolding

Scaffold production-ready fullstack projects with Next.js (App Router), Remix, Nuxt 3, SvelteKit, Astro, Blitz, RedwoodJS, or Wasp. Covers framework CLI starters, headless CMS options (Payload, Directus, Strapi, Keystone), feature/layer/domain project structures, Turborepo monorepo layout, env var validation, Docker Compose for local services, and dev tooling (Turbopack, Vite, HMR). Use when bootstrapping a new project or auditing an existing one for missing foundations.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-fullstack

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

- Starting a new project and need the correct framework CLI command

Supporting Assets

references/environment-dev-tooling.mdreferences/framework-cli-starters.mdreferences/headless-cms-options.mdreferences/project-structure.mdreferences/scaffolding-checklist.md

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

ai-first-engineering

Provides process, architecture, review, hiring, and testing guidelines for engineering teams relying on AI code generation.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-fullstack:fullstack-scaffolding

When to use

Starting a new project and need the correct framework CLI command

Choosing between Next.js, Remix, SvelteKit, Nuxt, Astro, or a DSL framework

Adding a headless CMS to an existing or new application

Deciding on project folder structure (feature vs layer vs domain)

Setting up Turborepo monorepo with shared packages

Configuring env var validation, Docker Compose, or CI/CD stub from day one

Core principles

Convention over configuration — exhaust framework defaults before reaching for custom solutions; every override is future maintenance

Validate at startup — env vars validated with zod at boot time; a missing secret should crash immediately with a clear message, not at 3 AM

Feature-based structure by default — co-locate components, hooks, types, and API calls per feature; switch to domain-based only when bounded contexts are clear

Remove boilerplate on first commit — delete all demo content from CLI-generated projects before the first real commit lands

Feature flags from day one — add a minimal flag mechanism before the first conditional shipping need; retrofitting is always messier

Reference Files

references/framework-cli-starters.md — CLI commands and rationale for T3, Next.js, Remix, SvelteKit, Nuxt, Astro, Expo, Blitz, RedwoodJS, Wasp, Amplication; boilerplate template comparison table

references/headless-cms-options.md — Payload CMS (code-first, Next.js integrated), Directus (no-code admin, any SQL), Strapi v5 (Document Service API), KeystoneJS (GraphQL + editorial UI)

references/project-structure.md — feature-based, layer-based, and domain-based structure examples with annotated directory trees; Turborepo monorepo layout

references/environment-dev-tooling.md — .env.example template, @t3-oss/env-nextjs validation code, Docker Compose for Postgres/Redis/Meilisearch, Turbopack setup, Vite patterns, HMR caveats

references/scaffolding-checklist.md — nine-step setup sequence from CLI init to CI/CD stub, key principles, and common pitfalls checklist

When to use

Starting a new project and need the correct framework CLI command

Choosing between Next.js, Remix, SvelteKit, Nuxt, Astro, or a DSL framework

Adding a headless CMS to an existing or new application

Deciding on project folder structure (feature vs layer vs domain)

Setting up Turborepo monorepo with shared packages

Configuring env var validation, Docker Compose, or CI/CD stub from day one

Core principles

Convention over configuration — exhaust framework defaults before reaching for custom solutions; every override is future maintenance

Validate at startup — env vars validated with zod at boot time; a missing secret should crash immediately with a clear message, not at 3 AM

Feature-based structure by default — co-locate components, hooks, types, and API calls per feature; switch to domain-based only when bounded contexts are clear

Remove boilerplate on first commit — delete all demo content from CLI-generated projects before the first real commit lands

Feature flags from day one — add a minimal flag mechanism before the first conditional shipping need; retrofitting is always messier

Reference Files

references/framework-cli-starters.md — CLI commands and rationale for T3, Next.js, Remix, SvelteKit, Nuxt, Astro, Expo, Blitz, RedwoodJS, Wasp, Amplication; boilerplate template comparison table

references/headless-cms-options.md — Payload CMS (code-first, Next.js integrated), Directus (no-code admin, any SQL), Strapi v5 (Document Service API), KeystoneJS (GraphQL + editorial UI)

references/project-structure.md — feature-based, layer-based, and domain-based structure examples with annotated directory trees; Turborepo monorepo layout

references/environment-dev-tooling.md — .env.example template, @t3-oss/env-nextjs validation code, Docker Compose for Postgres/Redis/Meilisearch, Turbopack setup, Vite patterns, HMR caveats

references/scaffolding-checklist.md — nine-step setup sequence from CLI init to CI/CD stub, key principles, and common pitfalls checklist

role-fullstack:fullstack-scaffolding

Install

Tool Access

Preview

Supporting Assets

SKILL.md

Similar Skills

role-fullstack:fullstack-scaffolding

Install

Tool Access

Preview

Supporting Assets

SKILL.md

Fullstack Scaffolding

When to use

Core principles

Reference Files

Similar Skills

Fullstack Scaffolding

When to use

Core principles

Reference Files