@forgeailab/spark 0.2.0 → 0.3.0

package/packs/ui-shadcn/skills/shadcn-dashboard-patterns/SKILL.md

@@ -1,85 +0,0 @@
----
-name: shadcn-dashboard-patterns
-description: Compose shadcn-style primitives into dense, practical dashboard layouts without drifting into marketing UI.
----
-
-# Skill: shadcn-dashboard-patterns
-
-## Goal
-
-Build dashboard screens from small primitives that stay easy to scan, resize,
-and extend. Use the shadcn component style as a starting point, not as a reason
-to turn every section into a card.
-
-## Defaults
-
-- Start with the user's job, not the component catalog.
-- Put navigation, filters, and primary actions where repeat users expect them.
-- Prefer one clear page title, one toolbar, and one main content region.
-- Use cards for repeated objects, stat summaries, forms, and modal content.
-- Do not wrap the whole page in a decorative card.
-- Keep radii at `rounded-lg` or below unless the app theme says otherwise.
-- Use `cn()` for class merging and keep variants close to the component.
-
-## Layout
-
-- Use a shell with a sidebar or top nav only when there are real destinations.
-- Keep dashboard width constrained with `mx-auto w-full max-w-7xl px-4`.
-- Use `gap-4` or `gap-6`; avoid ornamental whitespace in operational views.
-- Put status, owner, date, and filters near the table or list they affect.
-- Align destructive actions away from the primary happy path.
-- Keep tables full width and let dense data breathe through row height.
-- Use sticky headers only when the table is long enough to justify them.
-
-## Cards
-
-- A card should represent one thing: a metric, a record, a form, or a chart.
-- Do not nest cards inside cards.
-- Use `CardHeader`, `CardContent`, and `CardFooter` only when each region helps.
-- Small metric cards should use compact labels, one strong value, and a trend.
-- Empty cards should show the empty state for that object, not generic help copy.
-- Repeated cards need stable height or clear wrapping behavior.
-
-## Buttons
-
-- Primary buttons create or commit work.
-- Secondary buttons reveal adjacent options.
-- Ghost buttons belong in rows, toolbars, and low-emphasis actions.
-- Icon buttons need an accessible label.
-- Use `asChild` when routing through `Link`, not nested buttons or anchors.
-- Keep button labels short and concrete: `Save`, `Invite`, `Export`.
-- Avoid full-width buttons on desktop unless the panel itself is narrow.
-
-## Forms
-
-- Group fields by workflow, not by database table.
-- Put validation text next to the field that caused it.
-- Use disabled and pending states during server actions.
-- Use destructive copy only for irreversible actions.
-- Keep advanced settings collapsed until they are needed.
-- Use consistent input widths inside the same form group.
-
-## Tables And Lists
-
-- Use a table when users compare many rows across the same fields.
-- Use a list when records have mixed metadata and short actions.
-- Keep row actions at the trailing edge.
-- Expose bulk actions only after selection exists.
-- Use badges sparingly for status, plan, role, or risk.
-- Do not use color as the only status signal.
-
-## Empty, Loading, Error
-
-- Empty states should offer the next valid action.
-- Loading states should preserve the final layout shape.
-- Error states should say what failed and offer retry or recovery.
-- Avoid giant empty illustrations inside work dashboards.
-- Do not teach the whole product in an empty state.
-
-## Motion And Polish
-
-- Prefer subtle color, border, and shadow changes over large motion.
-- Keep hover states predictable across cards, rows, and buttons.
-- Respect reduced motion when adding transitions.
-- Check mobile wrapping for toolbar actions and long entity names.
-- Make the first useful workflow visible without a landing page.

package/packs/ui-shadcn/tasks.yaml

@@ -1,6 +0,0 @@
-epic: UI
-tasks:
-  - id: UI-001
-    title: Build first dashboard page
-    acceptance:
-      - First dashboard page uses the installed UI primitives for a real app workflow

package/presets/docs-site.toml

@@ -1,4 +0,0 @@
-name = "docs-site"
-description = "Documentation site (placeholder -- activates once astro-starlight template ships)."
-compatible_scaffolds = ["astro-starlight"]
-packs = []

package/presets/internal-tool.toml

@@ -1,4 +0,0 @@
-name = "internal-tool"
-description = "Internal admin tool -- Supabase auth, shadcn UI, local docker for dev."
-compatible_scaffolds = ["nextjs"]
-packs = ["db-supabase", "auth-supabase", "ui-shadcn", "docker-compose-dev"]

