nextworks 0.1.0-alpha.1 → 0.1.0-alpha.10

package/dist/kits/blocks/.nextworks/docs/BLOCKS_QUICKSTART.md

@@ -0,0 +1,193 @@
+# Blocks Quickstart
+
+This document explains the Blocks kit: prebuilt UI sections, templates and core UI primitives included in this repository. The Blocks kit is intended to be a non-invasive copyable kit (shadCN-style) you can install into any Next.js App Router + TypeScript + Tailwind project.
+
+> **Alpha note**
+> Other kits (Auth Core, Forms, Data) are currently tested and supported on top of a default Blocks install. For the smoothest experience, install Blocks first in your app before adding other kits.
+
+> If you are using the `nextworks` CLI in your own app, you can install this Blocks kit by running:
+>
+> ```bash
+> npx nextworks add blocks --sections --templates
+> ```
+>
+> This installs **core UI primitives, sections, and page templates**, so the example templates work out of the box. The CLI will copy files into your project under `components/`, `app/templates/`, `lib/`, and `public/` as described below.
+>
+> Advanced:
+>
+> - `npx nextworks add blocks --ui-only` → install core UI primitives only (no sections/templates).
+> - `npx nextworks add blocks --sections` → install core + sections only.
+> - `npx nextworks add blocks --templates` → install core + templates only.
+> - `npx nextworks add blocks --sections --templates` → install core + sections + templates.
+
+What’s included
+
+- Page templates (composed from sections):
+  - app/templates/productlaunch
+  - app/templates/saasdashboard
+  - app/templates/digitalagency
+- Reusable UI sections: components/sections/\* (Navbar, Hero, Features, Pricing, Testimonials, FAQ, Contact, Footer, etc.)
+- Core UI primitives: components/ui/\* (Button, Input, Card, Select, Checkbox, Switch, Theme toggle/selector, Form primitives)
+- Theme helpers and presets: components/PresetThemeVars in each template and lib/themes.ts
+- Global styles: app/globals.css and optional theme variables in each template's PresetThemeVars file
+- Sample placeholder assets: public/placeholders/\*
+
+Where to look
+
+- Templates:
+  - app/templates/productlaunch/page.tsx (productlaunch template)
+  - app/templates/saasdashboard/page.tsx (saasdashboard template)
+  - app/templates/digitalagency/page.tsx (digital agency template)
+- Sections:
+  - components/sections/\*.tsx
+- UI primitives and form building blocks:
+  - components/ui/button.tsx
+  - components/ui/input.tsx
+  - components/ui/label.tsx
+  - components/ui/card.tsx
+  - components/ui/textarea.tsx
+  - components/ui/select.tsx
+  - components/ui/checkbox.tsx
+  - components/ui/switch.tsx
+  - components/ui/form/\* (Form, FormField, FormItem, FormControl, FormLabel, FormMessage, FormDescription)
+- Theme and providers:
+  - components/theme-provider.tsx
+  - components/enhanced-theme-provider.tsx
+  - lib/themes.ts
+
+Minimal steps to render a template locally
+
+1. Install dependencies and run the dev server:
+
+   npm install
+   npm run dev
+
+2. Open the productlaunch template in your browser:
+
+   http://localhost:3000/templates/productlaunch
+
+3. The templates use global styles (app/globals.css). No environment variables are required for Blocks-only usage.
+
+How to adopt / override template pieces
+
+- Slots & component overrides
+  - Each template composes small sections from components/sections/\*.tsx. To override a section, copy the desired section file into your project (or replace the import) and update props or classNames.
+  - Example: to override the Navbar, copy components/sections/Navbar.tsx into your app and update the markup or styles. The template imports Navbar from the components directory.
+
+- Styling and utility classes
+  - Tailwind is used across components. Prefer adding or modifying Tailwind utility classes on the exported component or pass className props (many components accept className).
+
+- Theme variables and PresetThemeVars
+  - Each template has a PresetThemeVars component/file (e.g., app/templates/productlaunch/PresetThemeVars.tsx) that injects CSS variables for theme presets.
+  - To change default palette or add presets, edit the template PresetThemeVars and lib/themes.ts.
+  - Theme providers are implemented in components/theme-provider.tsx and components/enhanced-theme-provider.tsx — wrap your app with these if you extract blocks into another project.
+
+Import examples
+
+- Import a primitive in your code:
+
+  import Button from "@/components/ui/button";
+  import { Form, FormField } from "@/components/ui/form/form"; // path depends on your project alias
+
+- Use a section in a page:
+
+  import Navbar from "@/components/sections/Navbar";
+
+  export default function Page() {
+  return (
+  <>
+  <Navbar />
+  <main>{/_ ... _/}</main>
+  </>
+  );
+  }
+
+Public assets and placeholders
+
+- The templates reference placeholder images in public/placeholders/. If you copy templates to another project, copy the referenced assets (public/placeholders/gallery/\*) or replace with your own images.
+
+Simple Blocks kit manifest (for internal CLI packaging)
+
+> This section is for maintainers of the `nextworks` CLI. You don’t need this if you’re just installing Blocks into your own app.
+
+Use this manifest to drive a CLI copy step: it enumerates the primary files that make up the Blocks kit. Adjust paths if your CLI uses a different base.
+
+- Suggested internal path: cli/kits/blocks/manifest.json
+
+Contents:
+
+{
+"name": "blocks",
+"description": "Frontend UI sections, templates and core UI primitives",
+"files": [
+"components/sections/About.tsx",
+"components/sections/Contact.tsx",
+"components/sections/CTA.tsx",
+"components/sections/FAQ.tsx",
+"components/sections/Features.tsx",
+"components/sections/Footer.tsx",
+"components/sections/HeroMotion.tsx",
+"components/sections/HeroOverlay.tsx",
+"components/sections/HeroSplit.tsx",
+"components/sections/Navbar.tsx",
+"components/sections/Newsletter.tsx",
+"components/sections/PortfolioSimple.tsx",
+"components/sections/Pricing.tsx",
+"components/sections/ProcessTimeline.tsx",
+"components/sections/ServicesGrid.tsx",
+"components/sections/Team.tsx",
+"components/sections/Testimonials.tsx",
+"components/sections/TrustBadges.tsx",
+"components/ui/button.tsx",
+"components/ui/card.tsx",
+"components/ui/checkbox.tsx",
+"components/ui/cta-button.tsx",
+"components/ui/dropdown-menu.tsx",
+"components/ui/feature-card.tsx",
+"components/ui/input.tsx",
+"components/ui/label.tsx",
+"components/ui/pricing-card.tsx",
+"components/ui/skeleton.tsx",
+"components/ui/switch.tsx",
+"components/ui/table.tsx",
+"components/ui/textarea.tsx",
+"components/ui/theme-selector.tsx",
+"components/ui/theme-toggle.tsx",
+"components/ui/toaster.tsx",
+"components/ui/form/form.tsx",
+"components/ui/form/form-field.tsx",
+"components/ui/form/form-item.tsx",
+"components/ui/form/form-control.tsx",
+"components/ui/form/form-description.tsx",
+"components/ui/form/form-label.tsx",
+"components/ui/form/form-message.tsx",
+"components/enhanced-theme-provider.tsx",
+"components/theme-provider.tsx",
+"lib/themes.ts",
+"app/globals.css",
+"app/templates/productlaunch/page.tsx",
+"app/templates/productlaunch/PresetThemeVars.tsx",
+"app/templates/productlaunch/README.md",
+"app/templates/saasdashboard/page.tsx",
+"app/templates/saasdashboard/PresetThemeVars.tsx",
+"app/templates/saasdashboard/README.md",
+"app/templates/digitalagency/page.tsx",
+"app/templates/digitalagency/PresetThemeVars.tsx",
+"app/templates/digitalagency/README.md",
+"public/placeholders/gallery/hero-pexels-broken-9945014.avif"
+]
+}
+
+Notes & recommendations
+
+- Blocks are self-contained and do not require Prisma or NextAuth. If your user only needs Blocks, the CLI should copy these files and add a brief README instructing the user to import the theme provider in app/layout.tsx and ensure app/globals.css is present.
+- Consider adding an examples folder demonstrating how to swap PresetThemeVars and override a section component.
+
+---
+
+If you'd like, I can:
+
+- Create the CLI manifest file at cli/kits/blocks/manifest.json using the JSON above, or
+- Create a short example that demonstrates overriding Navbar and changing PresetThemeVars.
+
+Tell me which of the above to create next.

