Themis128
Themis128 / 07-testing-rules
- **Runner:** Vitest - **Environment:** jsdom (for React components), node (for utilities) - **Config:** `vitest.config.mts` (unit), `vitest.integration.config.mts` (integration)
Themis128 / 06-security-rules
- **Auth store:** Cloudflare D1 `user-auth-db` — users, sessions, roles, password hashes (PBKDF2) - **Session:** Opaque `session_token` cookie (or Bearer header), resolved by `src/lib/api-auth.ts` - **Default session:** 30 days; 60 days with "remember me"
Themis128 / 10-ai-agent-rules
- **Direct and technical:** Be direct and technical in responses — no conversational filler ("Great", "Certainly", "Okay", "Sure") - **One tool at a time:** Wait for user confirmation after each tool use before proceeding - **Verify before completing:** Check task requirements, verify output files e…
Themis128 / 08-workflow-rules
- **Branch strategy:** Feature branches from `main`, PRs to `main` - **Commit messages:** Conventional commits format: `type(scope): description` - Types: `feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `style`, `ci`
Themis128 / 04-cloudflare-rules
- **Target platform is Cloudflare** (Workers, R2, D1, Access, Tunnel, DNS/CDN). New work should prefer Cloudflare-native services over AWS. - Treat remaining AWS usage (SSM, SES, Cognito, S3, Lambda, Athena, etc.) as **legacy to migrate off**, not expand.
Themis128 / 03-coding-standards
- **TypeScript:** Strict mode enabled. Prefer `interface` over `type` for object shapes. Use `type` for unions, intersections, and utility types. - **React:** Use functional components with hooks. Server Components by default; add `'use client'` only when interactivity is needed.
Themis128 / 01-project-overview
A Next.js 16 + Cloudflare Workers full-stack application for cloud consulting services.
Themis128 / 09-mcp-rules
The project uses the following MCP servers: