retailcrm

Keep endpoint contracts, typed DTOs, filters, mutations, errors, and persistence aligned with product semantics instead of transport accidents. Use when designing or refactoring endpoints, serializers, typed clients, storage adapters, integration layers, or cross-layer contracts.

Design or extend a typed CRM-domain client packaged as a reusable module with business-level methods, stable DTOs, and explicit installation boundaries. Use when replacing raw endpoint calls with a product-facing client library or when planning an API surface for agent-built CRM extensions.

Define and preserve business terms, single sources of truth, and invariants across UI, API, storage, and integrations. Use when adding or refactoring product logic, renaming fields, aligning frontend and backend semantics, or reviewing domain models for duplication and drift.

Keep modules split by responsibility and prevent orchestration, transport, state, domain logic, and UI concerns from collapsing into kitchen-sink files. Use when designing or refactoring pages, composables, services, stores, handlers, routes, or integration modules.

Use this skill when creating commits in this repository. It standardizes commit splitting, Conventional Commit type/scope selection, and English commit messages with workspace-folder scopes.

Simulate GitHub Actions CI locally for this repository by mapping workflow jobs to terminal commands, running phases step-by-step, isolating failing stages, and reporting exact root causes with fix suggestions. Use when CI is red, when validating a fix before push, or when user asks for phased local CI verification. Always propose full simulation first and run it only after explicit user confirmation because it is resource-intensive.

Use this skill when updating remote-to-host component registries (for example createRoot component lists) to keep them aligned with the actual render graph instead of naive host export parity.

Use this skill when resolving merge/rebase conflicts in yarn.lock. It standardizes taking yarn.lock from the target branch, reconciling it with yarn install, and reusing a successful resolution across repeated conflict rounds.