Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

implement-feature

Étoiles0

Forks0

Mis à jour25 mai 2026 à 14:40

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

kimhongzhang323

kimhongzhang323/PaymentGateway

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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

Implement Feature

Disciplined workflow for adding functionality to the KimPay payment gateway.

Before writing code

Confirm there is a spec (docs/superpowers/specs/) and plan (docs/superpowers/plans/). If not, brainstorm and plan first — do not improvise a payment feature.
Identify which module each change belongs to (see .claude/rules/architecture-principles.md):
- Entity/enum → payment-domain
- Business logic / repository / infra interface → payment-core
- Controller / security / transport impl / config → payment-api
- Shared utility (crypto, masking) → payment-common
Check the relevant rules: security.md, api-design.md, testing-strategy.md, path-scoped/backend/database.md.

Implementation loop (TDD, per task)

Write the failing test (unit first; integration only where wiring matters).
Run it — confirm it fails for the expected reason.
Write the minimal code to pass. Constructor injection, records for DTOs, BigDecimal for money.
Run the test — confirm green. Run the module suite.
Commit with a conventional message (feat:, fix:, test:...).

Payment-specific checklist

Money uses BigDecimal; currency validated as 3-letter ISO.
Mutating endpoint authenticated; owner-scoped; supports idempotency.
No PAN/secret/PII logged; sensitive fields encrypted at rest.
State transitions go through entity methods, guarded against illegal moves.
Concurrency on balances protected by Redisson lock + DB pessimistic lock.
DTOs validated at the boundary; errors return the { code, message } envelope.
New error conditions added to the ErrorCode enum.
Prod Flyway migration written; entity mapping matches schema.

Done means

All new tests pass, the full ./mvnw test suite is green, the change is committed, and any new architectural decision is recorded in .claude/docs/decision-log.md.

Plus depuis ce dépôt

même dépôt

code-review

kimhongzhang323/PaymentGateway

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

2026-05-250

deploy

kimhongzhang323/PaymentGateway

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

2026-05-250

fix-bug

kimhongzhang323/PaymentGateway

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

2026-05-250

refactor

kimhongzhang323/PaymentGateway

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

2026-05-250

write-tests

kimhongzhang323/PaymentGateway

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

2026-05-250

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

Implement Feature

Disciplined workflow for adding functionality to the KimPay payment gateway.

Before writing code

Confirm there is a spec (docs/superpowers/specs/) and plan (docs/superpowers/plans/). If not, brainstorm and plan first — do not improvise a payment feature.
Identify which module each change belongs to (see .claude/rules/architecture-principles.md):
- Entity/enum → payment-domain
- Business logic / repository / infra interface → payment-core
- Controller / security / transport impl / config → payment-api
- Shared utility (crypto, masking) → payment-common
Check the relevant rules: security.md, api-design.md, testing-strategy.md, path-scoped/backend/database.md.

Implementation loop (TDD, per task)

Write the failing test (unit first; integration only where wiring matters).
Run it — confirm it fails for the expected reason.
Write the minimal code to pass. Constructor injection, records for DTOs, BigDecimal for money.
Run the test — confirm green. Run the module suite.
Commit with a conventional message (feat:, fix:, test:...).

Payment-specific checklist

Money uses BigDecimal; currency validated as 3-letter ISO.
Mutating endpoint authenticated; owner-scoped; supports idempotency.
No PAN/secret/PII logged; sensitive fields encrypted at rest.
State transitions go through entity methods, guarded against illegal moves.
Concurrency on balances protected by Redisson lock + DB pessimistic lock.
DTOs validated at the boundary; errors return the { code, message } envelope.
New error conditions added to the ErrorCode enum.
Prod Flyway migration written; entity mapping matches schema.

Done means

All new tests pass, the full ./mvnw test suite is green, the change is committed, and any new architectural decision is recorded in .claude/docs/decision-log.md.