auth9

Run E2E tests for Auth9 portal using Playwright with hybrid testing strategy.

Run tests, check logs, and troubleshoot Auth9 services in Docker and Kubernetes environments.

Run performance benchmarks for auth9-core API using hey load testing tool.

Execute scenario-based QA testing with browser automation, database validation, and automatic ticket creation for failures.

Reset Auth9 local Docker development environment to a clean state.

Rust coding conventions and patterns for auth9-core development.

Run tests and check coverage for Auth9 backend, frontend, and SDK with mock-based testing patterns.

Read the ticket document(s) under docs/ticket/, and verify the issue against the actual implementation. Classify as bug, false positive, or feature gap. For bugs, fix the code. For false positives, update QA docs. For feature gaps, fix in-place if small or create a Feature Request if large. Regardless of category, reset the environment using ./scripts/reset-docker.sh, then rerun QA testing. After testing confirms resolution, delete the ticket document(s). Use when a user asks to fix a ticket or resolve a QA failure.

Govern feature requests from docs/feature_request/ through a structured lifecycle: scan FR docs, produce implementation plans, execute changes, self-check closure, generate QA docs, execute QA testing, and clean up. Use when a user asks to implement a feature request, govern FRs, process feature requests, or says '治理 FR'. Also triggers when docs/feature_request/ contains unresolved documents.

Generate or update QA/security/UIUX test documentation after confirmed feature implementation plans or completed refactors. Use this skill AFTER plan approval or code completion to: (1) add new QA/security test docs for new behavior, and (2) run cross-doc impact analysis across docs/qa/, docs/security/, and docs/uiux/ to update stale steps, expectations, and security assertions. Triggers when users ask to create QA docs, update test docs after implementation, or sync QA/security/UIUX docs after behavior changes.

Govern and periodically remediate QA documentation quality across docs/qa, docs/security, and docs/uiux. Use when users ask to audit QA docs, run recurring documentation checks, fix doc drift after refactors, enforce scenario limits/checklists/UI entry visibility, or synchronize README/manifest/changelog consistency.

Execute unit-test alignment after large refactors or broad code changes. Trigger when the user explicitly uses the command "-- 对齐测试 --" or asks to align/fix tests after massive modifications. Run relevant unit tests, analyze failing test cases, update tests and/or implementation, and iterate until stable.

Run Auth9 gRPC regression tests by issuing grpcurl requests from inside the Docker Compose network (required when host-to-container ports are blocked), especially for the auth9-grpc-tls TLS endpoint.

Initialize a brand-new project from scratch with a default full-stack scaffold (Rust core + React Router 7 portal + Docker + Kubernetes). Use when a developer asks to bootstrap an empty repo or start a new project and no specific tech stack is requested.

End-to-end deployment workflow for this repo that gates on the latest GitHub Actions run, deploys with deploy/upgrade.sh to Kubernetes, monitors kubectl resources, troubleshoots failures (logs, code, IaC), and performs health checks. Use when the user asks to deploy or says “进行部署”, “发布”, “上线”, or requests a Kubernetes deployment/check.