When the user wants the day-to-day review of how code ships. Use when they say day-to-day, /day-to-day, CI/CD, staging, or how a deploy becomes visible. Follow cloudflare or render for the preview and the deploy Action. Do not deploy.

Kickoff prompt

Review this app for /day-to-day. How does code get to staging and then production? The files do not name Cloudflare or Render.

npx skills add StephanSmith-me/builder-skills --skill day-to-day

Day to day

You run the day-to-day review by following the host that ships the app. Cloudflare Pages or Workers follows cloudflare. Render follows render. You bring back the preview and the deploy Action. You do not deploy, and you do not re-walk the rest of that host.

Before you start

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

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

If they ask for the full Cloudflare setup, use cloudflare directly. If they ask what Render runs, use render directly. This skill is the ship check.

What to bring back

Follow the host you can see and bring back only these two:

A preview, or only the primary branch.
A GitHub Action that deploys to that host, or that the deploy Action is absent.

Cloudflare is cloudflare. Render is render. Both present: one line for each. Do not pick a winner. Neither in the files you opened: the ship path is unseen. Do not assume Cloudflare.

Branch handling in the repo is part of that answer. Dashboard settings you did not open stay unseen. Do not add a preview, and do not create the workflow.

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
cloudflare — the preview and the deploy Action when Pages or Workers ship the app
render — the preview and the deploy Action when Render ships the app

Subskills

Open the one that matches the tool you're already using.

Tools I use
Infisical
aka Infisical.com
Where secrets live once they leave a .env file or a hosted builder.
On the workbench
GitHub
The repo's Actions. They are signals for observability and scalability. A workflow that names main is not a maturity mark.
On the workbench
ImprovMX
Off-brand domain mail. Aliases forward into the Gmail you already use.
On the workbench
PostHog
Product analytics, from a public session through to a known user.
On the workbench
Postmark
Product email. The send path, the template, and where the send key lives.
On the workbench
Resend
Product email in the same job as Postmark. Common when an app was vibe-coded.

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.