package/dist/kits/blocks/{README.md → .nextworks/docs/BLOCKS_README.md}

@@ -9,6 +9,18 @@ What the kit includes
 - Theme and provider utilities (theme-provider, enhanced-theme-provider, lib/themes)
 - app/globals.css and placeholder assets used by templates
 
+Install behavior
+
+> **Alpha note**
+> Other kits (Auth Core, Forms, Data) are currently tested and supported on top of a Blocks install that includes sections and templates. For the smoothest experience, run `npx nextworks add blocks --sections --templates` before adding additional kits.
+
+- For a full UI kit, run `npx nextworks add blocks --sections --templates` to install **core UI primitives, sections, and templates** so the example templates work out of the box.
+- You can pass flags to control what gets installed:
+  - `npx nextworks add blocks --ui-only` → core UI primitives only (no sections/templates).
+  - `npx nextworks add blocks --sections` → core + sections only.
+  - `npx nextworks add blocks --templates` → core + templates only.
+  - `npx nextworks add blocks --sections --templates` → same as the default (core + sections + templates).
+
 Files included are defined in `cli/cli_manifests/blocks_manifest.json` in the Nextworks repository. When updating this kit inside the repo, keep that manifest and this kit folder in sync.
 
 Post-install notes

package/dist/kits/blocks/.nextworks/docs/THEME_GUIDE.md

