kimhongzhang323

Use when reviewing a KimPay change or PR - applies a payment-gateway-specific checklist covering correctness, security, concurrency, and module hygiene.

Use when building, packaging, or deploying KimPay - covers the build, container image, required environment/secrets, migrations, and health verification.

Use when investigating a bug, test failure, or unexpected behavior in KimPay - enforces root-cause analysis and a regression test before any fix.

Use when adding a new feature or endpoint to KimPay - guides spec-driven, TDD implementation that respects module boundaries and payment security rules.

Use when restructuring KimPay code without changing behavior - enforces green-tests-before-and-after and respect for module boundaries.

Use when adding or improving test coverage for KimPay - guides choosing the right test level and writing meaningful payment/concurrency/security tests.

Use before merging a feature branch. Runs through the Atrium-specific checklist.

Use when creating a new UI component for Atrium. Enforces folder structure, naming, server-first defaults, and design-token usage.

Use when a page feels slow or LCP is poor. Walks through the Next.js 16 performance checklist for Atrium.

Use when generating, validating, or fixing Javadoc across TraceGraph modules. Triggers on user requests like "generate javadoc", "fix javadoc warnings", "publish docs", or after a public API change.

Use when bumping the project version (e.g. 0.1.0-SNAPSHOT → 0.1.0, then → 0.2.0-SNAPSHOT) and updating CHANGELOG.md. Triggers on user requests like "cut a release", "bump to 0.x", "tag 0.x".