Menu
Use when restructuring KimPay code without changing behavior - enforces green-tests-before-and-after and respect for module boundaries.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 adding or improving test coverage for KimPay - guides choosing the right test level and writing meaningful payment/concurrency/security tests.
| name | refactor |
| description | Use when restructuring KimPay code without changing behavior - enforces green-tests-before-and-after and respect for module boundaries. |
Improve structure without changing behavior. Behavior change is a feature, not a refactor — do that separately.
./mvnw test). If not, fix or characterize first — never refactor on red.refactor: message.architecture-principles.md): moving a class must not create an upward dependency (e.g. domain → core).@ConditionalOnMissingBean on a @Component → @Bean in a @Configuration.fix-bug (test + fix), then resume.