Required Plugins

Superpowers plugin: MUST be active for all work using this skill. Use throughout the entire build pipeline — design decisions, code generation, debugging, quality checks, and any task where it offers enhanced capabilities. If superpowers provides a better way to accomplish something, prefer it over the default approach.

API Error Handling

Implement comprehensive, standardized error response system for PHP REST APIs with consistent JSON envelopes, specific error message extraction, and SweetAlert2 integration.

Core Principles:

• Consistent JSON envelope across all endpoints
• Specific error messages extracted from all exception types
• Appropriate HTTP status codes for all error categories
• Machine-readable error codes for programmatic handling
• Human-readable messages for SweetAlert2 display
• Secure error handling (no stack traces in production)
• Comprehensive logging with request IDs
• CRITICAL: Always show error messages to users in SweetAlert (never silent failures)

Security Baseline (Required): Always load and apply the Vibe Security Skill for PHP API work. Do not leak sensitive data in responses or logs.

Cross-Platform: APIs deploy to Windows (dev), Ubuntu (staging), Debian (production), all running MySQL 8.x. Use utf8mb4_unicode_ci collation. Match file/directory case exactly in require paths (Linux is case-sensitive). Use forward slashes in paths.

See subdirectories for:

• references/ - Complete PHP classes (ApiResponse, ExceptionHandler, Exceptions)
• examples/ - Full endpoint implementation, frontend client

Response Envelope Standard

Success:

{
  "success": true,
  "data": {
    /* payload */
  },
  "message": "Optional success message",
  "meta": {
    "timestamp": "2026-01-24T10:30:00Z",
    "request_id": "req_abc123"
  }
}

Error:

{
  "success": false,
  "message": "Human-readable error for SweetAlert2",
  "error": {
    "code": "ERROR_CODE",
    "type": "validation_error",
    "details": {
      /* field-specific errors */
    }
  },
  "meta": {
    "timestamp": "2026-01-24T10:30:00Z",
    "request_id": "req_abc123"
  }
}

HTTP Status Codes

ApiResponse Helper (Quick Reference)

See references/ApiResponse.php for complete implementation

// Success responses
ApiResponse::success($data, $message, $status);
ApiResponse::created($data, $message);

// Error responses
ApiResponse::error($message, $code, $status, $type, $details);
ApiResponse::validationError($errors, $message);
ApiResponse::notFound($resource, $identifier);
ApiResponse::unauthorized($message);
ApiResponse::forbidden($permission);
ApiResponse::conflict($message, $code);
ApiResponse::methodNotAllowed($allowedMethods);
ApiResponse::rateLimited($retryAfter);
ApiResponse::serverError($message);
ApiResponse::serviceUnavailable($message);

Exception Handler (Quick Reference)

See references/ExceptionHandler.php for complete implementation

Key Features:

• Extracts specific messages from PDOException
• Parses SQLSTATE 45000 (user-defined exceptions from triggers)
• Extracts constraint violation messages
• Handles deadlocks gracefully
• Logs all errors with request ID
• Hides stack traces in production

PDOException Parsing:

// SQLSTATE 45000: Business rule from trigger
// "SQLSTATE[45000]: <<1>>: 1644 Overpayment not allowed"
// Extracted: "Overpayment not allowed"

// SQLSTATE 23000: Duplicate entry
// "Duplicate entry 'john@example.com' for key 'uk_email'"
// Extracted: "A record with this Email already exists: 'john@example.com'"

// SQLSTATE 23000: Foreign key violation
// "Cannot delete or update a parent row..."
// Extracted: "Referenced Customer does not exist or cannot be deleted"

Custom Exception Classes

See references/CustomExceptions.php for all classes

// Validation (422)
throw new ValidationException([
    'email' => 'Invalid email format',
    'phone' => 'Phone number required'
], 'Validation failed');

// Authentication (401)
throw new AuthenticationException('Token expired', 'expired');

// Authorization (403)
throw new AuthorizationException('MANAGE_USERS');

// Not Found (404)
throw new NotFoundException('Invoice', 'INV-123');

// Conflict (409)
throw new ConflictException('Already voided', 'ALREADY_VOIDED');

// Rate Limit (429)
throw new RateLimitException(60);

API Bootstrap Pattern

See references/bootstrap.php for complete file

Include at top of all API endpoints:

require_once __DIR__ . '/bootstrap.php';

// Helper functions available:
require_method(['POST', 'PUT']);
$data = read_json_body();
validate_required($data, ['customer_id', 'amount']);
$db = get_db();
$token = bearer_token();
require_auth();
require_permission('MANAGE_INVOICES');
handle_request(function() { /* endpoint logic */ });

Endpoint Implementation Pattern

See examples/InvoicesEndpoint.php for complete example

require_once __DIR__ . '/../bootstrap.php';
use App\Http\ApiResponse;
use App\Http\Exceptions\{NotFoundException, ValidationException};