package/presets/lean-saas.toml

@@ -1,4 +0,0 @@
-name = "lean-saas"
-description = "Lean SaaS -- no Supabase. SQLite + Better Auth + shadcn + Vercel."
-compatible_scaffolds = ["nextjs"]
-packs = ["db-sqlite", "auth-better-auth", "ui-shadcn", "deploy-vercel"]

package/presets/local-ai-mvp.toml

@@ -1,4 +0,0 @@
-name = "local-ai-mvp"
-description = "Local-first AI MVP -- SQLite + Claude + shadcn on Next.js, with Playwright tests."
-compatible_scaffolds = ["nextjs"]
-packs = ["db-sqlite", "ai-anthropic", "ui-shadcn", "testing-playwright"]

package/presets/saas-classic.toml

@@ -1,4 +0,0 @@
-name = "saas-classic"
-description = "Classic SaaS stack -- Supabase + Stripe + Resend on Next.js."
-compatible_scaffolds = ["nextjs"]
-packs = ["db-supabase", "auth-supabase", "payments-stripe", "email-resend", "ui-shadcn", "deploy-vercel"]

package/templates/README.md

@@ -1,43 +0,0 @@
-# Template Authoring
-
-Templates live under `templates/<name>/` and register a base scaffold for `create-spark`. Each template directory must contain a `template.toml` manifest and may contain scaffold files when the template is stable.
-
-## `template.toml`
-
-`template.toml` is parsed with `TemplateManifestSchema` from `packages/spark-schema/src/template.ts`.
-
-Required fields:
-
-- `name`: lowercase template id matching `^[a-z][a-z0-9-]*$`.
-- `status`: `stable` or `planned`.
-- `provides`: array of template capability tags.
-- `description`: one-line human-readable summary.
-
-Example:
-
-```toml
-name = "nextjs"
-status = "stable"
-provides = ["server", "static", "spa"]
-description = "Next.js App Router scaffold for TypeScript web apps."
-```
-
-## Template Capabilities
-
-Template capabilities describe what the base scaffold runtime provides. They are separate from pack capabilities such as `db`, `auth`, or `payments`.
-
-Current accepted template capabilities:
-
-- `server`: can run server-side application code.
-- `spa`: supports client-side single-page app behavior.
-- `native`: supports native app targets.
-- `edge`: supports edge runtime deployment.
-- `library`: is intended as a reusable package or library scaffold.
-- `monorepo`: is a multi-package workspace scaffold.
-- `static`: can emit static assets or static pages.
-
-Use only these exact values until the schema changes. Planned templates should still include a valid `template.toml` so packs and presets can declare compatibility before the full scaffold ships.
-
-## Promoting Planned Templates
-
-To promote a template from `planned` to `stable`, add the runnable scaffold files under `templates/<name>/`, update `status = "stable"`, and run the manifest parser against every template. Stable templates should be copyable into a new project and runnable without requiring auth, database, billing, email, UI libraries, or AI SDK setup by default.

package/templates/astro/README.md

@@ -1,3 +0,0 @@
-# Astro Template
-
-This template is registered for pack compatibility planning, but it is not implemented yet. The planned scope is an Astro content-site scaffold with server rendering, static output support, MDX-oriented content workflows once the template capability schema supports that tag, and the same AI workflow artifacts as the stable Next.js template.

package/templates/astro/template.toml

@@ -1,4 +0,0 @@
-name = "astro"
-status = "planned"
-provides = ["server", "static", "mdx-content"]
-description = "Planned Astro scaffold for content sites with partial hydration."

package/templates/astro-starlight/README.md

@@ -1,3 +0,0 @@
-# Astro Starlight Template
-
-This template is registered for pack compatibility planning, but it is not implemented yet. The planned scope is a static documentation scaffold based on Astro Starlight, with content-focused defaults and the same AI workflow artifacts as the stable Next.js template.

package/templates/astro-starlight/template.toml

@@ -1,4 +0,0 @@
-name = "astro-starlight"
-status = "planned"
-provides = ["static", "mdx-content"]
-description = "Planned Astro Starlight scaffold for documentation sites."

package/templates/nextjs/.ai/architecture.md

@@ -1,13 +0,0 @@
-# Architecture
-
-## Stack
-
-## Repo structure
-
-## Data model
-
-## API surface
-
-## Pack plan
-
-## Non-goals

package/templates/nextjs/.ai/board.md

