菜单
Strict TypeScript guidance for LifeOS backend (NestJS) and frontend (React). Use when creating or refactoring DTOs, domain/application types, API client types, generics, type guards, or when resolving TypeScript errors without weakening type safety.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.
API DTO and response contract rules for LifeOS backend/frontend compatibility. Use when adding or changing endpoints, request/response DTOs, error payloads, versioning decisions, or Swagger/OpenAPI documentation.
Authentication and ownership enforcement rules for LifeOS multi-user isolation. Use when creating or changing auth flows, guarded endpoints, user-scoped queries, or nested resource access checks.
Clean Architecture + DDD rules for this repo. Triggers: adding/refactoring code across src/domain|application|infrastructure, moving files between layers, creating ports/adapters/use-cases.
Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.
Repository documentation conventions for LifeOS. Use when creating or updating README, docs/*, architecture notes, API behavior notes, or implementation decisions that must remain clear for future contributors and agents.
| name | typescript |
| description | Strict TypeScript guidance for LifeOS backend (NestJS) and frontend (React). Use when creating or refactoring DTOs, domain/application types, API client types, generics, type guards, or when resolving TypeScript errors without weakening type safety. |
Definir tipos explícitos y estables entre backend y frontend sin usar atajos inseguros.
unknown y refinar con type guards.frontend/src/types o frontend/src/features/*/types).pending, completed, etc.).string | null) y evitar asumir valores.any salvo bloqueo temporal explícitamente comentado.as para ocultar errores de diseño de tipos.tsc/vitest y corregir sin relajar tipos.