require_auth();
handle_request(function() {
    $method = $_SERVER['REQUEST_METHOD'];
    match ($method) {
        'POST' => handlePost(),
        default => ApiResponse::methodNotAllowed('POST')
    };
});

function handlePost(): void {
    $data = read_json_body();
    validate_required($data, ['customer_id', 'items']);

    if (empty($data['items'])) {
        throw new ValidationException(['items' => 'Required']);
    }

    // Business logic...
    ApiResponse::created(['id' => $id], 'Created successfully');
}

Frontend Integration

See examples/ApiClient.js for complete implementation

const api = new ApiClient("./api");

// GET - Errors automatically shown via SweetAlert2
const response = await api.get("invoices.php", { status: "pending" });
if (response) renderInvoices(response.data);

// POST - Validation errors highlight form fields
showLoading("Creating...");
const result = await api.post("invoices.php", formData);
hideLoading();
if (result) showSuccess("Created successfully");

// DELETE - With confirmation
const { value: reason } = await Swal.fire({
  title: "Void?",
  input: "textarea",
  showCancelButton: true,
});
if (reason) {
  const res = await api.delete(`invoices.php?id=${id}`, { reason });
  if (res) showSuccess("Voided");
}

// Helpers: showSuccess/Error/Warning/Info, showConfirm, showLoading, hideLoading

Critical Error Display Pattern

MANDATORY: Always show API errors to users in SweetAlert2

try {
  const response = await $.ajax({
    url: "./api/endpoint.php?action=verify",
    method: "POST",
    contentType: "application/json",
    data: JSON.stringify({ id: 123 }),
  });

  // Check response.success BEFORE using data
  if (!response.success) {
    await Swal.fire({
      icon: "error",
      title: "Operation Failed",
      text: response.message || "An error occurred",
      confirmButtonText: "OK",
    });
    return; // Stop execution
  }

  // Success path
  await Swal.fire({
    icon: "success",
    title: "Success!",
    text: response.message || "Operation completed",
  });

} catch (error) {
  // Extract error message from different formats
  let errorMessage = "An unexpected error occurred";

  if (error.responseJSON && error.responseJSON.message) {
    errorMessage = error.responseJSON.message; // API error message
  } else if (error.message) {
    errorMessage = error.message; // JavaScript error
  }

  await Swal.fire({
    icon: "error",
    title: "Error",
    text: errorMessage,
    confirmButtonText: "OK",
  });
}

Key Points:

• ✅ Always check response.success before proceeding
• ✅ Show error message in SweetAlert (never silent failure)
• ✅ Extract message from response.message or error.responseJSON.message
• ✅ Close any open modals before showing error
• ✅ Use await to ensure user sees error before code continues

Debugging Data Shape Mismatches

• When you see not a function errors in JS, trace the full chain: service return → API wrapper → JS consumer.
• Services may intentionally wrap arrays (e.g., { sales: [...] }) for mobile consumers while web UI expects a flat array.
• Normalize defensively when response shape may vary:

const rows = Array.isArray(data)
  ? data
  : Array.isArray(data?.sales)
    ? data.sales
    : [];

API Contract Validation (Frontend-Backend Alignment)

See references/contract-validation.md for complete guide

Critical Pattern: Always validate that frontend data matches backend API requirements. Missing fields cause 400 errors that are difficult to debug without detailed error messages.

Common Scenario:

// Frontend sends incomplete data
{ agent_id: 2, payment_method: "Cash", amount: 10000 }

// API expects (but doesn't communicate):
{ agent_id: 2, sales_point_id: 5, remittance_date: "2026-02-10", ... }

// Result: Generic 400 Bad Request ❌

Solution: Field-Specific Validation

// Backend: Return specific errors (HTTP 422)
$errors = [];
if (empty($input['sales_point_id'])) {
    $errors['sales_point_id'] = 'Sales point ID is required';
}
if (empty($input['remittance_date'])) {
    $errors['remittance_date'] = 'Remittance date is required';
}
if (!empty($errors)) {
    ResponseHandler::validationError($errors);
}

Quick Checklist:

• ✅ Document required fields in endpoint comments
• ✅ Return field-specific errors (HTTP 422, not 400)
• ✅ Validate frontend data before API call
• ✅ Match parameter names exactly (snake_case consistency)
• ✅ Log validation failures with request context
• ✅ Action in query string, payload in JSON body (see below)

Action Parameter Location:

// ✅ CORRECT: Action in URL
url: "./api/endpoint.php?action=create",
data: JSON.stringify({ agent_id: 2, amount: 10000 })

// ❌ WRONG: Action in body
url: "./api/endpoint.php",
data: JSON.stringify({ action: "create", agent_id: 2 })

Why: Query string for routing, JSON body for payload. Makes URLs clear, enables caching, readable logs.

Debugging: Check browser console → network tab → PHP error log → compare contracts → test with curl

Key Takeaways:

