@totaland/create-starter-kit 2.0.0 → 2.0.1

package/templates/frontend/src/App.tsx

@@ -1,7 +1,7 @@
 import { Route, Routes } from 'react-router-dom';
-import { Layout } from './components/layout/Layout';
-import { AboutPage } from './pages/about/AboutPage';
-import { HomePage } from './pages/home/HomePage';
+import { Layout } from './components/layout/layout.component';
+import { AboutPage } from './pages/about/about.page';
+import { HomePage } from './pages/home/home.page';
 
 function App() {
   return (

package/templates/backend/AGENTS.md

@@ -1,23 +0,0 @@
-# Repository Guidelines
-
-## Project Structure & Module Organization
-TypeScript sources live in `src/`, with graph traversal logic under `src/graph/` (crawl policy, state hashing, trajectory storage) and telemetry helpers in `src/telemetry.ts`. Example entrypoints such as `src/demo.ts` show how agents orchestrate flows. Generated JavaScript lands in `build/` (never hand-edit). Documentation and design notes are under `docs/`, and replay artifacts persist to `storage/` while running crawls or demo scripts. Keep tests adjacent to the code (for example `src/graph/xstate.test.ts`).
-
-## Build, Test, and Development Commands
-- `pnpm install`: sets up dependencies for both the CLI and Playwright runtime.
-- `pnpm typecheck`: runs `tsc --noEmit` against `tsconfig.json` to catch type regressions early.
-- `pnpm build`: compiles `src/` to ESM output in `build/` via SWC; use `pnpm build:debug` when you need source maps.
-- `pnpm test`, `pnpm test:watch`, `pnpm test:ui`: execute the Vitest suite in batch, watch, or UI mode.
-- `pnpm knip`: detects unused files, exports, and dependencies—fix warnings before raising a PR.
-
-## Coding Style & Naming Conventions
-Follow the repository's Biome configuration (`biome.json`) and run `npx biome check .` if needed. Use 2-space indentation, TypeScript `strict` semantics, and ECMAScript modules (`import/export`). Exported symbols and files should read as actions or nouns (`discoverState`, `persist.ts`). Tests mirror the file under test (`xstate.test.ts`). Prefer descriptive async function names reflecting their side effects.
-
-## Testing Guidelines
-Vitest drives all unit and integration coverage. Name suites after the module (`describe("bfs")`) and isolate Playwright-heavy tests behind capability checks to keep CI fast. New behavior must include at least one test validating failure handling and a corresponding happy path. Run `pnpm test` locally before committing; `storage/` fixtures may be stubbed with lightweight mocks to avoid hitting real browsers.
-
-## Commit & Pull Request Guidelines
-Use imperative, conventional messages observed in history (`feat:`, `chore:`, `fix:`). One logical change per commit, referencing an issue ID when relevant. Pull requests should describe motivation, summarize testing (`pnpm test` output, screenshots for Playwright interactions), and link design docs in `docs/` if expanded. Request review from an owner when touching crawl policy or telemetry layers, and ensure CI (typecheck, build, tests) passes before assignment.
-
-## Environment & Configuration Tips
-Configure credentials through `.env` files consumed by Crawlee/Playwright—never hard-code tokens. For telemetry, set OpenTelemetry exporters via environment variables before running demos. Heavy crawls persist checkpoints to `storage/`; clean stale runs before committing to keep diffs focused.

package/templates/backend/ARCHITECTURE.md

@@ -1,53 +0,0 @@
-# Architecture Pattern Examples
-
-This starter kit demonstrates a blend of patterns from **"Designing Data-Intensive Applications"** and **"Patterns of Enterprise Application Architecture"**.
-
-## Order System Example
-
-### From Designing Data-Intensive Applications (DDIA):
-
-1. **Event Sourcing** - All state changes stored as immutable events
-   - `order.entity.ts`: Events are the source of truth
-   - Events: `OrderCreated`, `ItemAdded`, `OrderPlaced`
-
-2. **CQRS (Command Query Responsibility Segregation)**
-   - Commands: `commands.usecase.ts` - Write operations that generate events
-   - Queries: `queries.usecase.ts` - Read operations from materialized views
-
-3. **Materialized Views** - Denormalized data for fast queries
-   - `order.repository.impl.ts`: `readModel` maintains pre-computed summaries
-   - User index for O(1) lookups by user ID
-
-4. **Append-Only Log** - Event store never modifies existing data
-   - New events are appended, never updated or deleted
-
-### From Patterns of Enterprise Application Architecture (PEAA):
-
-1. **Repository Pattern** - Abstract data access
-   - `order.repository.ts`: Interface defining data operations
-   - Separates domain logic from persistence
-
-2. **Domain Model** - Rich business logic in entities
-   - `order.entity.ts`: Order entity with business rules and validation
-
-3. **Use Case / Service Layer** - Application logic orchestration
-   - Commands and queries as separate use cases
-   - Transaction boundaries and workflow management
-
-## API Endpoints
-
-```
-POST   /orders              # Create new order
-POST   /orders/:id/items    # Add item to order
-POST   /orders/:id/place    # Place order
-GET    /orders/:id          # Get order details
-GET    /orders/user/:userId # Get user's orders (fast via materialized view)
-GET    /orders/:id/events   # Get event stream (audit log)
-```
-
-## Key Benefits
-
-- **Scalability**: Read/write separation allows independent scaling
-- **Auditability**: Complete event history for compliance/debugging
-- **Performance**: Materialized views optimize common queries
-- **Maintainability**: Clean architecture with separated concerns

package/templates/backend/ORDER_SYSTEM.md

@@ -1,93 +0,0 @@
-# Order System with Drizzle ORM
-
-## Setup
-
-### 1. Environment Variables
-
-Create a `.env` file:
-
-```bash
-# Optional: PostgreSQL connection (if not set, uses in-memory)
-DATABASE_URL=postgres://user:password@localhost:5432/orders_db
-
-PORT=3000
-```
-
-### 2. Database Setup (Optional - for PostgreSQL)
-
-If you want to use PostgreSQL instead of in-memory storage:
-
-```bash
-# Generate migration
-pnpm drizzle-kit generate
-
-# Run migration
-pnpm drizzle-kit migrate
-
-# Or use push for development
-pnpm drizzle-kit push
-```
-
-### 3. Run the Server
-
-```bash
-# Development
-pnpm dev
-
-# Production
-pnpm build
-pnpm start
-```
-
-## API Endpoints
-
-Base URL: `http://localhost:3000/api`
-
-### Create Order
-```bash
-POST /api/orders
-Content-Type: application/json
-
-{
-  "userId": "550e8400-e29b-41d4-a716-446655440000"
-}
-```
-
-### Add Item to Order
-```bash
-POST /api/orders/:orderId/items
-Content-Type: application/json
-
-{
-  "productId": "660e8400-e29b-41d4-a716-446655440000",
-  "quantity": 2,
-  "price": 29.99
-}
-```
-
-### Place Order
-```bash
-POST /api/orders/:orderId/place
-```
-
-### Get Order Details
-```bash
-GET /api/orders/:orderId
-```
-
-### Get User's Orders (Fast - from materialized view)
-```bash
-GET /api/orders/user/:userId
-```
-
-### Get Order Event Stream (Audit log)
-```bash
-GET /api/orders/:orderId/events
-```
-
-## Architecture
-
-- **No DATABASE_URL**: Uses in-memory repository (for testing/demo)
-- **With DATABASE_URL**: Uses Drizzle ORM with PostgreSQL
-- Event Sourcing with materialized views for optimal read performance
-- CQRS pattern with separate command and query operations