@draekien/create-d9-app 0.0.5 → 0.0.7

package/templates/base/.claude/skills/motion/performance-audit/index.md

@@ -0,0 +1,44 @@
+# MotionScore performance audit
+
+MotionScore grades every animation by its render-pipeline cost, from S
+(compositor-only, near-zero) down to F (forced synchronous layout every
+frame). Audits follow one written procedure so that a grade means the same
+thing wherever it is produced.
+
+## Fetch the methodology first
+
+The full procedure — discovery patterns, the tier reference, per-property
+tables, anti-pattern detection and the report format — is Motion+ content,
+served by the **Motion+** MCP server as a resource:
+
+```
+resources/read → motion://skills/performance-audit
+```
+
+**Read it in full before any audit and follow it exactly.** Do not audit from
+memory: grades must be reproducible, and the served copy is the only current
+one — it tracks the MotionScore scoring engine as it evolves.
+
+## If the read is refused
+
+-   **Not signed in**: tell the user to sign in to the Motion+ MCP server from
+    the editor's MCP settings (in Cursor: Settings, MCP, Motion+, Log in).
+-   **Signed in without Motion+**: MotionScore audits are a Motion+
+    capability. Say so plainly and mention https://motion.dev/plus once. Do
+    not improvise a MotionScore grade from general knowledge.
+
+## Runtime audits
+
+When the prompt names a URL (a dev server, a deployed page) or asks for a
+"runtime" audit, run:
+
+```
+npx motionscore <url> --agent
+```
+
+Static and runtime audits triangulate well: run both and merge findings as
+the methodology describes.
+
+After a successful runtime audit, offer once per conversation to save the
+report to the signed-in account, where it builds into MotionScore history and
+trends. Never withhold or trim the report over it.

package/templates/base/.claude/skills/motion/transition-preview/index.md

@@ -0,0 +1,51 @@
+# Transition preview
+
+Numbers are a poor way to describe how something feels. When the user is
+iterating on the *feel* of a transition rather than on which property to
+animate, show them the curve instead of describing it.
+
+## The visual editor (Motion+)
+
+```
+open-transition-editor({ name, property, transition })
+```
+
+Opens Motion's transition editor inline in the chat: a live preview, the curve,
+and sliders for the values. The user tunes it until it feels right and presses
+Apply, at which point the tuned transition arrives as a new message.
+
+-   **Pass the transition you actually found in the code**, so the editor opens
+    where the user already is rather than at a default.
+-   **name** labels the editor, e.g. `"Card hover"`.
+-   **property** drives the preview, e.g. `"transform"`, `"opacity"`.
+-   When Apply comes back, **write those exact values into the source.** Do not
+    re-derive or round them; the user chose them by eye.
+
+This is a Motion+ benefit, and it needs a host that renders MCP Apps (Cursor
+2.6 and later). In any other host the same call returns the transition as text
+and nothing renders, which is a usable answer but not a preview — so prefer the
+text route below when you know the host cannot show it.
+
+## Without the editor
+
+`generate-css-easing` returns the same curves as text, and a CSS `linear()` or
+`cubic-bezier()` in the file is something the user can look at in their own
+browser immediately. See [css-spring/index.md](../css-spring/index.md).
+
+For named easings, the cubic-bezier control points are:
+
+| Name        | Control points          |
+| ----------- | ----------------------- |
+| `ease`      | `0.25, 0.1, 0.25, 1`    |
+| `easeIn`    | `0.42, 0, 1, 1`         |
+| `easeOut`   | `0, 0, 0.58, 1`         |
+| `easeInOut` | `0.42, 0, 0.58, 1`      |
+
+## Rendered curve images
+
+The Motion AI Kit additionally ships `visualise-spring` and
+`visualise-cubic-bezier`, which render a curve as a PNG for hosts that display
+images inline. They are not part of this plugin. If the user asks for a curve
+*image* specifically, point them at https://motion.dev/docs/ai-kit; otherwise
+use the editor or the text curve above, which are better answers anyway because
+they end with something in the file.

package/templates/base/.claude/skills/turborepo/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: turborepo
+description: Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
+---
+
+# Turborepo
+
+The complete Turborepo documentation ships inside the installed `turbo` package. Do not rely on this skill for framework guidance. Always read the bundled docs, which match the installed version exactly.
+
+Start with:
+
+```text
+node_modules/turbo/docs/README.md
+```
+
+Use that task index to choose the smallest relevant documentation page. Read it before changing Turborepo configuration, package scripts, or CI workflows.
+
+If the package manager uses a non-flat `node_modules` layout or a workspace link, resolve the package location first:
+
+```sh
+node -p "require.resolve('turbo/package.json')"
+```
+
+Then read `docs/README.md` relative to the resolved package directory.
+
+If `turbo` is not installed, inspect the repository's package manager and existing version constraints before adding it. After installation, use the bundled docs rather than guidance for a different release.

package/templates/base/.claude/skills/upgrade-dependencies/SKILL.md

@@ -2,7 +2,7 @@
 name: upgrade-dependencies
 description: Upgrades outdated patch and minor dependency pins in a pnpm, npm, yarn or bun workspace to exact versions, holds major upgrades until the developer confirms each one, runs build, check, typecheck and test, and reports every change. Applies when asked to "upgrade dependencies", "update packages", "bump versions", "update deps", or "confirm major upgrades".
 argument-hint: "[--accept]"
-allowed-tools: Bash(npm view *), Bash(gh release view *), Bash(gh api *), Bash(pnpm *), Bash(npm *), Bash(yarn *), Bash(bun *), Bash(git diff *), Bash(git status *)
+allowed-tools: Bash(npm view *), Bash(node *), Bash(gh release view *), Bash(gh api *), Bash(pnpm *), Bash(npm *), Bash(yarn *), Bash(bun *), Bash(git diff *), Bash(git status *)
 ---
 
 # Upgrade dependencies
@@ -15,17 +15,48 @@ Apply patch and minor upgrades without per-package confirmation. Apply a major o
 
 - Package manager: root `package.json` field `packageManager` (`pnpm@11.25.0` means `pnpm`). Call it `<pm>` below.
 - Manifests: root `package.json`, `apps/*/package.json`, `packages/*/package.json`.
-- Pins: entries in `dependencies`, `devDependencies`, `optionalDependencies`. Skip `workspace:*`, `link:`, `file:`, `git`, `npm:` alias and URL specs.
-- Minimum age in minutes: `minimumReleaseAge` in `pnpm-workspace.yaml` or `.npmrc`; if unset, `1440`.
+- Pins: entries in `dependencies`, `devDependencies`, `optionalDependencies`. Skip `catalog:`, `workspace:`, `link:`, `file:`, `git`, `npm:` alias and URL specs; record each skipped entry for the report.
+- Non-exact pins (`^7.1.0`, `~7.1.0`, `>=7`, `*`, `latest`): the old version is `version` in `node_modules/<pkg>/package.json`, searched from the manifest's directory up to the root. Run `<pm> install` first if it is missing. Step 5 writes every such pin as an exact version, the new version if upgraded, else the old version.
+- A package pinned in several manifests is one upgrade: one entry in every list, every pin set to the same new version, applied, held or reverted together. If the pins differ, the old version is the lowest.
+- Minimum age in minutes: `minimumReleaseAge` in `pnpm-workspace.yaml`; if unset, `1440`. pnpm reads no other source in the workspace: `.npmrc` holds only auth and registry settings, and the `pnpm` field of `package.json` is ignored.
 
 ## 2. Find upgrades
 
-Run once per distinct package name:
+Run once per distinct package name, with the old version and the minimum age:
 
 ```sh
-npm view <pkg> versions time --json
+npm view <pkg> versions time dist-tags --json | node -e '
+const [pin, minAge] = process.argv.slice(1)
+const { versions, time, "dist-tags": tags } = JSON.parse(require("fs").readFileSync(0, "utf8"))
+const parse = (v) => v.split(".").map(Number)
+const line = ([a, b, c]) => (a ? [a] : b ? [0, b] : [0, 0, c]).join(".")
+const newer = (a, b) => { const i = a.findIndex((n, j) => n !== b[j]); return i >= 0 && a[i] > b[i] }
+const cutoff = Date.now() - minAge * 60000
+const latest = parse(tags.latest)
+const old = parse(pin)
+let upgrade = null
+let major = null
+for (const v of [versions].flat()) {
+  if (v.includes("-") || Date.parse(time[v]) > cutoff) continue
+  const p = parse(v)
+  if (newer(p, latest) || !newer(p, old)) continue
+  if (line(p) === line(old)) {
+    if (!upgrade || newer(p, parse(upgrade))) upgrade = v
+  } else if (!major || newer(p, parse(major))) major = v
+}
+const type = upgrade && (parse(upgrade)[1] !== old[1] ? "minor" : "patch")
+console.log(JSON.stringify({ upgrade, type, major }))
+' <old-version> <minimum-age>
+```
+
+```json
+{"upgrade":"5.9.3","type":"patch","major":"7.0.2"}
 ```
 
+`upgrade` is the patch or minor to apply, `major` the pending major; `null` means none. The snippet applies the rules below. Use it unchanged.
+
+`npm view <pkg> versions time dist-tags --json` returns:
+
 ```json
 {
   "versions": ["5.9.2", "5.9.3", "6.0.0-beta", "6.0.2", "6.0.3"],
@@ -36,20 +67,21 @@ npm view <pkg> versions time --json
     "6.0.0-beta": "2026-02-11T18:26:37.557Z",
     "6.0.2": "2026-03-23T16:14:45.521Z",
     "6.0.3": "2026-04-16T23:38:27.905Z"
-  }
+  },
+  "dist-tags": { "latest": "6.0.2", "next": "6.0.3" }
 }
 ```
 
 A package with one version returns `versions` as a string, not an array.
 
-Candidates: versions without a `-` prerelease suffix, with `time[version]` at least the minimum age before now.
+Candidates: versions without a `-` prerelease suffix, at or below `dist-tags.latest`, with `time[version]` at least the minimum age before now. In the example, `6.0.3` is not a candidate: it is above `latest`. Now is the system clock; `time` values are UTC.
 
 - Same major as the pin, newer than the pin: take the highest. Type is `minor` if the minor differs, else `patch`.
 - Higher major exists: record the highest eligible version as a pending major. Do not apply it before step 7.
 - No candidate newer than the pin: current.
 - A 0.x pin is compared by its first non-zero segment: 0.13 to 0.14 is a major, 0.13.0 to 0.13.1 is a patch.
 
-A pin is current when it has no eligible patch or minor. If no pin has an eligible patch or minor, change no files and skip to step 7. If no major is pending either, report `all pins current` and stop.
+A pin is current when it has no eligible patch or minor. If no pin has an eligible patch or minor and every pin is exact, change no files and skip to step 7. If no major is pending either, report as in step 8 and stop.
 
 ## 3. Read release notes
 
@@ -61,6 +93,7 @@ gh release view v<version> --repo <owner>/<repo> --json body
 
 - Repository: `npm view <pkg> repository.url`.
 - No GitHub release for the tag: read `CHANGELOG.md` in the repository for the same range.
+- `@types/*` packages publish no GitHub releases and no changelog; record `no release notes`. For `@types/node`, also show the old and new versions against the `engines.node` floor in the root `package.json` and the output of `node -v`, and state that a newer major may type APIs the `engines.node` floor lacks.
 - Record each breaking change, deprecation and migration step per package.
 
 ## 4. Surface and stop
@@ -72,7 +105,7 @@ Print one list of patch and minor upgrades: package, old version, new version, t
 
 ## 5. Apply
 
-- Set each upgraded pin to the exact new version: no `^`, no `~`, no `latest`.
+- Set each upgraded pin to the exact new version: no `^`, no `~`, no `latest`. Set each non-exact pin that is not upgraded to its exact old version.
 - Run `<pm> install`.
 - Run each project script with `<pm> run <script>` in this order: `build`, `check`, `typecheck`, `test`. Skip a script the root `package.json` does not define.
 
@@ -94,7 +127,7 @@ After the patch and minor list, print each pending major as its own entry: packa
 
 ## 8. Report
 
-Print a table of changed packages, including applied majors:
+Print a table of changed packages, including applied majors and non-exact pins written as exact. With no changed package, print `all pins current` instead of the table.
 
 | Package | Old | New | Type |
 | --- | --- | --- | --- |
@@ -103,6 +136,7 @@ Print a table of changed packages, including applied majors:
 
 Below it list:
 
-- `held: major`: package, current version, newest eligible major, reason `declined` or `not confirmed`. List it even when every other pin is current; the no-change report is `all pins current` plus this list.
+- `held: major`: package, current version, newest eligible major, reason `declined` or `not confirmed`. List it even when every other pin is current.
+- `skipped`: package, manifest, spec, for every entry step 1 skipped.
 - `held: check failed`: package, old version, attempted version, error text. For a major, the reason is `check failed` with the error text.
 - Migrations applied, with the file changed.

package/templates/base/_gitignore

@@ -1,7 +1,42 @@
+# Dependencies
 node_modules
+
+# Build output
 dist
-.turbo
 .output
 .nitro
 .tanstack
