sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
security-test
Fast, continuous DevSecOps pipeline for Pull Requests and active branches. Runs SAST, SCA, and secrets detection to catch vulnerabilities before they merge.
session-report
Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
system-design-artifact-intake
Ingest a provided design artifact - screenshot, drawio, Mermaid, PlantUML, Excalidraw, slides, PDF, or IaC - into a reviewable fact sheet. Probes for embedded structure before vision, marks per-edge confidence, treats extracted text as data. Use when someone hands over a design to review.
system-design-building-blocks
Select infrastructure components by the constraint each removes: load balancers, caches and invalidation, queues and pub/sub, CDN, API gateway, rate limiting, consistent hashing. Use when choosing cache, queue, replica, or edge layers; defer engine tuning to the database category.
system-design-case-catalog
Answer classic system design problems as constraint-to-solution sketches and coach interview practice: URL shortener, rate limiter, news feed, chat, notification, autocomplete, crawler, unique id. Use for interview practice or naming the closest known shape for a new problem.
system-design-communication
Select how services talk: REST, gRPC, GraphQL, WebSocket, SSE, or webhook per hop, sync versus async per flow, service discovery mode, and DNS/edge routing. Use when choosing a protocol or API paradigm; defer REST contract detail (status codes, pagination, OpenAPI) to common-api-design.
system-design-data-architecture
Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation. Use when selecting a store, planning sharding, or fixing a data-tier bottleneck.
system-design-estimation
Compute defensible capacity numbers before architecture: average and peak QPS, storage growth, bandwidth, working-set memory, latency and availability budgets. Use when sizing a service, provisioning infrastructure, or checking that a design survives peak load.
system-design-integration-patterns
Choose distributed integration and evolution patterns by the constraint each removes: outbox, CQRS, event sourcing, saga orchestration or choreography, leader election, sidecar, anti-corruption layer, and strangler-fig migration. Use when services must stay consistent across a boundary.
system-design-interview-coaching
Runs a timed mock system design round as the interviewer, then scores it as the coach: seven phases on a 45-minute clock, one follow-up on the weakest area, Mermaid sketches in chat, a six-criterion 0-3 rubric with quoted evidence. Use for interview practice, prep, or grading a practice design.
system-design-methodology
Drives an interactive system design session: classifies depth, elicits scale/SLO/consistency inputs, computes capacity, then reveals components one by one, each justified by a constraint. Use when designing a system or running a design session; diagrams go through `common-architecture-diagramming`.
system-design-principles
Define module boundaries, dependency direction, data ownership, resilience, and distributed-system trade-offs. Use for architecture, service boundaries, coupling, scalability, or failure-cascade decisions; defer session facilitation to system-design-methodology.
system-design-resilience-ops
Make a design survivable and operable: eliminate single points of failure, pick failover topology, set RPO/RTO, define readiness signals and observability, choose a deployment and rollback strategy. Use when reviewing availability, planning DR, or deciding rollout mechanics.
system-design-review
Audit an existing or proposed architecture and return a scored verdict across nine axes, from requirements and capacity evidence to observability and rollout, then convert gaps into a prioritized roadmap. Use when reviewing a design doc, auditing a running system, or gating a design.
system-design-session
Run an interactive system design session that turns a product goal into a sized, justified architecture with diagrams, ADRs, a scorecard, and a machine-readable handoff.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
traceability-audit
Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.
uat-signoff
Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.
update-docs
Automated workflow to detect and fix missing documentation
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
zephyr-coverage-analysis
Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.
api-conventions
Mix 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-core-local-auth
Create and reuse a short-lived local mx-core owner session when UI or API verification encounters a login gate, redirect, 401, or AUTH_NOT_LOGGED_IN response. Use only against the local development database and remove the temporary session after verification.
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 Mix 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
Mix Space project Zod schema patterns. Apply when creating DTOs, validation schemas, or handling request validation.
ln-11-opportunity-evaluator
Evaluates new product opportunities through demand, channels and economics before committing to build.
ln-12-product-requirements-builder
Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only.
ln-13-interaction-design-builder
Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code.
ln-21-system-design-baseline-builder
Defines measurable architecture drivers and constraints before system design; edits architecture docs only.
ln-22-current-architecture-documenter
Documents current architecture from implementation evidence; does not propose a target or audit fitness.
ln-23-system-design-proposal-builder
Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.
ln-24-architecture-decision-recorder
Records one architecture decision with alternatives, consequences and status; does not design the whole system.
ln-25-architecture-diagram-builder
Creates evidence-backed current or target architecture diagrams; not UI design.
ln-26-architecture-migration-planner
Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.
ln-31-delivery-plan-builder
Builds dependency-ordered delivery plans from requirements and repository evidence; read-only.
ln-32-test-strategy-planner
Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.
ln-33-plan-reviewer
Reviews a concrete implementation plan for missing decisions, feasibility and risk before execution; read-only.
ln-41-surgical-change-implementer
Implements one scoped feature or fix through the smallest complete solution; not upgrades or performance tuning.
ln-42-dependency-upgrader
Upgrades dependencies in reversible batches with version-specific compatibility and regression checks.
ln-43-code-modernizer
Modernizes a bounded capability to reduce demonstrated maintenance cost; not routine upgrades or performance tuning.
Page 298 of 1681 · 84047 results
