A skill for Claude Code and Codex · Software and infrastructure
escala is the skill that gets your AI to decide what to multiply, when, and in what order, so your site or system can handle load: measure first, layered caching, vertical before horizontal, queues for slow work, stateless design, load balancer, containers and database replicas. It covers everything from a site on shared hosting to a SaaS running on a VPS, with zero over-engineering.
Solo skill: unlocks right away, no guarantee after download. Purchase terms.
Or get all 25 skills plus 9 bonuses in the Supreme Pack for R$ 497.
The problem
When the system chokes, the reflex is to upgrade the plan or install Kubernetes, when the real problem is often a query missing an index or an email being sent inside the request. Three symptoms, and what changes with the skill.
| Without the skill | With escala |
|---|---|
| The site slows down at peak, and the first move is renting a bigger machine, without anyone measuring whether the bottleneck is the database, the disk, cache, or code. | It measures first and finds the bottleneck, then climbs the ladder one rung at a time: code and data, cache, a bigger machine, queues, stateless design, and only then horizontal scaling. |
| Someone spins up multiple instances behind a load balancer and login breaks, because the session lived in memory and uploads sat on a single machine's disk. | Stateless design as a prerequisite for horizontal scaling: sessions in Redis or a token, files in object storage, and nothing stuck on the instance's disk. |
| A project with a few hundred users running an expensive, complicated cluster, because scaling seemed to require the same tooling as big tech companies. | Simplicity first: a VPS, Compose and Swarm solve almost everything, and heavy orchestration only comes in once the complexity justifies the cost. |
What you get out of it
A scaling plan in the right order, with the current rung, the next one, and the reasoning behind each choice.
what actually hurts: database, disk, missing cache, or slow work inside the request
where the project stands and which step solves it without skipping ahead
load balancer, containers, queue and database sized to the actual problem
load balancing with cache and health checks, replicas with Traefik, and a queue worker
How it works
Site or system, the real symptom, today's load versus the expected one, whether the bottleneck has been measured, and whether any state is stuck on the instance.
Ten rungs, from measuring and optimizing to high availability. It names the current rung and the next one that actually solves the problem.
Cache, vertical scaling, queues, stateless design, horizontal scaling, containers, or database, reading that rung's reference instead of dumping everything on the project.
Sites and hosting scale through cache, CDN, and the move from shared hosting to a VPS. Systems on a VPS scale through stateless design, queues, replicas, and a load balancer.
A production checklist and a catalog of pitfalls at the end, with the number confirmed by a load test, not by faith.
Before you buy
Without measurement, that's exactly where it starts, because scaling without measuring means spending money in the wrong place.
Its limits
The skill decides the order and the architecture, but the number for how much the system handles today comes from a load test, which is the job of teste-de-carga, also in the catalog.
The focus is containers and VPS, from a site on shared hosting to a SaaS running on multiple instances. Serverless shows up only as a footnote, not as the main path.
Changing infrastructure touches money and uptime: the skill proposes and explains, and executing it on your server stays your call.
What you receive
The price
Just escala
R$57one time payment
Bought it solo and now want it all? Message me on WhatsApp and I will deduct what you already paid.
Supreme Pack
R$ 1.665R$497or 10x on a card
Buying all 25 solo adds up to R$ 1.665. The pack pays for itself by the ninth skill. See everything the Supreme Pack includes
04 · Software and infrastructure
Before you ask
Yes. One of the two fronts is sites and hosting: page caching, CDN, tuning PHP and the database, and knowing the right moment to move from shared hosting to a VPS.
Almost never. A VPS with Compose or Swarm solves most cases, and the skill only recommends heavy orchestration when the complexity and the spike justify the operating cost.
Vertical means upgrading the machine, with more CPU and memory: simple, and it solves a lot, but it has a ceiling. Horizontal means multiplying instances behind a load balancer: no ceiling and it tolerates failure, but it requires a stateless system. The skill starts with vertical.
It tells you what to measure and what to do with the bottleneck. The actual capacity test, with a number of concurrent users, belongs to teste-de-carga, which complements this skill.
Yes, the license covers your work for third parties. What's off limits is reselling or redistributing the skill.
One-time payment, 12 months of updates. No refunds after download; the Supreme Pack comes with a 7-day guarantee.