@@ -1,7 +0,0 @@
-# Board
-
-Status flow: `Clarifying` -> `Approved for planning` -> `Approved for execution` -> `In progress` -> `Needs review` -> `Validated`
-
-Side states: `Blocked`, `Cut from MVP`
-
-## Backlog

package/templates/nextjs/.ai/product-spec.md

@@ -1,11 +0,0 @@
-# Product Spec
-
-## Vision
-
-## Users
-
-## Core flows
-
-## Constraints
-
-## Out of scope

package/templates/nextjs/AGENTS.md

@@ -1,95 +0,0 @@
-# AGENTS.md
-
-Operating rules for any agent (Codex, Claude Code, or otherwise) working in this repo. Mirror of the workflow encoded in `.claude/skills/`, so the system stays portable.
-
-<!-- SPEC:START -->
-## Spec workflow
-
-For proposals/specs/plans, new capabilities, breaking changes, architecture shifts, or behavior-changing perf/security work, keep the source of truth in this project's `.ai/` artifacts first. If the project later adopts formal spec deltas, place them under `docs/spec/changes/<id>-YYYY-MM-DD/`; truth specs after archive live under `docs/spec/specs/`.
-<!-- SPEC:END -->
-
-## Operating model
-
-This project runs a **planner / implementer / evaluator** loop. The same agent should not plan, build, and grade its own work. Use a strong reasoning model (Opus 4.7 / GPT-5.5) for planning and review; use a faster executor (Sonnet 4.6 / GPT-5 family) for routine implementation.
-
-## Source of truth
-
-The truth is in repo artifacts, not in chat:
-
-- `.ai/product-spec.md` — what the MVP is. Source of acceptance criteria and non-goals.
-- `.ai/architecture.md` — the stack and the cutline (what we are NOT building yet).
-- `.ai/ux-theme.md` — visual direction. Empty / loading / error patterns live here.
-- `.ai/board.md` — every task, with status, dependencies, owners, validation state, linked PR.
-- `.ai/decision-log.md` — locked-in decisions and the reasoning.
-- `.ai/execution-log.md` — append-only history of state changes.
-
-If an answer is not in these files, ask the user — do not invent it.
-
-## Workflow phases
-
-1. **Grill the idea** until it is buildable. Max 5 questions per round. Only questions that change scope or architecture.
-2. **Write the spec.** One MVP slice. Non-goals are mandatory.
-3. **Cut the architecture.** Boring stack > clever stack. Every choice has a "not building yet" sibling.
-4. **Theme the UX.** One vibe, one reference product, concrete tokens.
-5. **Build the board.** Tasks sized for one focused session. Declare `Depends on:` and `Parallel-safe:`.
-6. **Review the board.** Approval gate between planning and execution. No task starts until it is `Approved for execution`.
-7. **Brief each task** before execution. Self-contained, with files-to-inspect, acceptance criteria verbatim, and a verification command.
-8. **Execute one task at a time.** Stay inside the declared file list. No bonus refactors.
-9. **Review independently.** A separate pass checks the diff against acceptance criteria, security, and scope.
-10. **QA-verify** by actually running the app and walking the core user journey.
-11. **Sync the board** from git reality. Trust git, not claims.
-
-## Board statuses
-
-`Clarifying` → `Approved for planning` → `Approved for execution` → `In progress` → `Needs review` → `Validated`
-
-Side states: `Blocked`, `Cut from MVP`.
-
-`Validated` requires both a `/code-review` pass and a `/qa-verify` pass for user-facing changes. Execution never grades itself.
-
-## Hard rules
-
-- Do not edit files outside the current task's declared scope. New discoveries become new tasks in `Clarifying`, not silent edits.
-- Do not pick a stack outside `.ai/architecture.md`. Propose a decision-log update first.
-- Do not mark tasks `Validated` without independent review.
-- Do not move a task to `Approved for execution` from execution skills. Only board-review can.
-- Treat the `Non-goals` section of the spec and the `What we are NOT building yet` section of architecture as a `do-not-build` list. Violations are scope creep, not features.
-- Verification commands must actually run. Type-check passing is not the same as feature working.
-- When `git status` and a self-report disagree, trust git.
-
-## Skill / command equivalents
-
-Claude Code skills live in `.claude/skills/`. The same operations on Codex should be triggered through the matching workflow names:
-
-| Stage | Skill |
-| --- | --- |
-| Grill | `mvp-grill`, `idea-sharpen` |
-| Spec | `mvp-spec` |
-| Architecture | `architecture-cutline` |
-| Theme | `ux-theme` |
-| Board | `mvp-board`, `board-review` |
-| Schedule | `parallel-execution`, `next-task` |
-| Execute | `implementation-brief`, `execute-task` |
-| Evaluate | `code-review`, `qa-verify` |
-| Sync | `sync-board` |
-| Watch | `risk-check` |
-
-## Model assignment defaults
-
-- Planning / reviewing / scoping: **Opus 4.7** or **GPT-5.5**.
-- Routine execution: **Sonnet 4.6** or a GPT-5 family executor.
-- High-risk tasks (auth, payments, migrations, security): planning-quality model for both build and review.
-
-## Conventions
-
-- Stable task IDs (e.g. `AUTH-001`). Never renumber.
-- Append to `.ai/decision-log.md` whenever a non-obvious choice is made, with: decision, context, alternatives considered, why, risk, revisit condition.
-- Append to `.ai/execution-log.md` one line per state change in `.ai/board.md`.
-- Do not delete board tasks. Move them to `Cut from MVP` with a reason.
-
-## Packs
-
-Feature packs are installed with the `spark` CLI.
-Use `pack-resolve` to choose the scaffold and pack set, `pack-add` to dry-run
-and install declarative pack changes, then `sync-board` to reconcile `.ai/board.md`
-with the installed capabilities and current repository state.

