Library — DistroSource

Everything digital. One source.

37 resources

Checklist · Beginner · 10 min
Weekly Minecraft server health check checklist
A fifteen-minute weekly check for a community server.
- Servers decay quietly. Fifteen minutes a week catches the problems before the players do.
- ☐ Latest log read for new exceptions; plugin named
- ☐ TPS checked at peak time
Items 10
Checklist · Beginner · 10 min
Weekly FiveM server health check checklist
The fifteen-minute weekly check that catches problems before players do.
- Servers decay quietly: a resource starts erroring, backups stop, staff drift. Fifteen minutes a week catches it.
- ☐ Crash log read; new errors noted with the resource name
- ☐ Console warnings for slow resources reviewed
Items 10
Checklist · Beginner · 10 min
Client offboarding checklist
What to do when a client relationship ends, cleanly.
- How a client leaves decides whether they come back or refer. Do it properly.
- ☐ Final invoice sent and paid
- ☐ All deliverables in the agreed location with the naming convention
Items 10
Checklist · Beginner · 10 min
Email send before it goes out checklist
The five-minute check before a campaign email is sent to the list.
- Every email mistake is sent to everyone. Five minutes here beats an apology email.
- ☐ Subject line states the idea; preview text set
- ☐ One link, tested, tagged
Items 10
Checklist · Beginner · 10 min
Pull request ready for review checklist
What a pull request contains before a reviewer is asked to spend time on it.
- Reviewer time is the scarcest resource on a team. Spend it on judgement, not on things a checklist catches.
- ☐ Title states the behaviour change
- ☐ Description says why, not only what
Items 10
Checklist · Beginner · 10 min
New tool rollout checklist
What to do the week a new tool goes live so people actually use it.
- Tools fail on adoption, not features. This week decides it.
- ☐ The three jobs it is for are written and shared
- ☐ Data imported and deduplicated
Items 10
Checklist · Beginner · 10 min
Store launch day checklist
The morning-of checks before a store or product line goes public.
- Launch day problems are almost always on this list.
- ☐ Checkout tested with a real card in the last 24 hours
- ☐ Library delivery tested for a new account and a guest
Items 10
Checklist · Beginner · 10 min
Support macro before it goes live checklist
The checks a new reply macro passes before agents can use it.
- A bad macro is a mistake sent a hundred times. Review each one once, properly.
- ☐ Under ninety words
- ☐ Uses only policy sentences from the snippet library
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Automation touching customer orders checklist
What an ecommerce automation must satisfy before it can change or message an order.
- Order automations are where a small bug becomes a hundred wrong emails. Verify these before enabling.
- ☐ Trigger is deduplicated on order id
- ☐ Every write is idempotent
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
CRM data before automating on it checklist
The data hygiene an automation needs before it can route, score or nudge from CRM records.
- Automations amplify whatever is in the CRM. Clean first.
- ☐ Emails lower-cased and deduplicated
- ☐ Stage definitions written and applied
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Agent evaluation before release checklist
What an evaluation run must show before an agent is released or updated.
- An agent update without an evaluation is a guess deployed to users.
- ☐ A fixed test set of thirty or more inputs including refuse cases
- ☐ Expected outputs or a rubric per case
Items 10ClaudeChatGPT
Checklist · Beginner · 10 min
Minecraft server launch checklist
What must be true before a public launch.
- The first weekend decides a server's reputation. This list protects it.
- ☐ Platform installed with recommended memory flags
- ☐ World protection and rollback tested
Items 10
Checklist · Beginner · 10 min
FiveM server launch checklist
What must be true before the server opens to the public.
- Opening day problems are almost always on this list.
- ☐ Clean boot with no console errors
- ☐ Framework and dependencies at documented versions
Items 10
Checklist · Beginner · 10 min
Project delivery checklist
What must be true before a project is handed over.
- Handover is where agencies lose the last five percent. This list is the five percent.
- ☐ Every deliverable meets its done-criteria
- ☐ Internal review recorded for each
Items 10
Checklist · Beginner · 10 min
Campaign launch checklist
What must be true the morning a campaign goes live.
- Campaigns fail on details: a wrong link, a mismatched price. This list catches them.
- ☐ Every asset states the same price, date and offer
- ☐ Every claim has proof
Items 10
Checklist · Beginner · 10 min
Production deploy checklist
What to verify before and after a production deploy.
- Deploys go wrong in the same ten ways. This list is those ten.
- ☐ Typecheck, tests and build green on the exact commit
- ☐ Migrations applied before the code that needs them
Items 10
Checklist · Beginner · 10 min
Monthly business admin checklist
The admin that keeps a small business out of trouble, done once a month.
- Small businesses get into trouble through missed admin, not bad decisions. This list is the monthly minimum.
- ☐ Books reconciled and closed
- ☐ Invoices sent for all completed work
Items 10
Checklist · Beginner · 10 min
Product listing before publishing checklist
What every listing needs before a buyer sees it.
- Thin listings get returns and questions. This list is the minimum for a listing that sells and stays sold.
- ☐ Name says what it is and for whom
- ☐ First image shows the real product
Items 10
Checklist · Beginner · 10 min
AI automation go-live checklist
What must be true before an assistant-driven automation runs on real work.
- Assistant automations fail quietly and confidently. This list makes the failure visible before it costs anything.
- ☐ The step the assistant performs is a transformation, not a decision or side effect
- ☐ Inputs are redacted of personal data
Items 10Any assistant
Checklist · Beginner · 10 min
SaaS launch checklist
The items that must be true before the first paying customer is invited.
- A launch checklist is the difference between a first customer and a first refund. These items are the minimum.
- ☐ Sign-in, reset and verification tested from a real inbox
- ☐ Billing tested with a real card in test mode and one real charge
Items 10
Checklist · Beginner · 10 min
Process handover checklist
What must exist before a process can be handed to someone new or to an automation.
- A process that lives in one head is not a process. This is the minimum written form.
- ☐ Purpose in one sentence
- ☐ Trigger and frequency
Items 10Any assistant
Checklist · Beginner · 10 min
Scheduled job safety checklist
What a nightly job needs before it is allowed to run unattended.
- A job that misfires at night can destroy data by morning. These items prevent that.
- ☐ Dry run by default; --write to act
- ☐ Idempotent: running twice is safe
Items 10Claude CodeAny assistant
Checklist · Beginner · 10 min
No-code scenario review checklist
A review list for scenarios built by someone else, or by you last quarter.
- Scenarios rot. This list finds the rot before it finds a customer.
- ☐ Every module is named by what it does
- ☐ The trigger's polling interval is deliberate
Items 10MakeZapier
Checklist · Beginner · 10 min
Automation go-live checklist
What to verify before an automation runs unattended.
- Automations that work in a test run fail on the first unexpected input. This list is the unexpected input.
- ☐ Tested with a missing field
- ☐ Tested with a duplicate trigger
Items 10ZapierMake

Search