kaide 1.0.2 → 1.0.4

package/README.md

@@ -11,7 +11,7 @@
 1. Run the CLI to automatically install the configuration files:
 
    ```bash
-   npx kaide
+   npx kaide init
    ```
 2. (Recommended) For maximum adherence, point your AI tool to your identity in **Settings/Project Rules**:
 
@@ -64,4 +64,4 @@ While optimized for Cursor (`.mdc`), **Kaide** is built on pure Markdown and wor
 ## Security & Performance
 - **Zero Inline Script:** Strictly enforced CSP compliance.
 - **Locked Boundaries:** Server-only logic is isolated from client bundles.
-- **Optimized Assets:** Automatic enforcement of modern formats and performance patterns for peak scores.
+- **Optimized Assets:** Automatic enforcement of modern formats and performance patterns for peak scores.

package/package.json

@@ -1,12 +1,13 @@
 {
   "name": "kaide",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "AI-native architecture kit for modern React. High-discipline protocols for autonomous agents.",
   "type": "module",
   "bin": {
     "kaide": "./bin/kaide.js"
   },
   "keywords": [
+    "kaide",
     "ai",
     "react",
     "architecture",
@@ -19,8 +20,7 @@
     "tanstack",
     "typescript",
     "zod",
-    "cli",
-    "kaide"
+    "cli"
   ],
   "author": "Ömer Gülçiçek (https://github.com/omergulcicek)",
   "license": "MIT",

package/templates/.cursor/rules/frontend/tanstack-start.mdc

@@ -9,12 +9,13 @@ alwaysApply: false
 
 - **Route Definition:** Always use `createFileRoute`. Path MUST strictly match the file system location.
 - **Component Scope:** Keep route files thin. Only orchestrate routing and data. Move UI and business logic to `src/features`.
+- **Nested Layouts:** Use the `<Outlet />` component in parent routes to render child routes. If a route has children, the parent component MUST render `<Outlet />`.
 - **Data Loading:** Fetch all route-level data in `loader`. Consume via `Route.useLoaderData` or `useSuspenseQuery`.
 - **Guards:** Put auth, redirects, and preconditions in `beforeLoad`.
-- **Hydration:** For Next.js RSC, use dehydrate(queryClient) pattern. For Start, use loader prefetching.
+- **Hydration:** Rely on loader prefetching for data hydration. Do not use Next.js-specific patterns like manual dehydration.
 - **Server Functions:** Wrap all backend-only logic in standalone `serverFn`. Functions MUST act as a bridge to the API layer; keep database orchestration and business logic inside src/features/api or helpers.
 - **Search Params:** Validate all search params with `validateSearch` using a Zod schema. Never trust raw search values.
-- **i18n Implementation:** Use `paraglide-js` for translations. Import messages from `@/paraglide/messages`.
+- **i18n Implementation:** Use `paraglide-js` for translations. Follow the patterns defined in `i18n.mdc`.
 - **Error Handling:** Provide `errorComponent` for failure states. Handle expected errors in the loader.
 - **Loading UI:** Provide `pendingComponent` for async states when needed.
 - **Not Found:** Provide `notFoundComponent` for missing resources.

package/templates/.cursor/rules/frontend/testing.mdc

@@ -7,7 +7,7 @@ alwaysApply: false
 # Testing Guide (Pragmatic)
 
 ## Principles
-- **Value over Coverage:** Focus on testing complex business logic in `features/logic`. Skip simple UI components unless critical.
+- **Value over Coverage:** Focus on testing complex business logic in `features/[feature]`. Skip simple UI components unless critical.
 - [cite_start]**Behavior Testing:** Focus on user outcomes (Arrange-Act-Assert)[cite: 3].
 
 ## Tech Stack