package/templates/nextjs/CLAUDE.md

@@ -1,3 +0,0 @@
-# CLAUDE.md
-
-Follow `AGENTS.md` for the operating contract. Keep `.ai/board.md` as the task source of truth, and use the `spark` CLI when adding packs or checking installed capabilities.

package/templates/nextjs/README.md

@@ -1,20 +0,0 @@
-# Next.js Spark Template
-
-This is the minimal Next.js 15 + TypeScript scaffold used by `create-spark`.
-
-## Development
-
-Install dependencies, then start the dev server:
-
-```sh
-bun install
-bun dev
-```
-
-## Next Steps
-
-Read `AGENTS.md`, fill in the `.ai/` planning files, and keep `.ai/board.md` current before implementing. Add capabilities only when the board calls for them:
-
-```sh
-spark add <pack>
-```

package/templates/nextjs/app/(app)/home/page.tsx

@@ -1,43 +0,0 @@
-import Link from 'next/link';
-import { getSessionUser } from '@/lib/auth-placeholder';
-import { PostsPanel } from './posts-panel';
-
-export default async function AppHome() {
-  const user = await getSessionUser();
-
-  return (
-    <main className="mx-auto max-w-3xl px-6 py-12">
-      <header className="flex items-center justify-between">
-        <div>
-          <p className="text-xs font-semibold uppercase tracking-[0.2em] text-slate-500">
-            Home
-          </p>
-          <h1 className="mt-1 text-2xl font-semibold tracking-tight text-slate-900">
-            {user ? `Hello ${user.name}` : 'Hello, friend'}
-          </h1>
-        </div>
-        {!user && (
-          <Link
-            href="/login"
-            className="rounded-md border border-slate-300 bg-white px-3 py-1.5 text-xs font-medium text-slate-700 shadow-sm hover:bg-slate-50"
-          >
-            Sign in
-          </Link>
-        )}
-      </header>
-
-      {!user && (
-        <p className="mt-4 rounded-md border border-amber-200 bg-amber-50 px-4 py-3 text-sm text-amber-900">
-          No session detected. Install the{' '}
-          <code className="rounded bg-amber-100 px-1">auth-better-auth</code>{' '}
-          pack to wire real authentication.
-        </p>
-      )}
-
-      <section className="mt-8">
-        <h2 className="text-sm font-semibold text-slate-700">Your posts</h2>
-        <PostsPanel />
-      </section>
-    </main>
-  );
-}

package/templates/nextjs/app/(app)/home/posts-panel.tsx

