kaide 1.0.1 → 1.0.3

package/README.md

@@ -4,6 +4,25 @@
 
 > **Kaide** (Etymology: Turkish): A fundamental rule, principle, or base that provides structural integrity. The name cleverly embeds **AI** (K**ai**de), reflecting its core mission.
 
+## Getting Started
+
+### Installation & Setup
+
+1. Run the CLI to automatically install the configuration files:
+
+   ```bash
+   npx kaide
+   ```
+2. (Recommended) For maximum adherence, point your AI tool to your identity in **Settings/Project Rules**:
+
+> **Adhere to `AGENTS.md` for persona/planning and `docs/` for architectural constitutions.**
+
+### Usage Workflow
+This kit follows a **Plan-First Protocol**:
+- **Initialize:** Ask the AI to read the rules: `Read all .mdc files and AGENTS.md.`
+- **Plan:** Propose a feature: `I want to build a [Feature Name]. Create an architectural plan.`
+- **Execute:** After approving the plan, the AI will generate code following the strict constraints of the relevant `.mdc` files.
+
 ## The Problem We Solve
 
 **Kaide** provides the missing governance layer to turn AI from a simple coder into a high-level Staff Engineer.
@@ -28,21 +47,6 @@ The system operates on a **Three-Layer Governance** model:
 - **Optimized for Modern Tech:** Seamless support for Next.js and TanStack Start for world-class web applications.
 - **Performance-First:** Built-in rules for LCP optimization, CLS prevention, and maximum efficiency.
 
-## Getting Started
-
-### Installation & Setup
-
-1. Copy the `.cursor/rules/` folder, `docs/` directory, and `AGENTS.md` file to your project root.
-2. (Recommended) For maximum adherence, point your AI tool to your identity in **Settings/Project Rules**:
-
-> **Adhere to `AGENTS.md` for persona/planning and `docs/` for architectural constitutions.**
-
-### Usage Workflow
-This kit follows a **Plan-First Protocol**:
-- **Initialize:** Ask the AI to read the rules: `Read all .mdc files and AGENTS.md.`
-- **Plan:** Propose a feature: `I want to build a [Feature Name]. Create an architectural plan.`
-- **Execute:** After approving the plan, the AI will generate code following the strict constraints of the relevant `.mdc` files.
-
 ## LLM Agnostic Usage
 While optimized for Cursor (`.mdc`), **Kaide** is built on pure Markdown and works with any "Agentic" AI (Claude Code, Windsurf, GitHub Copilot CLI, etc.):
 - All `.mdc` files are standard Markdown. No conversion is needed.
@@ -60,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,6 +1,6 @@
 {
   "name": "kaide",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "AI-native architecture kit for modern React. High-discipline protocols for autonomous agents.",
   "type": "module",
   "bin": {

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