@@ -0,0 +1,223 @@
+# Theme System Guide
+
+This file is shipped with the Nextworks Blocks kit and lives under `.nextworks/docs/THEME_GUIDE.md` in your project.
+
+The content below is the canonical theme guide for projects using Nextworks Blocks.
+
+---
+
+## Overview
+
+This project now includes a comprehensive theming system that allows you to easily switch between different color schemes and have all components automatically adapt.
+
+## How to Use
+
+### 1. Basic Setup
+
+Your app is already configured with the enhanced theme provider in `app/layout.tsx`. The default theme is set to "monochrome".
+
+### 2. Available Themes
+
+- **Monochrome** - Clean black and white theme
+- **Blue** - Professional blue color scheme
+- **Green** - Fresh green color scheme
+- **Purple** - Modern purple color scheme
+- **Orange** - Vibrant orange color scheme
+- **Default** - Standard shadCN theme
+
+### 3. Using Theme-Aware Components
+
+#### Navbar2 Component
+
+```tsx
+import { Navbar2 } from "@/components/sections/Navbar2";
+
+<Navbar2
+  brand="My App"
+  brandNode={<YourLogoComponent />}
+  menuItems={[
+    { label: "Home", href: "/" },
+    { label: "About", href: "/about" },
+  ]}
+  ctaButton={{ label: "Get Started", href: "/signup" }}
+  showThemeSelector={true}
+/>;
+```
+
+#### Theme Selector
+
+The `ThemeSelector` component is automatically included in Navbar2 and allows users to:
+
+- Switch between theme variants (monochrome, blue, green, etc.)
+- Toggle between light/dark modes
+- Use system preference
+
+### 4. Converting Existing Components
+
+To make your existing components theme-aware, replace hardcoded colors with semantic classes:
+
+#### Before (Hardcoded Colors):
+
+```tsx
+className = "bg-gray-50 dark:bg-gray-800 text-gray-800 dark:text-white";
+```
+
+#### After (Theme-Aware):
+
+```tsx
+className = "bg-background text-foreground";
+```
+
+#### Common Replacements:
+
+- `text-gray-800 dark:text-white` → `text-foreground`
+- `bg-gray-50 dark:bg-gray-800` → `bg-background`
+- `border-gray-200 dark:border-gray-700` → `border-border`
+- `hover:bg-gray-100 dark:hover:bg-gray-700` → `hover:bg-accent`
+- `text-blue-600 dark:text-blue-500` → `text-primary`
+
+### 5. Semantic Color Classes
+
+Use these semantic classes for consistent theming:
+
+- `text-primary` - Primary brand color
+- `text-secondary` - Secondary text color
+- `text-muted-foreground` - Muted text color
+- `bg-background` - Main background color
+- `bg-card` - Card background color
+- `bg-accent` - Accent background color
+- `border-border` - Border color
+- `ring-ring` - Focus ring color
+
+### 6. Creating Custom Themes
+
+To create a custom theme, modify `lib/themes.ts`:
+
+```ts
+export const themes: Record<ThemeVariant, ThemeConfig> = {
+  // ... existing themes
+  myCustomTheme: {
+    name: "My Custom Theme",
+    colors: {
+      primary: "oklch(0.5 0.2 120)", // Custom green
+      primaryForeground: "oklch(0.98 0 0)",
+      // ... other colors
+    },
+  },
+};
+```
+
+### 7. Example Usage
+
+See the templates under `app/templates/*` and `lib/themes.ts` for concrete examples of how themes are wired up.
+
+## Benefits
+
+1. **Consistent Design**: All components automatically use the same color scheme
+2. **Easy Customization**: Change the entire app's look by switching themes
+3. **Accessibility**: Proper contrast ratios maintained across all themes
+4. **Developer Experience**: No need to manually style each component
+5. **User Choice**: Users can choose their preferred theme and light/dark mode
+
+---
+
+## Mixing tokens and local overrides
+
+Sometimes you want the speed and consistency of the Color Theme (tokens), but still make template-specific tweaks. This project supports three patterns:
+
+- Token-first: use semantic classes/variants everywhere (default behavior)
+- Hybrid: keep tokens for most things and override specific slots/elements
+- Full control: bypass tokens with unstyled primitives and fully custom classes
+
+### 1) Prefer additive overrides first
+
+- Keep variant/size from tokens and add className for small tweaks.
+- Use component slot props for targeted overrides rather than global changes.
+
+Example: override only mobile link hover background in the shared Navbar from a preset, leaving everything else token-based.
+
+```tsx
+// app/templates/productlaunch/components/Navbar.tsx
+mobileLinks: {
+  className: "hover:bg-purple-50 dark:hover:bg-purple-900/20",
+},
+```
+
+### 2) Override focus ring colors locally
+
+Links in Navbar apply a token focus ring (`focus:ring-ring`). You can override it per preset by placing your ring utilities in `links.className` (these are merged last):
+
+```tsx
+// app/templates/productlaunch/components/Navbar.tsx
+links: {
+  className:
+    "text-sm font-medium font-inter text-gray-800 dark:text-white hover:text-purple-700 dark:hover:text-purple-500 " +
+    "focus:ring-purple-500 dark:focus:ring-purple-400",
+},
+```
+
+### 3) ThemeToggle with local styling
+
+`ThemeToggle` accepts `buttonProps` that forward to the internal `Button`. For small tweaks, keep token variants and just add classes. For full control, use `unstyled: true` to bypass tokens:
+
+```tsx
+// app/templates/productlaunch/components/Navbar.tsx
+themeToggle: {
+  buttonProps: {
+    unstyled: true,
+    className:
+      "size-9 p-0 flex items-center justify-center rounded-md border border-gray-200 " +
+      "bg-white text-gray-700 hover:bg-purple-50 hover:text-purple-700 " +
+      "dark:border-gray-800 dark:bg-gray-900 dark:text-gray-100 dark:hover:bg-purple-900/20 " +
+      "transition-colors focus:outline-none focus:ring-2 focus:ring-purple-500 dark:focus:ring-purple-400",
+  },
+  moonClassName: "text-gray-700 dark:text-gray-100",
+  sunClassName: "text-gray-700 dark:text-gray-100",
+},
+```
+
+### 4) Unstyled escape hatch for primitives
+
+Shared primitives like `Button` support an `unstyled` prop to bypass tokenized CVA classes and allow complete consumer control:
+
+```tsx
+// components/ui/button.tsx
+<Button unstyled className="rounded-md bg-purple-600 px-3 py-2 text-white ...">
+  Click me
+</Button>
+```
+
+Use this when a section must not be influenced by the global Color Theme.
+
+### 5) Navbar accent via CSS variables (recommended for presets)
+
+Set a small set of CSS variables on the Navbar root in your preset, and internal elements (ThemeToggle, mobile links, focus rings) will read them automatically with fallbacks to tokens.
+
+Suggested variables:
+
+- `--navbar-accent`: icon/text accent color
+- `--navbar-hover-bg`: hover background color for toggle and mobile links
+- `--navbar-toggle-bg`: default background for the theme toggle button
+- `--navbar-ring`: focus ring color
+- `--navbar-border`: border color for theme toggle and similar controls
+
+Example in a preset:
+
+```tsx
+// app/templates/productlaunch/components/Navbar.tsx
+nav: {
+  className:
+    "bg-white dark:bg-gray-900 text-gray-800 dark:text-white border-b border-gray-200 dark:border-gray-800 " +
+    "[--navbar-accent:theme(colors.purple.600)] dark:[--navbar-accent:theme(colors.purple.400)] " +
+    "[--navbar-hover-bg:theme(colors.purple.50)] dark:[--navbar-hover-bg:color-mix(in oklab,oklch(0.17 0.05 324) 20%, transparent)] " +
+    "[--navbar-ring:theme(colors.purple.500)] dark:[--navbar-ring:theme(colors.purple.400)]",
+},
+```
+
+After setting these, you generally don’t need to pass `themeToggle` overrides; the toggle and links will align to your preset accent automatically.
+
+Notes:
+
+- Consumer `className` is merged last, so your overrides win when conflicts exist.
+- Always include `dark:` variants when you override hover/focus to maintain dark mode parity.
+- Scope overrides narrowly (slots/elements) to avoid surprising global changes.