+.cache
+.vite
+vite.config.ts.timestamp-*
+*.tsbuildinfo
+
+# Task cache
+.turbo
+
+# Tests
+coverage
+
+# Environment
+.env
+.env.*
+!.env.example
+
+# Agents
+.claude/settings.local.json
+.claude/worktrees
+
+# Deploy
+.vercel
+
+# OS and editors
+.DS_Store
+Thumbs.db
+.idea
+.vscode/*
+!.vscode/extensions.json
+!.vscode/settings.json
+
+# Logs and keys
 *.log
+*.pem

package/templates/base/apps/web/public/favicon.svg

@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32"><title>App</title><rect width="32" height="32" rx="6" fill="#0f172a"/><text x="16" y="22" text-anchor="middle" font-family="sans-serif" font-size="18" font-weight="700" fill="#f8fafc">d9</text></svg>

package/templates/base/apps/web/src/router.tsx

@@ -1,5 +1,5 @@
 import { QueryClient } from "@tanstack/react-query"
-import { createRouter } from "@tanstack/react-router"
+import { createRouter, ErrorComponent } from "@tanstack/react-router"
 import { setupRouterSsrQueryIntegration } from "@tanstack/react-router-ssr-query"
 import { routeTree } from "./routeTree.gen.ts"
 
@@ -13,6 +13,8 @@ export function getRouter() {
     scrollRestoration: true,
     defaultPreload: "intent",
     defaultPreloadStaleTime: 0,
+    defaultErrorComponent: ({ error }) => <ErrorComponent error={error} />,
+    defaultNotFoundComponent: () => <p>Not found</p>,
   })
 
   setupRouterSsrQueryIntegration({ router, queryClient })

package/templates/base/apps/web/src/routes/__root.tsx

@@ -10,7 +10,10 @@ export const Route = createRootRouteWithContext<{ queryClient: QueryClient }>()(
       { name: "viewport", content: "width=device-width, initial-scale=1" },
       { title: "App" },
     ],
-    links: [{ rel: "stylesheet", href: appCss }],
+    links: [
+      { rel: "stylesheet", href: appCss },
+      { rel: "icon", type: "image/svg+xml", href: "/favicon.svg" },
+    ],
   }),
   component: () => (
     <html lang="en">

package/templates/base/package.json

@@ -2,7 +2,7 @@
   "name": "my-app",
   "private": true,
   "type": "module",
-  "packageManager": "pnpm@12.11.0",
+  "packageManager": "pnpm@12.10.1",
   "engines": {
     "node": ">=22.18.0"
   },

package/templates/base/skills-lock.json

@@ -1,11 +1,29 @@
 {
   "version": 1,
   "skills": {
+    "hugeicons": {
+      "source": "hugeicons/hugeicons",
+      "sourceType": "github",
+      "skillPath": "skills/hugeicons/SKILL.md",
+      "computedHash": "4e65a89ca4417259b58c4e5c079d83fb977da214028334f504f18af820bbadcf"
+    },
+    "motion": {
+      "source": "motiondivision/ai-kit",
+      "sourceType": "github",
+      "skillPath": "plugins/motion/skills/motion/SKILL.md",
+      "computedHash": "76db0772da8f5056c4dc9433f8f8d691153f83ba4d4db20dfe38e19b5bb76809"
+    },
     "shadcn": {
       "source": "shadcn/ui",
       "sourceType": "github",
       "skillPath": "skills/shadcn/SKILL.md",
-      "computedHash": "2d7bf36e581289fdcc3ffc592c1ec1d7457572baa72ba0d440229ef34bd7f6dd"
+      "computedHash": "da388f632cd83783c02967446e21941c9ee8291ccb43ba74c23f7d4e9b7c298c"
+    },
+    "turborepo": {
+      "source": "vercel/turborepo",
+      "sourceType": "github",
+      "skillPath": "skills/turborepo/SKILL.md",
+      "computedHash": "9681d8dfeb5e6cdff767f1bcaba5d7ac55732a9d6c02ee120f44229f8ec25e7e"
     }
   }
 }

package/templates/integrations.json

@@ -0,0 +1,22 @@
+{
+  "shadcn": {
+    "kind": "stdio",
+    "command": "npx",
+    "args": ["shadcn@4.21.4", "mcp"],
+    "default": true
+  },
+  "hugeicons": {
+    "kind": "stdio",
+    "command": "npx",
+    "args": ["-y", "@hugeicons/mcp-server@0.2.2"],
+    "default": true
+  },
+  "motion": { "kind": "http", "url": "https://mcp.motion.dev", "default": true },
+  "motion-plus": {
+    "kind": "http",
+    "url": "https://mcp.motion.dev/plus",
+    "login": "Motion+ sign-in",
+    "default": false
+  },
+  "motion-cursor-rule": { "kind": "overlay", "hint": "Cursor only", "default": false }
+}

package/templates/optional/motion-cursor-rule/.cursor/rules/motion.mdc

@@ -0,0 +1,14 @@
+---
+description: Use the Motion skill for animation work, and never import from framer-motion
+globs: ["**/*.{ts,tsx,js,jsx,vue,svelte,astro,css,scss,sass}"]
+alwaysApply: false
+---
+
+When a change in this file animates anything — CSS `transition`/`@keyframes`,
+Motion (`motion`, `motion/react`, `motion-v`), a gesture, drag, scroll effect,
+reveal or page transition — use the `motion` skill first. It carries the
+official patterns, the docs search and the performance tiers.
+
+Never import from `framer-motion`. The package is `motion` (`motion/react` for
+React, `motion-v` for Vue). If this file still imports `framer-motion`, say so
+and offer to migrate it.