contextos-agents 1.5.0

package/.agents/core/skills/interview-me/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: interview-me
+description: >
+  Interactive requirements elicitation skill. Interrogates ambiguous, complex, or high-blast-radius
+  tasks one focused question at a time before any plan or code is written.
+---
+
+# interview-me
+
+## Overview
+
+Structured requirements interrogation framework inspired by [addyosmani/agent-skills](https://github.com/addyosmani/agent-skills). Prevents wasted cycles by transforming vague user intents into crisp, unambiguous architectural constraints through single-question progressive interview loops.
+
+## When to Use
+
+Activate whenever:
+
+- User task has underspecified requirements, open UX decisions, or multiple viable architectural trade-offs.
+- A high-blast-radius change (database migrations, auth refactor, API contract change) is requested.
+- Explicitly triggered via `/spec`, `/interview`, or "ask me questions first".
+
+## Rules & Patterns
+
+### 1. The One-Question-At-A-Time Rule
+
+**Never overwhelm the user with a 10-point interrogation form.**
+
+- Ask **exactly ONE focused question** per turn (or at most two tightly-coupled binary options).
+- Provide the recommended option first with clear rationale: `"(Recommended) Option A because..."`.
+- Always allow write-in or clarification.
+
+### 2. The 4 Interrogation Dimensions
+
+Interrogate in this strict priority order:
+
+1. **Business Outcome & Invariants**:
+   - What core problem does this solve?
+   - What behavior is strictly forbidden?
+2. **Scope Boundaries (In vs Out)**:
+   - What must be delivered in this atomic slice?
+   - What is explicitly deferred to later?
+3. **Technical Constraints**:
+   - Versions, libraries, database engines, backwards compatibility requirements.
+4. **Edge Cases & Failure Modes**:
+   - What happens on network disconnect, empty response, or unauthorized token?
+
+### 3. Progressive Synthesis
+
+After each user answer:
+
+- Acknowledge the decision and update the mental model.
+- If more critical decisions remain, ask the next question.
+- Once 2–4 key questions are resolved, synthesize the formal Feature Spec and transition to `engineering-workflow` (`[PHASE: Plan]`).
+
+---
+
+## Code Examples
+
+### Interactive Interview Turn Example
+
+```markdown
+**Question 1 of 3 (Authentication Strategy)**
+
+Before implementing the API authentication layer, we need to align on session storage:
+
+1. **(Recommended) HTTP-only Secure Cookies with Refresh Tokens**:
+   - *Why*: Immune to XSS token theft, standard for web dashboards.
+2. **Bearer Token in Authorization Header**:
+   - *Why*: Ideal if this API will also be consumed by mobile apps or third-party CLI tools.
+
+Which model fits your architecture best?
+```
+
+---
+
+## Validation Checklist
+
+- [ ] Question addresses an actual ambiguity (never ask about obvious defaults).
+- [ ] Exactly one question (or two tightly coupled choices) asked.
+- [ ] Recommendation provided with clear engineering justification.
+- [ ] User response incorporated into the final spec before coding.
+
+---
+
+## Common Mistakes
+
+- **Asking obvious questions**: Asking "Do you want error handling?" instead of making a sensible senior default.
+- **Interrogation bombardment**: Dumping a list of 8 open-ended questions in a single wall of text.
+- **Ignoring user answers**: Asking a question, receiving an answer, and then implementing something else.
+
+---
+
+## Integration Notes
+
+- Runs at the start of `engineering-workflow` Phase 1 (`/spec`).
+- Interacts with `gstack-roles` (`[ROLE: Product Manager]` or `[ROLE: Architect]`).
+- Hands off to `ponytail-mindset` once scope is defined.

package/.agents/core/skills/interview-me/VALIDATION.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "rules_followed": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "rules_followed"
+  ]
+}

package/.agents/core/skills/interview-me/skill.yaml

@@ -0,0 +1,8 @@
+name: interview-me
+description: Interactive requirements elicitation skill. Interrogates ambiguous, complex, or high-blast-radius tasks one focused question at a time before any plan or code is written.
+tags:
+  - workflow
+  - requirements
+  - planning
+  - interview
+version: 1.0.0