package/dist/kits/blocks/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Jakob Bro Liebe Hansen
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/kits/data/.nextworks/docs/DATA_QUICKSTART.md

@@ -0,0 +1,112 @@
+# nextworks — Data kit quickstart
+
+This document explains how to use the Data (crud) kit in the nextworks starter project.
+
+Prerequisites
+
+- A running PostgreSQL database and `DATABASE_URL` set in `.env`.
+- Auth kit installed and configured (NextAuth + Prisma). The Data kit relies on NextAuth session for access control.
+  - In the monorepo, this is already wired up.
+  - In your own app via the CLI, the recommended alpha setup is to install Blocks (with sections + templates) + Auth Core + Forms first, then Data:
+
+    ```bash
+    npx nextworks add blocks --sections --templates
+    npx nextworks add auth-core
+    npx nextworks add forms
+    npx nextworks add data
+    ```
+
+    then follow the Prisma and `.env` steps below.
+
+- Forms kit (optional but recommended) for form primitives.
+
+Setup
+
+1. Install dependencies and generate Prisma client:
+
+   npm install
+   npx prisma generate
+
+2. Run migrations (creates User/Post tables):
+
+   Make sure you have merged the Auth + Data models into your `prisma/schema.prisma` before running migrations.
+
+   npx prisma migrate dev
+
+3. Seed a demo admin user and posts locally (optional):
+
+   # Set env vars or use defaults
+
+   SEED_ADMIN_EMAIL=admin@example.com SEED_ADMIN_PASSWORD=password123 node ./scripts/seed-demo.mjs
+
+4. Run the dev server:
+
+   npm run dev
+
+Usage & testing
+
+- Sign in at /auth/login using the seeded admin credentials (admin@example.com / password123).
+- Visit /admin/posts to create/edit/delete posts. The UI supports pagination, search (title contains), and sort by createdAt.
+- Visit /admin/users to view users (admin-only).
+
+Notes
+
+- Server-side RBAC: all modifying APIs (POST/PUT/DELETE) require a valid session, and user-level checks ensure only authors or admins can modify posts. The users list API requires admin access.
+- Published flag: posts have a `published` boolean in Prisma. The admin UI exposes the published checkbox when creating or editing posts.
+
+Troubleshooting
+
+- If users list returns 403, ensure your signed-in user has role = 'admin'. You can promote a user with Prisma Studio or by running:
+
+  npx prisma db executeRaw "UPDATE \"User\" SET role = 'admin' WHERE email = 'admin@example.com';"
+
+- If migrations fail, try:
+
+  npx prisma migrate reset
+
+Files & kit manifest
+
+If you plan to package a Data kit, here are the primary files, API routes and components used by the Data example flows. This manifest is intended to help packaging and documentation — adjust paths if you extract the kit into another project.
+
+Files
+
+- app/api/posts/route.ts
+- app/api/posts/[id]/route.ts
+- app/api/users/route.ts
+- app/api/users/[id]/route.ts
+- app/api/users/check-unique/route.ts
+- app/api/users/check-email/route.ts
+- app/api/seed-demo/route.ts
+- app/api/signup/route.ts
+- components/admin/admin-header.tsx
+- components/admin/posts-manager.tsx
+- components/admin/users-manager.tsx
+- app/(protected)/admin/users/page.tsx
+- app/(protected)/admin/posts/page.tsx
+- app/examples/demo/create-post-form.tsx
+- app/examples/demo/page.tsx
+- lib/prisma.ts
+- lib/server/result.ts
+- lib/utils.ts
+- lib/validation/forms.ts
+- scripts/seed-demo.mjs
+
+API routes (list)
+
+- /api/posts (GET/POST) -> app/api/posts/route.ts
+- /api/posts/:id (GET/PUT/DELETE) -> app/api/posts/[id]/route.ts
+- /api/users (GET/POST) -> app/api/users/route.ts
+- /api/users/:id (GET/PUT/DELETE) -> app/api/users/[id]/route.ts
+- /api/users/check-unique -> app/api/users/check-unique/route.ts
+- /api/users/check-email -> app/api/users/check-email/route.ts
+- /api/seed-demo -> app/api/seed-demo/route.ts
+- /api/signup -> app/api/signup/route.ts
+
+Notes
+
+- The Data kit relies on NextAuth sessions for access control — see lib/auth-helpers.ts and lib/auth.ts for server-side helpers and RBAC checks.
+- The API routes return ApiResult envelope objects (see lib/server/result.ts) and the client uses lib/forms/map-errors.ts to map server validation errors into react-hook-form where appropriate.
+
+Feedback
+
+- File issues in the repo; note that CLI packaging for the Data kit is not yet implemented — this quickstart is for the repository as-is.

