stripe.
32 skills across 7 repos
- 100/100
check-link-wallet
Reads the connected Link account, the cards and bank accounts saved in its wallet, its saved shipping addresses, and the status of existing spend requests. Use when the user asks which Link account is connected, what payment methods or addresses Link has saved, or whether a Link purchase has been approved yet.
- 100/100
complete-link-purchase
Buys something on a merchant site with a Link wallet by asking the user to authorize a one-time virtual card, then retrieving the credential and entering it at checkout. Use when the user asks to buy something, pay for something, check out, or use their Link wallet on a merchant site.
- 100/100
create-payment-credential
|
- 100/100
financial-insights
|
- 100/100
use-link-identity
Use Link CLI's identity commands when a service requests a Link Agent Attestation Token (AAT) or signed user claims such as email. Covers acquiring and managing attestations, obtaining identity credentials, and presenting selected claims to a verifier through an HTTP client or browser automation.
- 100/100
compose-tests
Use when writing Compose UI tests in stripe-android — covers composeRule setup, Robolectric annotations, node assertions, and test tag patterns
- 100/100
delegate-low-reasoning-work
Use when running routine Gradle tests, builds, lint, formatting, generated-output checks, or verbose output collection in stripe-android. Delegate independent low-judgment work to a low-cost subagent to preserve the main context.
- 100/100
fixing-flakes
Reproduce, diagnose, and fix flaky stripe-android tests with focused, repeated validation and evidence-driven synchronization or determinism fixes. Use for intermittent unit, coroutine, Robolectric, Compose, screenshot, instrumentation, Gradle Managed Device, PaymentSheet E2E, Chrome, WebView, UiAutomator, or Espresso failures, while ensuring temporary ShampooRule edits never enter commits or pull requests.
- 100/100
network-tests
Use when writing NetworkRule integration tests in stripe-android — covers testBodyFromFile, inline JSON modification, request matchers, and fixture patterns
- 100/100
parameterized-tests
Use when writing, converting, or reviewing parameterized JVM, Robolectric, instrumentation, or Paparazzi tests in stripe-android. Covers TestParameterInjector runners, source-set dependencies, method versus class parameters, value providers, case matrices, and stable test names.
- 100/100
screenshot-tests
Use when writing or running Paparazzi screenshot tests in stripe-android — covers PaparazziRule setup, recording/verifying commands, and test structure
- 100/100
write-unit-tests
Use when writing or structuring unit tests or fake test implementations in stripe-android — covers scenarios, Turbine interaction tracking and Flow testing, and Truth assertions
- 100/100
add-native-feature
Step-by-step guide for adding features requiring JS-to-native bridge communication in the Stripe React Native SDK. Covers TypeScript types, Android Kotlin, iOS Swift, event emitters, bidirectional callbacks, and native module specs.
- 100/100
deflake-test
Reproduce, diagnose, fix, and stress-verify a suspected flaky unit, integration, or Maestro E2E test. Use when asked to repeat one focused test until it fails or establish a consecutive-pass threshold, not for ordinary one-off failures or broad suite validation.