package/.agents/core/skills/microservices/EXAMPLES.md

@@ -0,0 +1,38 @@
+# microservices Examples — Anti-patterns vs ContextOS Standard
+
+## Example 1: Inter-service Communication
+
+### Anti-pattern: Synchronous HTTP Call Chains (The Distributed Monolith)
+
+```text
+User -> OrderService (HTTP) -> InventoryService (HTTP) -> PaymentService (HTTP) -> EmailService (HTTP)
+Problem: High latency, 99.9% availability compounding to 96% overall availability, cascading failure.
+```
+
+### Best practice: ContextOS Standard (Asynchronous Event Choreography)
+
+```text
+User -> OrderService (creates order with status 'PENDING')
+OrderService publishes 'OrderPlaced' event to Event Broker (Kafka/RabbitMQ)
+  ├── InventoryService consumes 'OrderPlaced' -> Reserves stock
+  ├── PaymentService consumes 'OrderPlaced' -> Charges customer
+  └── NotificationService consumes 'PaymentProcessed' -> Sends confirmation email
+```
+
+---
+
+## Example 2: Database Architecture
+
+### Anti-pattern: Shared Database Across Multiple Microservices
+
+```text
+BAD: OrderService and UserService both directly read and write to the same 'users' table.
+Schema migrations in UserService immediately break OrderService.
+```
+
+### Best practice: ContextOS Standard (Database-per-Service)
+
+```text
+GOOD: UserService owns user data. OrderService maintains a local read-model (denormalized user info)
+synchronized via 'UserUpdated' events. Each service can migrate and scale independently.
+```

