Add create-next-shadcn command to automate Next.js app scaffolding with AIDD

[Copilot]

Description

Adds npx aidd create-next-shadcn [project-name] command that automates Phase 1 setup of a Next.js application with AIDD framework, tests, and tooling. Based on feedback, the command now performs deterministic automation instead of delegating to Claude CLI, making it LLM-agnostic and more reliable.

Changes

• New command implementation (lib/create-next-shadcn.js)

  • Automates complete Phase 1 setup without requiring any LLM
  • Creates Next.js app with TypeScript, Tailwind, App Router using create-next-app
  • Installs and configures AIDD framework (npx aidd --cursor && npm install aidd)
  • Installs test dependencies (Vitest, Riteway, Playwright)
  • Installs and configures Storybook
  • Configures package.json scripts (test, test:e2e, test:ui, typecheck)
  • Creates baseline test files and Playwright E2E setup
  • Sets module type to "module" for native ESM support

• CLI integration (bin/aidd.js)

  • Added subcommand using commander.js with project-name argument
  • Updated help text with Quick Start example

• New /scaffold command (ai/commands/scaffold.md)

  • LLM-agnostic command for Phase 2 design system work
  • Works with any AI tool (Claude Code, Cursor, GitHub Copilot)
  • Documents shadcn setup and baseline design system creation
  • References Phase 1 automation as prerequisite

• Tests

  • Unit tests with mocked spawn and fs-extra (3 tests)
  • E2E tests for CLI help integration (3 tests)
  • All 206 tests passing

Usage

# Phase 1: Automated setup (no LLM required)
npx aidd create-next-shadcn my-app

# Phase 2: Use /scaffold command with your preferred LLM
# (documented in ai/commands/scaffold.md)

Benefits

• ✅ Instant working Next.js app (no LLM wait time)
• ✅ No dependency on specific AI tool
• ✅ More reliable setup (deterministic automation)
• ✅ Users choose their preferred LLM for creative Phase 2 work
• ✅ Clear separation between automation and LLM-driven tasks

Original prompt

---

This section details on the original issue you should resolve

<issue_title>npx aidd create-next-shadcn </issue_title>
<issue_description>New /task (see ai/commands/task.md)

Add a command:

npx aidd create-next-shadcn # quickly scaffold a new app

Requires Claude Code to be installed.

Does something like:

{
  echo "Follow these instructions exactly. Stop when complete."
  echo
  curl -fsSL "$PROMPT_URL"
} | claude # assuming claude supports prompt piped from stdin?

Prompt url: https://github.com/paralleldrive/aidd/blob/main/docs/new-project-setup-nextjs-shadcn.md

Please carefully obey the JS style guide in ai/rules/javascript along with the tdd guide in ai/rules/tdd.mdc

Please carefully /review your work when you are done using ai/commands/review using the /execute command</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes npx aidd create-next-shadcn <projecName> #70

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[ericelliott]

@copilot Let's come up with a plan to start the CLI command with all the stuff we can do without invoking an LLM - automate installation of everything using the CLI tools like create-next-app -y and all the installers for things like riteway, playwright, etc as in the prompt I initially thought we would feed in. Instead of feeding in that prompt, extract everything we can automate without LLMs and put THAT in the CLI script. And then we'll let the user bring their own preferred code agent system such as claude code or Cursor or GitHub Copilot and create a new /command in ai/commands - maybe call it /scafold - thoughts?

[Copilot]

@copilot Let's come up with a plan to start the CLI command with all the stuff we can do without invoking an LLM - automate installation of everything using the CLI tools like create-next-app -y and...

Great idea! I'll refactor to:

1. Move all deterministic Phase 1 automation into the CLI command (create-next-app, installs, configs)
2. Create /scaffold command in ai/commands/ for Phase 2 (design system, LLM-driven work)
3. Make it LLM-agnostic so users can use Claude Code, Cursor, or Copilot

This separates the "can be automated" from the "needs LLM creativity" work. I'll start by extracting the automatable steps from the setup guide.