@@ -1,83 +0,0 @@
-'use client';
-
-import { useState, type FormEvent } from 'react';
-import { usePosts } from '@/lib/posts-placeholder';
-
-export function PostsPanel() {
-  const { posts, createPost } = usePosts();
-  const [title, setTitle] = useState('');
-  const [body, setBody] = useState('');
-  const [pending, setPending] = useState(false);
-
-  async function onSubmit(event: FormEvent<HTMLFormElement>) {
-    event.preventDefault();
-    if (!title.trim()) return;
-    setPending(true);
-    try {
-      await createPost({ title: title.trim(), body: body.trim() });
-      setTitle('');
-      setBody('');
-    } finally {
-      setPending(false);
-    }
-  }
-
-  return (
-    <div className="mt-3 space-y-4">
-      <form
-        onSubmit={onSubmit}
-        className="rounded-xl border border-slate-200 bg-white p-4 shadow-sm"
-      >
-        <input
-          value={title}
-          onChange={(e) => setTitle(e.target.value)}
-          placeholder="Post title"
-          className="block w-full rounded-md border border-slate-300 px-3 py-2 text-sm placeholder:text-slate-400 focus:border-slate-900 focus:outline-none focus:ring-1 focus:ring-slate-900"
-        />
-        <textarea
-          value={body}
-          onChange={(e) => setBody(e.target.value)}
-          placeholder="Write something…"
-          rows={2}
-          className="mt-2 block w-full rounded-md border border-slate-300 px-3 py-2 text-sm placeholder:text-slate-400 focus:border-slate-900 focus:outline-none focus:ring-1 focus:ring-slate-900"
-        />
-        <div className="mt-3 flex items-center justify-end">
-          <button
-            type="submit"
-            disabled={pending || !title.trim()}
-            className="inline-flex items-center justify-center rounded-md bg-slate-900 px-4 py-1.5 text-sm font-medium text-white shadow-sm transition hover:bg-slate-800 disabled:cursor-not-allowed disabled:opacity-50"
-          >
-            {pending ? 'Posting…' : 'Post'}
-          </button>
-        </div>
-      </form>
-
-      {posts.length === 0 ? (
-        <div className="rounded-xl border border-dashed border-slate-300 bg-white/60 px-4 py-8 text-center text-sm text-slate-500">
-          No posts yet. Install the{' '}
-          <code className="rounded bg-slate-100 px-1">sync-zero</code> pack to
-          persist and sync posts in real time.
-        </div>
-      ) : (
-        <ul className="space-y-2">
-          {posts.map((post) => (
-            <li
-              key={post.id}
-              className="rounded-xl border border-slate-200 bg-white p-4 shadow-sm"
-            >
-              <h3 className="text-sm font-semibold text-slate-900">
-                {post.title}
-              </h3>
-              {post.body && (
-                <p className="mt-1 text-sm text-slate-600">{post.body}</p>
-              )}
-              <p className="mt-2 text-xs text-slate-400">
-                {post.createdAt.toLocaleString()}
-              </p>
-            </li>
-          ))}
-        </ul>
-      )}
-    </div>
-  );
-}

package/templates/nextjs/app/(app)/layout.tsx

@@ -1,12 +0,0 @@
-import type { ReactNode } from 'react';
-
-// Placeholder authed-route layout.
-//
-// The `auth-better-auth` pack will replace this with a server-side guard that
-// calls `getSessionUser()` and `redirect('/login')` when there is no session.
-// Until then this just renders children so the scaffold compiles and runs.
-export default function AppLayout({ children }: { children: ReactNode }) {
-  return (
-    <div className="min-h-screen bg-slate-50 text-slate-900">{children}</div>
-  );
-}

package/templates/nextjs/app/(auth)/login/page.tsx

@@ -1,97 +0,0 @@
-import Link from 'next/link';
-
-// NOTE: no auth wired yet. The `action` and the GitHub button are placeholders.
-// The `auth-better-auth` pack will:
-//   - replace `action="/api/auth/sign-in"` with the real route handler path
-//   - replace the GitHub button's form with a real OAuth start endpoint
-//   - add `app/api/auth/[...all]/route.ts` and `lib/auth.ts`
-export default function LoginPage() {
-  return (
-    <main className="min-h-screen flex items-center justify-center bg-slate-50 px-6 py-16">
-      <div className="w-full max-w-sm">
-        <div className="mb-8 text-center">
-          <h1 className="text-2xl font-semibold tracking-tight text-slate-900">
-            Welcome back
-          </h1>
-          <p className="mt-1 text-sm text-slate-600">
-            Sign in to continue to your workspace.
-          </p>
-        </div>
-        <div className="rounded-xl border border-slate-200 bg-white p-6 shadow-sm">
-          <form action="/api/auth/sign-in" method="post" className="space-y-4">
-            <div>
-              <label
-                htmlFor="email"
-                className="block text-xs font-medium text-slate-700"
-              >
-                Email
-              </label>
-              <input
-                id="email"
-                name="email"
-                type="email"
-                autoComplete="email"
-                required
-                className="mt-1 block w-full rounded-md border border-slate-300 bg-white px-3 py-2 text-sm text-slate-900 shadow-sm placeholder:text-slate-400 focus:border-slate-900 focus:outline-none focus:ring-1 focus:ring-slate-900"
-                placeholder="you@example.com"
-              />
-            </div>
-            <div>
-              <label
-                htmlFor="password"
-                className="block text-xs font-medium text-slate-700"
-              >
-                Password
-              </label>
-              <input
-                id="password"
-                name="password"
-                type="password"
-                autoComplete="current-password"
-                required
-                className="mt-1 block w-full rounded-md border border-slate-300 bg-white px-3 py-2 text-sm text-slate-900 shadow-sm placeholder:text-slate-400 focus:border-slate-900 focus:outline-none focus:ring-1 focus:ring-slate-900"
-                placeholder="••••••••"
-              />
-            </div>
-            <button
-              type="submit"
-              className="w-full rounded-md bg-slate-900 px-4 py-2 text-sm font-medium text-white shadow-sm transition hover:bg-slate-800 focus:outline-none focus:ring-2 focus:ring-slate-900 focus:ring-offset-2"
-            >
-              Sign in
-            </button>
-          </form>
-          <div className="relative my-5">
-            <div className="absolute inset-0 flex items-center">
-              <div className="w-full border-t border-slate-200" />
-            </div>
-            <div className="relative flex justify-center text-xs uppercase">
-              <span className="bg-white px-2 text-slate-500">or</span>
-            </div>
-          </div>
-          <form action="/api/auth/sign-in/github" method="post">
-            <button
-              type="submit"
-              className="inline-flex w-full items-center justify-center gap-2 rounded-md border border-slate-300 bg-white px-4 py-2 text-sm font-medium text-slate-800 shadow-sm transition hover:bg-slate-50"
-            >
-              <svg
-                aria-hidden="true"
-                viewBox="0 0 24 24"
-                className="h-4 w-4"
-                fill="currentColor"
-              >
-                <path d="M12 .5C5.65.5.5 5.65.5 12c0 5.08 3.29 9.39 7.86 10.91.58.11.79-.25.79-.56v-2c-3.2.7-3.87-1.37-3.87-1.37-.52-1.33-1.28-1.69-1.28-1.69-1.05-.72.08-.7.08-.7 1.16.08 1.77 1.19 1.77 1.19 1.03 1.77 2.7 1.26 3.36.96.1-.75.4-1.26.73-1.55-2.55-.29-5.24-1.28-5.24-5.7 0-1.26.45-2.29 1.19-3.1-.12-.29-.52-1.46.11-3.04 0 0 .97-.31 3.18 1.18a11 11 0 015.79 0c2.2-1.49 3.17-1.18 3.17-1.18.63 1.58.23 2.75.12 3.04.74.81 1.19 1.84 1.19 3.1 0 4.43-2.69 5.41-5.25 5.69.41.36.78 1.06.78 2.14v3.17c0 .31.21.68.8.56 4.57-1.52 7.86-5.83 7.86-10.91C23.5 5.65 18.35.5 12 .5z" />
-              </svg>
-              Continue with GitHub
-            </button>
-          </form>
-        </div>
-        <p className="mt-6 text-center text-xs text-slate-500">
-          Don&apos;t have an account?{' '}
-          <Link href="/" className="font-medium text-slate-900 hover:underline">
-            Back home
-          </Link>
-        </p>
-      </div>
-    </main>
-  );
-}

package/templates/nextjs/app/globals.css

@@ -1,23 +0,0 @@
-@import "tailwindcss";
-
-:root {
-  color-scheme: light;
-}
-
-html,
-body {
-  height: 100%;
-}
-
-body {
-  font-family:
-    ui-sans-serif,
-    system-ui,
-    -apple-system,
-    'Segoe UI',
-    Roboto,
-    sans-serif;
-  background-color: #f8fafc;
-  color: #0f172a;
-  line-height: 1.5;
-}

package/templates/nextjs/app/layout.tsx

@@ -1,20 +0,0 @@
-import type { Metadata } from 'next';
-import type { ReactNode } from 'react';
-import './globals.css';
-
-export const metadata: Metadata = {
-  title: 'Spark App',
-  description: 'Minimal Next.js scaffold for spark projects.',
-};
-
-export default function RootLayout({
-  children,
-}: Readonly<{
-  children: ReactNode;
-}>) {
-  return (
-    <html lang="en">
-      <body>{children}</body>
-    </html>
-  );
-}