package/.agents/core/skills/microservices/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: Microservices
+description: >
+  ContextOS skill for Microservices
+---
+
+# Microservices
+
+## Overview
+
+Distributed systems architecture standard. Enforces bounded context isolation, asynchronous event-driven messaging (Kafka, RabbitMQ), Saga distributed transactions, API gateways, and outbox patterns.
+
+## When to Use
+
+Activate when decomposing monoliths into independent services, designing inter-service communications, or building scalable distributed systems.
+
+## Rules & Patterns
+<!-- Source: microservices.md -->
+
+## Microservices — Architecture Guide
+
+## When to Use Microservices
+
+**Use when:**
+
+- Team > 10 engineers working on the same product
+- Independent deployment of components is critical
+- Different components have different scaling needs
+- Different components need different tech stacks
+
+**Don't use when:**
+
+- Small team (< 5 engineers)
+- MVP or prototype
+- No operational expertise (monitoring, tracing, deployment)
+- Tight coupling between components
+
+## Core Principles
+
+### 1. Single Responsibility
+
+Each service does ONE thing well.
+
+### 2. Own Your Data
+
+Each service has its own database. No shared databases.
+
+### 3. API Contracts
+
+Services communicate through well-defined APIs. Internal implementation is hidden.
+
+### 4. Autonomous Deployment
+
+Each service can be deployed independently.
+
+## Communication Patterns
+
+### Synchronous (REST/gRPC)
+
+- **When**: Request needs immediate response
+- **Tools**: REST (HTTP), gRPC (high-performance)
+- **Risk**: Cascading failures, latency accumulation
+
+### Asynchronous (Events/Messages)
+
+- **When**: Eventual consistency is acceptable
+- **Tools**: Kafka, RabbitMQ, Redis Streams, AWS SQS
+- **Benefit**: Loose coupling, resilience
+
+### Saga Pattern (Distributed Transactions)
+
+```
+Order Service → Payment Service → Inventory Service → Shipping Service
+      ↓ (failure)
+Compensating transactions reverse each step
+```
+
+1. **Choreography (Event-Driven)**: Each service emits events, downstream services listen and react. Best for simple flows (≤ 3 steps) where a central coordinator adds unnecessary coupling.
+2. **Orchestration (State Machine)**: A dedicated Saga Orchestrator controls the flow and explicitly triggers compensating transactions on failure (e.g., `RefundPayment`, `ReleaseInventoryReservation`). Mandatory for complex multi-step workflows.
+
+### Dead Letter Queues (DLQ) & Poison Pill Handling
+
+- **Never retry infinitely**: Set max retries (e.g. 3) with exponential backoff and jitter.
+- After max retries, route failed messages to a **Dead Letter Queue (DLQ)** with error metadata.
+- Provide alerting on DLQ depth and an admin CLI/script to replay DLQ messages.
+
+## CQRS (Command Query Responsibility Segregation)
+
+Separate read and write models:
+
+```
+Command (Write) → Write Model → Event Store → Projections → Read Model → Query (Read)
+```
+
+**When**: Read patterns differ significantly from write patterns.
+
+## Event Sourcing
+
+Store events, not state:
+
+```
+UserCreated → EmailUpdated → RoleChanged → PasswordReset
+```
+
+Current state = replay all events. Full audit trail.
+
+## Service Boundaries
+
+### Bounded Contexts (from DDD)
+
+- Identify domain boundaries
+- Each service maps to a bounded context
+- Shared language within the context, translation at boundaries
+
+### Anti-Corruption Layer
+
+When integrating with legacy or external systems, create an adapter that translates between models.
+
+## Operational Concerns
+
+### Observability (The Three Pillars)
+
+1. **Logs** — structured JSON, correlated by request ID
+2. **Metrics** — latency, error rate, throughput (RED)
+3. **Traces** — distributed tracing across services (Jaeger, Zipkin)
+
+### Resilience
+
+- **Circuit Breaker** — stop calling failing services
+- **Retry with Backoff** — exponential backoff + jitter
+- **Timeout** — every call has a timeout
+- **Bulkhead** — isolate failures
+
+### Deployment
+
+- **Containers** — Docker for consistency
+- **Orchestration** — Kubernetes for production
+- **CI/CD** — independent pipelines per service
+- **Blue-Green / Canary** — safe rollouts
+
+## Anti-Patterns
+
+- [FAIL] Distributed monolith — services that can't deploy independently
+- [FAIL] Shared database — defeats the purpose
+- [FAIL] Synchronous chains — A calls B calls C calls D
+- [FAIL] No versioning — breaking API changes
+- [FAIL] Premature microservices — start with a modular monolith
+
+
+## Code Examples
+
+See `EXAMPLES.md` for detailed code examples.
+
+## Validation Checklist
+
+What to verify during the review phase before completing the task.
+
+## Common Mistakes
+
+Anti-patterns and things to explicitly avoid. See `TROUBLESHOOTING.md`.
+
+## Integration Notes
+
+How this skill interacts with other skills.

package/.agents/core/skills/microservices/TROUBLESHOOTING.md

@@ -0,0 +1,19 @@
+# microservices Troubleshooting & Common Mistakes
+
+## 1. Missing Consumer Idempotency
+
+- **Symptom**: Users charged twice or duplicate records created when events are re-delivered.
+- **Root Cause**: Message brokers guarantee at-least-once delivery; network retries re-send events.
+- **Fix**: Store processed message/event IDs in a deduplication table with unique constraint.
+
+## 2. Circular Service Dependencies
+
+- **Symptom**: Service A cannot boot or operate without Service B, and Service B depends on Service A.
+- **Root Cause**: Improper domain boundaries and coupled synchronous dependencies.
+- **Fix**: Invert dependency using domain events or introduce a composite BFF/Orchestrator.
+
+## 3. Distributed Tracing Blindness
+
+- **Symptom**: Impossible to diagnose which downstream microservice caused a 500 error or latency spike.
+- **Root Cause**: HTTP headers and event messages do not propagate correlation IDs.
+- **Fix**: Propagate X-Correlation-ID / traceparent across all HTTP requests and event headers.

package/.agents/core/skills/microservices/VALIDATION.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "rules_followed": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "rules_followed"
+  ]
+}

package/.agents/core/skills/microservices/microservices.md

