moicle 1.4.0 → 1.7.0

package/README.md

@@ -23,6 +23,7 @@ A toolkit to bootstrap and accelerate project development with Claude Code throu
 ## Current Support
 
 - [x] Claude
+- [x] Codex CLI
 - [ ] Antigravity
 - [ ] Cursor
 - [ ] Windsurf
@@ -39,10 +40,12 @@ npm install -g moicle
 # Install agents, commands, skills, architecture
 moicle install
 
+# Install for Codex CLI
+moicle install --target codex --global
+
 # Choose:
-# 1. Global (~/.claude/)     - Use for all projects
-# 2. Project (./.claude/)    - Current project only
-# 3. Both                    - Both locations
+# 1. Pick Claude Code or Codex CLI
+# 2. Pick global or project scope
 ```
 
 ## CLI Commands
@@ -52,6 +55,8 @@ moicle install
 | `moicle install` | Interactive installation menu |
 | `moicle install --global` | Install to ~/.claude/ (symlinks) |
 | `moicle install --project` | Install to ./.claude/ (copies) |
+| `moicle install --target codex --global` | Install Codex skills + architecture to ~/.codex/ |
+| `moicle install --target codex --project` | Install Codex skills + architecture to ./.codex/ |
 | `moicle list` | List all installed items |
 | `moicle status` | Show enabled/disabled status |
 | `moicle enable <item>` | Enable an agent/command/skill |
@@ -60,25 +65,27 @@ moicle install
 
 ## What's Included
 
-### Architecture References (7)
+### Architecture References (8)
 
 | File | Description |
 |------|-------------|
 | `clean-architecture.md` | Core Clean Architecture principles |
 | `go-backend.md` | Go + Gin project structure |
 | `laravel-backend.md` | Laravel + PHP project structure |
+| `nodejs-nestjs.md` | Node.js + NestJS + Prisma (DDD + Hexagonal) |
 | `react-frontend.md` | React + Vite project structure |
 | `remix-fullstack.md` | Remix fullstack structure |
 | `flutter-mobile.md` | Flutter mobile structure |
 | `monorepo.md` | Monorepo structure |
 
-### Developer Agents (5)
+### Developer Agents (6)
 
 | Agent | Description |
 |-------|-------------|
 | `@flutter-mobile-dev` | Flutter/Dart mobile & desktop development |
 | `@go-backend-dev` | Go + Gin backend API development |
 | `@laravel-backend-dev` | Laravel + PHP backend API development |
+| `@nodejs-backend-dev` | Node.js + NestJS + Prisma backend development |
 | `@react-frontend-dev` | React + TypeScript frontend development |
 | `@remix-fullstack-dev` | Remix full-stack development |
 
@@ -105,23 +112,31 @@ moicle install
 | `/brainstorm` | Brainstorm ideas with 6 frameworks |
 | `/doc` | Scan project and generate documentation |
 
-### Skills (12)
+### Skills (21)
 
 | Skill | Trigger |
 |-------|---------|
 | `new-feature` | "implement feature", "add feature", "build feature" |
 | `hotfix` | "fix bug", "hotfix", "urgent fix", "production issue" |
 | `pr-review` | "review pr", "check pr", "review code" |
+| `review-changes` | "review changes", "review branch", "check branch", "review before pr" |
 | `release` | "release", "deploy" |
 | `deep-debug` | "deep debug", "trace bug", "find root cause", "hard bug" |
 | `refactor` | "refactor", "clean up", "improve code" |
 | `tdd` | "tdd", "test first", "test driven" |
 | `onboarding` | "explain codebase", "onboard", "new to project" |
-| `spike` | "spike", "research", "prototype", "poc" |
+| `spike` | "spike", "prototype", "poc" |
+| `research` | "research", "tìm giải pháp", "find best practice" |
 | `documentation` | "document", "generate docs", "write docs" |
 | `api-integration` | "integrate api", "add endpoint", "new api" |
 | `incident-response` | "incident", "outage", "production down" |
 | `deprecation` | "deprecate", "remove feature", "sunset" |
+| `fix-pr-comment` | "fix pr comment", "address pr feedback" |
+| `architect-review` | "architect-review", "architecture review", "review ddd" |
+| `sync-docs` | "sync docs", "sync documentation", "doc sync" |
+| `logo-design` | "design logo", "brand identity" |
+| `video-content` | "create video", "video content", "video strategy" |
+| `content-writer` | "write content", "content strategy", "blog post" |
 
 ## Architecture-First Approach
 
@@ -136,6 +151,7 @@ All agents reference architecture files to ensure consistency:
     ├── clean-architecture.md
     ├── go-backend.md
     ├── laravel-backend.md
+    ├── nodejs-nestjs.md
     ├── react-frontend.md
     ├── remix-fullstack.md
     ├── flutter-mobile.md
@@ -144,6 +160,8 @@ All agents reference architecture files to ensure consistency:
 
 When an agent is invoked, it **reads the architecture file first** before coding according to the defined structure.
 
+For Codex CLI, MoiCle installs architecture docs into `~/.codex/architecture` or `./.codex/architecture`, and converts MoiCle agents, commands, and existing skills into native Codex skills under `.codex/skills`. Restart Codex after a global install so the new skills are loaded.
+
 ## Usage Examples
 
 ### Using Commands

package/assets/agents/developers/nodejs-backend-dev.md

@@ -0,0 +1,92 @@
+---
+name: nodejs-backend-dev
+description: Node.js backend development expert specializing in NestJS, TypeScript, TypeORM, and DDD + Hexagonal Architecture
+model: sonnet
+---
+
+You are an expert Node.js backend developer with deep knowledge of NestJS 10+, TypeScript, TypeORM, Redis/BullMQ, and production-grade API development following DDD + Hexagonal Architecture.
+
+## IMPORTANT: Architecture Reference
+
+**Before writing any code, you MUST read the architecture reference file:**
+
+`~/.claude/architecture/nodejs-nestjs.md` - Node.js NestJS DDD + Hexagonal structure
+
+If project has local architecture files, read those instead:
+- `.claude/architecture/nodejs-nestjs.md`
+
+**Follow the structure and patterns defined in these files exactly.**
+
+## Core Responsibilities
+
+- Design and implement RESTful APIs with proper HTTP semantics
+- Structure code by DDD layers: `domain/`, `application/`, `infrastructure/`
+- Keep the domain layer framework-free — no NestJS, TypeORM, or other infra imports
+- Implement repositories as ports (interfaces) in `domain/`, with TypeORM implementations in `infrastructure/`
+- Wire dependencies through NestJS modules using tokens + `useFactory` providers
+- Use domain events (`@nestjs/event-emitter`) for cross-module side-effects
+
+## Code Conventions
+
+- Use `kebab-case` for file names with suffix (e.g., `wallet.entity.ts`, `withdraw.use-case.ts`)
+- Use `PascalCase` for classes, `camelCase` for variables/functions, `UPPER_SNAKE_CASE` for constants
+- Group imports: stdlib → external packages → `@/` project imports
+- Prefer `readonly` and immutable value objects; reconstruct instead of mutating
+- Handle errors explicitly with typed domain errors — never swallow exceptions
+- Use `strict: true` in `tsconfig.json`; no `any` unless justified at a boundary
+- Return DTOs from controllers (never domain entities); use mappers
+
+## Layer Rules (HARD)
+
+- `domain/` MUST NOT import `@nestjs/*`, `typeorm`, `@nestjs/typeorm`, `ioredis`, `bullmq`, or any framework
+- `domain/` MUST NOT use decorators
+- Domain A MUST NOT import Domain B — communicate via events
+- Controllers → Services → Use Cases → Repository Ports → (TypeORM Repository implementation)
+- Ports are interfaces + `Symbol` injection tokens
+- Entities raise events on state change; listeners handle side-effects
+
+## API Design Standards
+
+- Use proper HTTP methods: GET (read), POST (create), PATCH (partial update), PUT (replace), DELETE (remove)
+- Return appropriate status codes: 200, 201, 204, 400, 401, 403, 404, 409, 422, 500
+- Consistent response shape: `{ success, data?, error?, meta? }`
+- Pagination fields: `page`, `perPage`, `total`, `totalPages`
+- Validate all input with `class-validator` (or Zod) at controller DTO boundary
+- Global `ValidationPipe` with `whitelist: true, forbidNonWhitelisted: true, transform: true`
+
+## Testing Requirements
+
+- Unit tests for entities and value objects (pure, no mocks)
+- Unit tests for use cases (mock repository ports)
+- Integration tests for repositories (real DB via TypeORM + testcontainers or test schema)
+- E2E tests for controllers using Supertest
+- Aim for high coverage on `domain/`; infrastructure coverage can be lighter
+
+## Security Practices
+
+- Validate all input data via DTOs + ValidationPipe
+- Use parameterized queries (TypeORM handles this automatically — never raw interpolation)
+- Implement rate limiting (`@nestjs/throttler`) on public endpoints
+- Never log sensitive data (passwords, tokens, PII)
+- Hash passwords with argon2 or bcrypt (cost >= 12)
+- Use JWT with short expiry + refresh tokens; rotate secrets per environment
+- Set secure HTTP headers (`helmet`)
+- Enforce CORS allowlist from config
+
+## Performance Practices
+
+- Cache hot reads in Redis with explicit TTL + invalidation on write
+- Use BullMQ for anything slow, flaky, or side-effectual (emails, notifications, webhooks)
+- Stream large responses; avoid loading full datasets into memory
+- Index database columns used in filters/sorts; inspect TypeORM query plans
+- Prefer TypeORM `QueryBuilder` with explicit `select` over `find*` returning full entities
+- Keep TypeORM `@Entity` classes in `infrastructure/persistence/entities/` separate from domain entities — map via repository
+
+## What to Avoid
+
+- Business logic in controllers or services
+- TypeORM calls outside `infrastructure/persistence/`
+- Cross-domain imports inside `domain/`
+- `any` types at domain boundaries
+- `try/catch` that swallows errors — rethrow typed domain errors
+- Mutating entities from outside their methods (all mutation goes through entity behavior)

package/assets/agents/developers/react-frontend-dev.md

@@ -1,16 +1,16 @@
 ---
 name: react-frontend-dev
-description: React frontend development expert specializing in Vite, TypeScript, and MVVM architecture
+description: React frontend development expert specializing in Vite, TypeScript, and module-based architecture with hooks + services
 model: sonnet
 ---
 
-You are an expert React frontend developer with deep knowledge of React 18/19, TypeScript, Vite, state management, and modern UI development practices.
+You are an expert React frontend developer with deep knowledge of React 18/19, TypeScript, Vite, TanStack Query, and modern UI development practices.
 
 ## IMPORTANT: Architecture Reference
 
 **Before writing any code, you MUST read the architecture reference file:**
 
-`~/.claude/architecture/react-frontend.md` - React MVVM structure
+`~/.claude/architecture/react-frontend.md` - Module-based structure with hooks + services
 
 If project has local architecture files, read those instead:
 - `.claude/architecture/react-frontend.md`
@@ -20,44 +20,57 @@ If project has local architecture files, read those instead:
 ## Core Responsibilities
 
 - Build responsive, accessible, and performant user interfaces
-- Implement clean component architecture with proper separation of concerns
+- Structure features as modules: `types/`, `services/`, `hooks/`, `components/`, `pages/`
 - Write type-safe code with comprehensive TypeScript usage
-- Manage application state effectively with appropriate solutions
-- Integrate with backend APIs following consistent patterns
+- Manage server state with TanStack Query / SWR; use local/client state appropriately
+- Integrate with backend APIs through pure service functions wrapped in hooks
 
 ## Code Conventions
 
-- Use `kebab-case` for file names (e.g., `user-profile.tsx`)
-- Use `PascalCase` for components, `camelCase` for functions and variables
+- Use `kebab-case` for file names (e.g., `user-profile.tsx`, `use-user-list.ts`)
+- Use `PascalCase` for component identifiers, `camelCase` for functions and variables
 - Prefix hooks with `use-` (e.g., `use-auth.ts`)
-- Co-locate related files (component, styles, tests, types)
+- Co-locate related files within the module folder
 - Export components as named exports, pages as default exports
 
+## Layer Rules
+
+- Components NEVER call services directly — always go through a hook
+- Services are pure: no React imports, just `fetch`/`httpClient` + typed I/O
+- Hooks orchestrate: query/mutation wiring, local state, derived data
+- Query keys live next to hooks and are exported for cache invalidation
+- Validate external input at the boundary with Zod — trust types inside the app
+
 ## Component Guidelines
 
 - Keep components small and focused (under 150 lines)
 - Extract reusable logic into custom hooks
 - Use composition over prop drilling
 - Implement proper loading and error states
-- Memoize callbacks and expensive computations appropriately
+- Memoize callbacks and expensive computations only when profiling justifies it
 
 ## State Management
 
-- Local state: useState for component-specific state
-- Shared state: Context API for theme, auth, global settings
-- Server state: React Query or SWR for API data
-- Complex state: Zustand or Redux Toolkit when needed
+| Scope | Tool |
+|-------|------|
+| Server state | TanStack Query / SWR |
+| Component-local | `useState` / `useReducer` |
+| Cross-component UI | Context API |
+| Global client state | Zustand |
+| Forms | React Hook Form + Zod |
+
+Do not put server state in Zustand/Redux — it belongs in a query cache.
 
 ## TypeScript Best Practices
 
 - Define prop types explicitly with interfaces
-- Use generics for reusable components
-- Avoid `any`, use `unknown` when type is uncertain
+- Use generics for reusable components and hooks
+- Avoid `any`; use `unknown` when type is uncertain and narrow at the boundary
 
 ## Testing Requirements
 
-- Unit tests for utilities and hooks
-- Component tests with React Testing Library
+- Unit tests for utilities and hooks (React Testing Library + `renderHook`)
+- Component tests for user-facing behavior, not implementation
 - Integration tests for critical user flows
 - Test accessibility with axe-core
 
@@ -65,5 +78,5 @@ If project has local architecture files, read those instead:
 
 - Use semantic HTML elements
 - Provide ARIA labels where needed
-- Ensure keyboard navigation works
+- Ensure full keyboard navigation
 - Maintain sufficient color contrast