• "Always validate API requirements against the frontend data being sent. Generic 400 errors without field details make debugging exponentially harder."
• "Use query string for action/method routing, JSON body for request payload. Check BOTH where API reads it ($_GET vs $input) AND where frontend sends it (URL vs body)."

Error Message Extraction

SQLSTATE 45000 (Trigger):

SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Overpayment not allowed';
-- Extracted: "Overpayment not allowed" → Code: OVERPAYMENT_NOT_ALLOWED

SQLSTATE 23000 (Duplicate):

"Duplicate entry 'john@example.com' for key 'uk_email'"
-- Extracted: "A record with this Email already exists: 'john@example.com'"

SQLSTATE 23000 (Foreign Key):

"Cannot delete or update a parent row..."
-- Extracted: "Referenced Customer does not exist or cannot be deleted"

Deadlock:

"Deadlock found when trying to get lock..."
-- Extracted: "Database conflict. Please try again." → HTTP 503

Validation Pattern

Backend:

$errors = [];
if (empty($data['email'])) $errors['email'] = 'Email required';
elseif (!filter_var($data['email'], FILTER_VALIDATE_EMAIL))
    $errors['email'] = 'Invalid email';

if ($errors) ApiResponse::validationError($errors);

Frontend automatically:

• SweetAlert2 with formatted error list
• Highlights fields with .is-invalid
• Adds .invalid-feedback elements

Business Rule Pattern

$stmt = $db->prepare("SELECT status FROM invoices WHERE id = ? FOR UPDATE");
$stmt->execute([$id]);
$invoice = $stmt->fetch();

if (!$invoice) throw new NotFoundException('Invoice', $id);
if ($invoice['status'] === 'voided')
    throw new ConflictException('Already voided', 'ALREADY_VOIDED');
if ($invoice['status'] === 'paid')
    throw new ConflictException('Cannot void paid invoice', 'INVOICE_PAID');

Logging Pattern

All errors logged with context:

[req_abc123] PDOException: SQLSTATE[45000]: Overpayment not allowed in /api/payments.php:45
Context: {"user_id":123,"franchise_id":5,"url":"/api/payments.php","method":"POST"}

Implementation Checklist

Backend:

• All endpoints use ApiResponse helper
• All exceptions caught by ExceptionHandler
• Specific error codes for each error type
• PDOException messages properly extracted
• Trigger errors parsed (SQLSTATE 45000)
• Constraint violations give meaningful messages
• Stack traces hidden in production
• All errors logged with request ID
• HTTP status codes match error types
• Bootstrap file included in all endpoints

Frontend:

• All API calls use centralized ApiClient
• Errors displayed via SweetAlert2 only (no native alert/confirm)
• Validation errors highlight form fields
• Network errors handled gracefully
• Loading states shown during requests
• Error codes displayed in footer
• Offline state detected and handled
• Request IDs logged for debugging

Database:

• Triggers use SQLSTATE 45000 for business rules
• Clear, user-friendly error messages in triggers
• Constraints have descriptive names (uk_email_franchise)
• Foreign key errors give context

Quick Error Reference

// 400 - Bad Request
ApiResponse::error('Invalid request', 'BAD_REQUEST', 400);

// 401 - Unauthorized
ApiResponse::unauthorized('Session expired');

// 403 - Forbidden
ApiResponse::forbidden('MANAGE_USERS');

// 404 - Not Found
ApiResponse::notFound('Invoice', 'INV-123');

// 409 - Conflict
ApiResponse::conflict('Already voided', 'ALREADY_VOIDED');

// 422 - Validation
ApiResponse::validationError(['email' => 'Invalid format']);

// 500 - Server Error
ApiResponse::serverError('Unexpected error occurred');

Security Considerations

Production:

• Never expose stack traces
• Sanitize database error messages
• Log full errors server-side only
• Generic messages for unexpected errors

Development:

• Set APP_DEBUG=true for detailed errors
• Stack traces in logs
• Actual error messages displayed

Sensitive Data:

• Never include passwords in logs
• Sanitize SQL queries in error messages
• Remove file paths from production errors

Summary

Implementation:

1. Include bootstrap.php at top of all endpoints
2. Use ApiResponse helper for all responses
3. Throw custom exceptions for specific errors
4. Let ExceptionHandler convert to JSON
5. Use ApiClient class on frontend
6. Display all errors via SweetAlert2

Key Files:

• references/ApiResponse.php - Response helper
• references/ExceptionHandler.php - Exception converter
• references/CustomExceptions.php - Exception classes
• references/bootstrap.php - API setup
• examples/InvoicesEndpoint.php - Complete endpoint
• examples/ApiClient.js - Frontend client

Benefits:

• Consistent error format across all endpoints
• Specific messages from database exceptions
• Beautiful error display with SweetAlert2
• Easy debugging with request IDs
• Secure (no sensitive data exposure)
• Developer-friendly (clear patterns)

Remember: All error messages must be suitable for direct display in SweetAlert2. Write them for end users, not developers.