@@ -0,0 +1,119 @@
+# Microservices — Architecture Guide
+
+## When to Use Microservices
+
+**Use when:**
+
+- Team > 10 engineers working on the same product
+- Independent deployment of components is critical
+- Different components have different scaling needs
+- Different components need different tech stacks
+
+**Don't use when:**
+
+- Small team (< 5 engineers)
+- MVP or prototype
+- No operational expertise (monitoring, tracing, deployment)
+- Tight coupling between components
+
+## Core Principles
+
+### 1. Single Responsibility
+
+Each service does ONE thing well.
+
+### 2. Own Your Data
+
+Each service has its own database. No shared databases.
+
+### 3. API Contracts
+
+Services communicate through well-defined APIs. Internal implementation is hidden.
+
+### 4. Autonomous Deployment
+
+Each service can be deployed independently.
+
+## Communication Patterns
+
+### Synchronous (REST/gRPC)
+
+- **When**: Request needs immediate response
+- **Tools**: REST (HTTP), gRPC (high-performance)
+- **Risk**: Cascading failures, latency accumulation
+
+### Asynchronous (Events/Messages)
+
+- **When**: Eventual consistency is acceptable
+- **Tools**: Kafka, RabbitMQ, Redis Streams, AWS SQS
+- **Benefit**: Loose coupling, resilience
+
+### Saga Pattern (Distributed Transactions)
+
+```
+Order Service → Payment Service → Inventory Service → Shipping Service
+      ↓ (failure)
+Compensating transactions reverse each step
+```
+
+## CQRS (Command Query Responsibility Segregation)
+
+Separate read and write models:
+
+```
+Command (Write) → Write Model → Event Store → Projections → Read Model → Query (Read)
+```
+
+**When**: Read patterns differ significantly from write patterns.
+
+## Event Sourcing
+
+Store events, not state:
+
+```
+UserCreated → EmailUpdated → RoleChanged → PasswordReset
+```
+
+Current state = replay all events. Full audit trail.
+
+## Service Boundaries
+
+### Bounded Contexts (from DDD)
+
+- Identify domain boundaries
+- Each service maps to a bounded context
+- Shared language within the context, translation at boundaries
+
+### Anti-Corruption Layer
+
+When integrating with legacy or external systems, create an adapter that translates between models.
+
+## Operational Concerns
+
+### Observability (The Three Pillars)
+
+1. **Logs** — structured JSON, correlated by request ID
+2. **Metrics** — latency, error rate, throughput (RED)
+3. **Traces** — distributed tracing across services (Jaeger, Zipkin)
+
+### Resilience
+
+- **Circuit Breaker** — stop calling failing services
+- **Retry with Backoff** — exponential backoff + jitter
+- **Timeout** — every call has a timeout
+- **Bulkhead** — isolate failures
+
+### Deployment
+
+- **Containers** — Docker for consistency
+- **Orchestration** — Kubernetes for production
+- **CI/CD** — independent pipelines per service
+- **Blue-Green / Canary** — safe rollouts
+
+## Anti-Patterns
+
+- [FAIL] Distributed monolith — services that can't deploy independently
+- [FAIL] Shared database — defeats the purpose
+- [FAIL] Synchronous chains — A calls B calls C calls D
+- [FAIL] No versioning — breaking API changes
+- [FAIL] Premature microservices — start with a modular monolith

package/.agents/core/skills/microservices/skill.yaml

@@ -0,0 +1,10 @@
+id: microservices
+name: Microservices
+category: architecture
+tags: [architecture, microservices, distributed, event-driven, cqrs]
+requires: [system-design]
+optional: [docker, security]
+conflicts: []
+weight: 6
+documents:
+  - microservices.md

