kaide 1.0.4 → 1.0.6

package/README.md

@@ -4,6 +4,8 @@
 
 > **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.
 
+<img src="kaide.png" alt="Kaide" width="610px" />
+
 ## Getting Started
 
 ### Installation & Setup

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kaide",
-  "version": "1.0.4",
+  "version": "1.0.6",
   "description": "AI-native architecture kit for modern React. High-discipline protocols for autonomous agents.",
   "type": "module",
   "bin": {

package/templates/.cursor/rules/core-principles.mdc

@@ -32,6 +32,7 @@ alwaysApply: true
 - `// ...existing code` (Provide full blocks).
 - Standard `TODO` or `FIXME` comments.
 - Using `INTENTIONAL_TODO` to skip core logic implementation.
+- Parent-relative imports (`../`, `../../`). Use path aliases only.
 
 ## Correct Implementation
 

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

@@ -54,7 +54,7 @@ export default async function DashboardPage() {
 // src/features/auth/actions/login.ts
 "use server";
 
-import { loginSchema } from "../schemas/login-schema";
+import { loginSchema } from "@/features/auth/schemas/login-schema";
 import { api } from "@/lib/api";
 
 export async function loginAction(formData: FormData) {

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

@@ -8,15 +8,15 @@ alwaysApply: false
 
 ## Principles
 - **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].
+- **Behavior Testing:** Focus on user outcomes (Arrange-Act-Assert).
 
 ## Tech Stack
-- [cite_start]Vitest & React Testing Library[cite: 1, 12].
+- Vitest & React Testing Library.
 
 ## Preferences (Not Hard Rules)
-- [cite_start]**API:** Use `MSW` for stable features; simple mocks are okay for rapid prototyping[cite: 5, 8].
-- [cite_start]**Location:** Keep `.test.ts` next to implementation[cite: 4].
-- [cite_start]**Snapshots:** Use only for small, static data structures to prevent maintenance hell.
+- **API:** Use `MSW` for stable features; simple mocks are okay for rapid prototyping.
+- **Location:** Keep `.test.ts` next to implementation.
+- **Snapshots:** Use only for small, static data structures to prevent maintenance hell.
 
 ## Correct Approach
 <example>

package/templates/docs/architecture-guide.md

@@ -25,11 +25,13 @@ Adhere strictly to the following tree structure. Creating arbitrary folders is F
 
 ```text
 src/
-├── app/ | routes/        # Routing layer (See Framework Rules)
-├── features/             # Domain & business logic
+├── app/ | routes/
+├── features/
 │   └── [feature-name]/
 │       ├── api/
 │       ├── components/
+│       ├── constants/
+│       ├── data/
 │       ├── helpers/
 │       ├── hooks/
 │       ├── schemas/
@@ -37,22 +39,23 @@ src/
 │       ├── types/
 │       └── index.ts
 ├── components/
-│   ├── ui/               # Atomic (shadcn)
-│   ├── layout/           # Layout parts
-│   └── shared/           # Reusable functional
-├── config/               # App/SEO config
-├── constants/            # Static values
-├── helpers/              # Framework-agnostic pure functions
+│   ├── icons/
+│   ├── layout/
+│   ├── shared/
+│   └── ui/
+├── config/
+├── constants/
+├── helpers/
 ├── hooks/
-├── i18n/                 # Localization setup
-├── lib/                  # Third-party configurations
-├── messages/             # Translations
-├── providers/            # Global context
-├── schemas/              # Shared validation
-├── stores/               # Global state
-├── styles/               # Tailwind/base CSS
-├── types/                # Global TS types
-└── env.ts                # Env validation
+├── i18n/
+├── lib/
+├── messages/
+├── providers/
+├── schemas/
+├── stores/
+├── styles/
+├── types/
+└── env.ts
 ```
 
 ## Shared vs. Feature Matrix (The Rule of Three)
@@ -62,10 +65,16 @@ Apply the following metric hierarchy to determine code location:
 - **Default Scope:** All logic and components originate within `features/[feature]/`.
 - **Promotion:** Any logic or component requested by 2 different features MUST be moved to the global `src/` (shared) layer.
 - **Cross-Import Ban:** Direct imports between features are FORBIDDEN. Communication is restricted to the `src/shared` layer or via prop-drilling at the Page level.
-- **Helpers:** Pure TypeScript functions that strictly transform input to output without side effects.
-- **Lib:** Contains project-specific configured instances of external libraries. Components MUST import the wrapped instance from `src/lib` rather than the external package directly.
+- **Helpers:** Pure TypeScript functions that strictly transform input to output without side effects. MUST NOT contain any package imports. (e.g., `isBrowser()`).
+- **Data:** Feature-specific static data (lists, config objects, constants). ONLY allowed within `features/[feature]/data/`.
+- **Lib:** Contains project-specific configured instances of external libraries (axios, date-fns, js-cookie, etc.). Files containing package imports MUST be placed here. Pure TS functions without package imports belong in `helpers`. (e.g., `isToday()` using date-fns goes to `lib`, `isBrowser()` goes to `helpers`).
 - **Zod Schemas:** All feature-related schemas MUST be stored in `features/[feature]/schemas/`. API functions and UI components MUST import from this single source to prevent duplication.
 
+## Imports
+
+- **Path Aliases:** Usage of path aliases is MANDATORY.
+- **Parent-Relative:** Parent-relative imports (`../`, `../../`) are FORBIDDEN. Use absolute path aliases.
+
 ## Server State & Ownership
 
 Server state is global, but access is hierarchical: