Gallery

Scalability

v0.1.3 1 reference

When the user wants the scalability review. Use when they say scalability, /scalability, more traffic, or more business. Follow hosting, fly, and inngest, and bring those results back. Do not choose a host here.

Kickoff prompt

Review this app for /scalability. How will it handle more traffic, meaning more business?

npx skills add StephanSmith-me/builder-skills --skill scalability

Scalability

You run the scalability review by following three skills. You bring back what each one reports. You do not choose a host, and you do not deploy.

Before you start

If .agents/product-context.md exists, read it.

Read references/which-skills.md before you answer.

What to bring back

Follow each skill. Report its result in a line. Do not re-walk it.

  1. hosting — which host matches the project.
  2. fly — whether Fly is the host, and how much of it is in the repo.
  3. inngest — whether jobs should move, and whether the jobs that exist will scale.

If one of them says it does not apply, say that. Do not fill the gap yourself. Do not add a fourth skill.

Report

When you finish, follow report. Say what they now know and what they can skip, then name the rule and one next prompt or skill. When you name what to do, also score effort and impact, then rank. Do not start the work.

Related skills

  • product-context — read first when the file exists
  • hosting — GitHub or Cloudflare Pages for the product
  • fly — Fly instead of AWS
  • inngest — jobs that will not scale

Subskills

These are the hosts I look at when more customers would mean more traffic.

  • On the workbench

    Cloudflare

    The edge of the stack: tunnels, Pages, and Workers, and how a preview branch and a deploy Action ship the app.

  • On the workbench

    Fly.io

    The app host when you do not want AWS. The setup that matters lives in a Dockerfile and fly.toml in the repo.

  • On the workbench

    Render

    When the user wants the Render setup reviewed, including how it ships.

Coming soon

is coming soon. It is not battle-ready yet. Subscribe to get an update when this skill comes online.

Need this to remember the business? Move to the MCP for more context.

Get the weekly note

Join 1,700 founders and builders. One note a week—straight to your inbox.

I write about the founder-side of tech decisions: what to buy, what to build, what to skip, and what you will regret six months from now. Start with what I've written in Insights, browse by theme, or see the tools I use.