package/.agents/core/skills/minimalist-design/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: minimalist-ui
+description: Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
+---
+
+# Protocol: Premium Utilitarian Minimalism UI Architect
+
+## Overview
+
+An advanced frontend engineering directive for generating highly refined, ultra-minimalist, "document-style" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends.
+
+## When to Use
+
+- When designing clean, editorial, or Notion-like document interfaces, workspaces, or notes apps.
+- When creating minimalist SaaS dashboards, personal essays, portfolios, or agency landing pages.
+- When asked for a "clean", "minimalist", "warm monochrome", or "flat bento-box" layout.
+
+## Rules & Patterns
+
+### 1. Absolute Negative Constraints (Banned Elements)
+
+The AI must strictly avoid the following generic web development defaults:
+
+- DO NOT use the "Inter", "Roboto", or "Open Sans" typefaces.
+- DO NOT use generic, thin-line icon libraries like "Lucide", "Feather", or standard "Heroicons".
+- DO NOT use Tailwind's default heavy drop shadows (e.g., `shadow-md`, `shadow-lg`, `shadow-xl`). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (< 0.05).
+- DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections).
+- DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).
+- DO NOT use `rounded-full` (pill shapes) for large containers, cards, or primary buttons.
+- DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives.
+- DO NOT use generic placeholder names like "John Doe", "Acme Corp", or "Lorem Ipsum". Use realistic, contextual content.
+- DO NOT use AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve". Write plain, specific language.
+
+### 2. Typographic Architecture
+
+The interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel.
+
+- **Primary Sans-Serif (Body, UI, Buttons):** Use clean, geometric, or system-native fonts with character (`'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif`).
+- **Editorial Serif (Hero Headings & Quotes):** (`'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif`). Apply tight tracking (`-0.02em` to `-0.04em`) and tight line-height (`1.1`).
+- **Monospace (Code, Keystrokes, Meta-data):** (`'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace`).
+- **Text Colors:** Body text must never be absolute black (`#000000`). Use off-black/charcoal (`#111111` or `#2F3437`) with a generous line-height of `1.6` for legibility. Secondary text should be muted gray (`#787774`).
+
+### 3. Color Palette (Warm Monochrome + Spot Pastels)
+
+Color is a scarce resource, utilized only for semantic meaning or subtle accents.
+
+- **Canvas / Background:** Pure White `#FFFFFF` or Warm Bone/Off-White `#F7F6F3` / `#FBFBFA`.
+- **Primary Surface (Cards):** `#FFFFFF` or `#F9F9F8`.
+- **Structural Borders / Dividers:** Ultra-light gray `#EAEAEA` or `rgba(0,0,0,0.06)`.
+- **Accent Colors:** Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds:
+  - Pale Red: `#FDEBEC` (Text: `#9F2F2D`)
+  - Pale Blue: `#E1F3FE` (Text: `#1F6C9F`)
+  - Pale Green: `#EDF3EC` (Text: `#346538`)
+  - Pale Yellow: `#FBF3DB` (Text: `#956400`)
+
+### 4. Component Specifications
+
+- **Bento Box Feature Grids:** Asymmetrical CSS Grid layouts. Cards have `border: 1px solid #EAEAEA`, crisp border-radius (`8px` to `12px` max), and generous internal padding (`24px` to `40px`).
+- **Primary Call-To-Action (Buttons):** Solid `#111111`, text `#FFFFFF`, radius `4px` to `6px`, no box-shadow. Micro-scale `transform: scale(0.98)` on active.
+- **Tags & Status Badges:** Pill-shaped (`rounded-full`), small typography (`text-xs`), uppercase with wide tracking (`0.05em`), pastel background.
+- **Accordions (FAQ):** Separated by `border-bottom: 1px solid #EAEAEA` without card boxes. Crisp `+` / `-` toggle icons.
+- **Keystroke Micro-UIs:** `<kbd className="border border-[#EAEAEA] rounded bg-[#F7F6F3] font-mono px-1.5 py-0.5 text-xs">`.
+
+### 5. Iconography & Imagery
+
+- **System Icons:** Phosphor Icons (Bold/Fill) or Radix UI Icons for crisp, technical strokes.
+- **Photography:** Desaturated images with warm tint and subtle grain overlay (`opacity: 0.04`).
+- **Depth:** Subtle ambient gradients (`radial-gradient` with warm tones at `opacity: 0.03`) or minimal geometric line patterns.
+
+### 6. Subtle Motion & Micro-Animations
+
+- **Scroll Entry:** Fade-in + `translateY(12px)` over 600ms via `IntersectionObserver`.
+- **Hover States:** Subtle card lift with ultra-diffuse shadow (`0 2px 8px rgba(0,0,0,0.04)`).
+- **Staggered Reveals:** Cascading delay (`calc(var(--index) * 80ms)`).
+
+## Code Examples
+
+```tsx
+export function BentoFeatureCard({ title, description, badge, tagColor = "blue" }: { title: string; description: string; badge: string; tagColor?: string }) {
+  return (
+    <div className="bg-[#FFFFFF] border border-[#EAEAEA] rounded-xl p-8 hover:shadow-[0_2px_8px_rgba(0,0,0,0.04)] transition-all duration-200">
+      <div className="flex items-center justify-between mb-4">
+        <span className="text-xs uppercase tracking-wider font-mono font-medium px-2.5 py-0.5 rounded-full bg-[#E1F3FE] text-[#1F6C9F]">
+          {badge}
+        </span>
+      </div>
+      <h3 className="font-serif text-2xl tracking-tight text-[#111111] mb-2">{title}</h3>
+      <p className="text-sm text-[#787774] leading-relaxed">{description}</p>
+    </div>
+  );
+}
+```
+
+## Validation Checklist
+
+- [ ] Macro-whitespace established with generous vertical section padding (`py-24` to `py-32`).
+- [ ] No pure black (`#000000`) for text or backgrounds.
+- [ ] Borders use crisp `1px solid #EAEAEA` or `rgba(0,0,0,0.06)`.
+- [ ] No generic AI buzzwords or emojis used in copy.
+- [ ] Typography uses editorial serif headers paired with clean sans-serif body.
+- [ ] Card corners constrained to crisp 8px-12px radius; no pill containers.
+
+## Common Mistakes
+
+- Using heavy saturated primary colors for hero backgrounds.
+- Adding default Tailwind drop-shadows (`shadow-lg`).
+- Cluttering interfaces with emojis instead of clean SVG icons.
+- Using default Inter or Roboto fonts without editorial contrast.
+
+## Integration Notes
+
+- Complements `ui-ux-pro` for color tokens and accessibility.
+- Integrates with `impeccable-design` for QA and anti-pattern enforcement.

