conventions-scale

Standardize scalable architecture decisions for endpoints, database tables, and deployment.

163|43|Updated May 3, 2026
One-click install
npx skills add https://github.com/stella/stella --skill conventions-scale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions-scale
Source: https://github.com/stella/stella/tree/main/.agents/skills/conventions-scale
Command: npx skills add https://github.com/stella/stella --skill conventions-scale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scalable architecture decisions are often inconsistent across teams, leading to costly rewrites. This Convention provides a framework to align teams on scalable patterns and guardrails.

Core Features & Use Cases

  • Pagination and streaming guidelines to avoid unbounded result sets and support efficient data retrieval.
  • Tenant isolation and readiness for future row level security to protect multi-tenant data.
  • Stateless API design and modular boundaries to enable load-balanced deployment and easier scaling.
  • Centralized resource limits, AI provider abstraction, and clear indexing strategies to promote maintainable growth.
  • Design patterns for safe connections and external poolers to improve reliability under load.

Quick Start

Apply these conventions to your next architectural change by reviewing endpoints, data access patterns, and deployment constraints to ensure scalability.

Frequently Asked Questions about conventions-scale

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design scalable API endpoints for large-scale usage?

Handle multi-tenant database isolation by applying tenant isolation conventions and preparing data models for future row level security. Standardize indexing strategies to protect multi-tenant data and maintain efficient query performance across isolated tenants.

How does stateless API design improve deployment scalability?

Stateless API design improves deployment scalability by removing server-side session state, enabling any server instance to handle any request. This allows load-balanced deployment and modular boundaries, making it easier to scale applications horizontally without session affinity constraints.

When do I need pagination and streaming guidelines for database queries?

You need pagination and streaming guidelines when designing new endpoints or adding database tables to prevent unbounded result sets. These conventions ensure efficient data retrieval, standardize query limits, and protect system memory when processing large-scale data requests.

Why should I use external connection poolers for scalable architecture?

Use external connection poolers to improve database reliability under heavy load. Safe connection pooling design patterns manage database connections efficiently, preventing connection exhaustion and maintaining stable performance when scaling applications for large-scale usage.

Do I need configurable resource limits and AI provider abstraction for scaling?

Configurable resource limits and AI provider abstraction are essential for maintainable growth when scaling architecture. Centralized limits prevent resource exhaustion, while provider abstraction decouples AI dependencies, ensuring the system remains flexible and scalable across different services.