sec-scaffold-monorepo-multimodulos-add-nextjs

Scaffold a frontend monorepo with Next.js and Expo apps under pnpm workspaces.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/diegolirio/ai-showcase-skills --skill sec-scaffold-monorepo-multimodulos-add-nextjs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sec-scaffold-monorepo-multimodulos-add-nextjs
Source: https://github.com/diegolirio/ai-showcase-skills/tree/main/skills/sec-scaffold-monorepo-multimodulos-add-nextjs
Command: npx skills add https://github.com/diegolirio/ai-showcase-skills --skill sec-scaffold-monorepo-multimodulos-add-nextjs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds a frontend monorepo structure for Next.js and Expo apps that is independent from the backend stack. It enables teams to structure a frontend that is decoupled from the backend language and colocate domain-specific apps under a single domain folder, simplifying maintenance and reuse.

Core Features & Use Cases

  • Scaffolds or extends a frontend monorepo with Next.js web apps, Expo mobile apps, shared domain UI packages, and a root-level shared-front package.
  • Creates a standardized structure: {ROOT}/ {project-name}/, {project-name}-web, {project-name}-mobile, {project-name}-ui, and shared-front at the repository root.
  • Ensures frontend monorepos are independent from backend stacks and can host multiple domain projects like properties or cars within the same repo.
  • Uses a discovery-driven approach: scans the repository for existing frontend indicators (package.json, next.config.*, app/ or pages/, app.json, expo) before scaffolding and may prompt when multiple projects exist.
  • Keeps frontend scaffolding backend-agnostic and workspace-friendly, leveraging pnpm workspaces and minimal project root configs.

Quick Start

Provide the project slug to the skill to generate the frontend monorepo scaffolding for that domain.

Frequently Asked Questions about sec-scaffold-monorepo-multimodulos-add-nextjs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Next.js frontend monorepo that stays independent from my backend stack?

Scaffolding a Next.js and Expo monorepo creates a domain-based folder structure with -web, -mobile, and -ui subdirectories, plus a shared-front package at the root. It uses a discovery-driven approach to scan for existing frontend projects before generating the pnpm workspace configuration.

Can I scaffold a monorepo with both Next.js and Expo apps using a shared UI?

Yes, scaffolding supports generating both Next.js web and Expo mobile apps within a single domain folder. It creates a dedicated {project-name}-ui package and a root-level shared-front directory to enforce a standardized workspace layout for cross-project UI reuse.

What is the best way to organize multiple domain projects within a single frontend repository?

Organizing multiple domain projects within a single frontend repository involves placing each domain under {ROOT}/{project-name}/ with dedicated -web, -mobile, and -ui folders. A root-level shared-front package handles cross-domain components while pnpm workspaces manage dependencies.

Does this frontend scaffolding tool detect existing Next.js or Expo projects before generating folders?

Yes, the frontend scaffolding tool uses a discovery-driven approach that scans the repository for existing frontend indicators like package.json, next.config, or app.json before scaffolding. It may prompt you when multiple existing projects are detected to prevent overwriting.

Do I need pnpm workspaces to set up a minimal backend-agnostic frontend monorepo?

Yes, you need pnpm workspaces to set up this minimal backend-agnostic frontend monorepo. The scaffolding relies on pnpm workspaces and minimal project root configs to enforce the workspace layout and manage dependencies across the shared-front and domain-specific packages.