package/.agents/core/skills/minimalist-design/VALIDATION.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "rules_followed": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "rules_followed"
+  ]
+}

package/.agents/core/skills/minimalist-design/skill.yaml

@@ -0,0 +1,8 @@
+name: minimalist-design
+description: Clean editorial-style interfaces with warm monochrome palettes and flat bento grids.
+tags:
+  - ui
+  - design
+  - minimalist
+  - editorial
+version: 1.0.0

package/.agents/core/skills/nestjs/EXAMPLES.md

@@ -0,0 +1,40 @@
+# nestjs Examples — Anti-patterns vs ContextOS Standard
+
+## Example 1: Input Validation and DTOs
+
+### Anti-pattern: Untyped Body or Manual Validation in Controller
+
+```typescript
+// BAD: No runtime validation, controller stuffed with business rules
+@Post('users')
+async create(@Body() body: any) {
+  if (!body.email || !body.email.includes('@')) {
+    throw new BadRequestException('Invalid email');
+  }
+  return this.usersService.create(body);
+}
+```
+
+### Best practice: ContextOS Standard (Class-Validator DTO + ValidationPipe)
+
+```typescript
+// GOOD: Declarative runtime validation with clean separation
+export class CreateUserDto {
+  @IsEmail({}, { message: 'A valid email is required' })
+  email: string;
+
+  @IsString()
+  @MinLength(8, { message: 'Password must be at least 8 characters long' })
+  password: string;
+}
+
+@Controller('users')
+export class UsersController {
+  constructor(private readonly usersService: UsersService) {}
+
+  @Post()
+  async create(@Body() dto: CreateUserDto) {
+    return this.usersService.create(dto);
+  }
+}
+```