/api-design-patterns

Rule Title Here

Impact: MEDIUM (optional impact description)

Brief explanation of the rule and why it matters for API design. Focus on the benefits and problems it solves.

Incorrect (description of what's wrong):

// Bad example showing the anti-pattern
{
  "example": "bad"
}

Correct (description of what's right):

// Good example showing the recommended pattern
{
  "example": "good"
}

// Additional code examples if needed
app.get('/endpoint', (req, res) => {
  // Implementation
});

Why

1. Benefit 1: Explanation of why this matters
2. Benefit 2: Another important reason
3. Benefit 3: Additional context

Reference: Link to documentation