package/dist/kits/data/{README.md → .nextworks/docs/DATA_README.md}

@@ -8,6 +8,19 @@ npx nextworks add data
 
 and is packaged with its own kit dependencies metadata.
 
+> **Alpha note**
+>
+> In this early alpha, the Data kit is tested and supported on top of **Blocks** (with sections + templates), **Auth Core**, and **Forms**. For the smoothest experience, run:
+>
+> ```bash
+> npx nextworks add blocks --sections --templates
+> npx nextworks add auth-core
+> npx nextworks add forms
+> npx nextworks add data
+> ```
+>
+> Using Data without Blocks/Auth/Forms may work but is not yet a supported path and can require manual Prisma/schema and UI tweaks.
+
 What the kit includes
 
 - API routes:

package/dist/kits/data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Jakob Bro Liebe Hansen
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/kits/data/lib/prisma.ts

@@ -13,3 +13,13 @@ export const prisma =
   });
 
 if (process.env.NODE_ENV !== "production") globalForPrisma.prisma = prisma;
+
+if (process.env.NODE_ENV === "development" && process.platform === "win32") {
+  // Dev-only hint for Windows users hitting Prisma + Turbopack symlink issues
+  // (e.g. "create symlink to ../../../../node_modules/@prisma/client" with os error 1314).
+  // This is intentionally a console.warn so it surfaces clearly but only in dev.
+  // See docs/DATA_QUICKSTART.md for full details.
+  console.warn(
+    "[nextworks][data] On Windows with Next 16+ and Prisma, enable Windows Developer Mode or run your dev server from an elevated terminal to avoid Prisma symlink errors (os error 1314). See DATA_QUICKSTART.md for details."
+  );
+}