added new partners

This commit is contained in:
Noah Zweben MacBook
2025-12-18 08:46:44 -08:00
parent 75b126f3ba
commit da8a738324
8 changed files with 108 additions and 15 deletions

View File

@@ -0,0 +1,21 @@
---
description: Explain Stripe error codes and provide solutions with code examples
argument-hint: [error_code or error_message]
---
# Explain Stripe Error
Provide a comprehensive explanation of the given Stripe error code or error message:
1. Accept the error code or full error message from the arguments
2. Explain in plain English what the error means
3. List common causes of this error
4. Provide specific solutions and handling recommendations
5. Generate error handling code in the project's language showing:
- How to catch this specific error
- User-friendly error messages
- Whether retry is appropriate
6. Mention related error codes the developer should be aware of
7. Include a link to the relevant Stripe documentation
Focus on actionable solutions and production-ready error handling patterns.

View File

@@ -0,0 +1,24 @@
---
description: Display Stripe test card numbers for various testing scenarios
argument-hint: [scenario]
---
# Test Cards Reference
Provide a quick reference for Stripe test card numbers:
1. If a scenario argument is provided (e.g., "declined", "3dsecure", "fraud"), show relevant test cards for that scenario
2. Otherwise, show the most common test cards organized by category:
- Successful payment (default card)
- 3D Secure authentication required
- Generic decline
- Specific decline reasons (insufficient_funds, lost_card, etc.)
3. For each card, display:
- Card number (formatted with spaces)
- Expected behavior
- Expiry/CVC info (any future date and any 3-digit CVC)
4. Use clear visual indicators (✓ for success, ⚠️ for auth required, ✗ for decline)
5. Mention that these only work in test mode
6. Provide link to full testing documentation: https://docs.stripe.com/testing.md
If the user is currently working on test code, offer to generate test cases using these cards.