api-conventions
MX Space API design conventions. Apply when writing controllers, API endpoints, or handling HTTP requests.
create-e2e-test
Create E2E test file for a specified module. Use when adding end-to-end tests for controllers or unit tests for services and repositories.
create-module
Create a new NestJS module with repository, service, controller, schema, and Drizzle table definition. Use when adding new feature modules, API endpoints, or business domains.
mx-migration-author
|
mx-pg-controller-migration
Use when verifying and porting an mx-core controller (Post/Note/Page/Comment/Category/etc.) after the MongoDB→PostgreSQL cutover, or when its data shape no longer matches what api-client and admin-vue3 expect. Triggers on "校验 controller"、"check controller"、"迁移 controller"、"修复迁移后的接口"、"data missing after PG migration"、"related/category 字段丢了" and similar.
mx-review
Review code for MX Space project conventions. Checks NestJS patterns, Drizzle ORM repositories, Zod schemas, API design, etc.
mxs-cli-ai-author
Use when an agent must inspect, draft, validate, edit, publish, unpublish, delete, or configure mx-space content through packages/cli or the mxs binary.
release-core
Use when releasing mx-core server (apps/core), @mx-space/api-client, or @mx-space/cli (mxs) — version bump, changelog, git tag, Docker build, GitHub Release, and Dokploy redeploy. Triggers on "发版", "release a new version", "cut a release", "bump version", "publish api-client", "publish cli", "release mxs".
run-test
Run tests. Supports running all tests, single file, or pattern-matched tests.
zod-patterns
MX Space project Zod schema patterns. Apply when creating DTOs, validation schemas, or handling request validation.