skill
fortune-checklist
Autonomous 518-point pre-launch QA for web projects — a Claude Code skill by FortuneCode. Type /fortune-checklist and it audits your repo with evidence and returns GO/NO-GO.
Set up
Skills are installed by placing their folder where your agent loads skills.
The download comes from github.com/Fortune-Code-Digital-Sloutions/fortune-checklist itself, not from our server, so what you get is exactly what its author published.
Install instructions come from the README
README
synced Oct 26, 2026Fortune Checklist
An autonomous, 518-point pre-launch QA for web projects — as a Claude Code skill.
Type /fortune-checklist in any repository and it explores the codebase, figures out the
stack, scopes the relevant checks, audits each one with real evidence, and hands you a
GO / NO-GO report. No flags, no config, no copy-pasting rows from a spreadsheet.
Built and open-sourced by FortuneCode — the quality bar we hold our own client websites, web apps, and software to before they ship.
Why
Most sites ship with the same avoidable holes: a missing security header, an unindexed page, a form with no validation, an image that tanks Core Web Vitals, a payment path nobody tested end to end. A checklist helps — but a 500-row spreadsheet nobody fills in doesn't.
Fortune Checklist turns that spreadsheet into something an AI agent actually runs for you, against your real code, with one rule that makes it trustworthy:
Never mark PASS without direct evidence. If it can only be proven outside the code (DNS, SSL, live payments, real email, analytics, a physical device), it stays PARTIAL with the exact manual step written out — never a hopeful green check.
What's inside
- 518 checks across 30 categories — scope, build, content, UX, responsive design, browser support, accessibility (WCAG 2.2), forms, technical SEO, structured data, performance & Core Web Vitals, frontend & backend quality, database integrity, auth, application security, privacy & legal, analytics, email, CMS/admin, e-commerce & payments, i18n/RTL, PWA, infrastructure, monitoring, backups, DNS/SSL, testing, handover, and post-launch validation.
- 222 P0 launch blockers — the subset that must be green (or a justified N/A) before go-live.
- A domain-tailored prompt for every single check — the security checks think like an application-security engineer, the SEO checks like a technical-SEO engineer, the a11y checks to WCAG 2.2 AA, and so on. 26 distinct expert personas, not one generic template.
- Evidence-based grading — PASS / FAIL / PARTIAL / N/A, each with cited files, routes, headers, commands, and results.
Install
Option A — as a Claude Code plugin (recommended):
/plugin marketplace add Fortune-Code-Digital-Sloutions/fortune-checklist
/plugin install fortune-checklist
Option B — drop in the skill folder:
Copy skills/fortune-checklist/ into your skills directory:
git clone https://github.com/Fortune-Code-Digital-Sloutions/fortune-checklist
cp -r fortune-checklist/skills/fortune-checklist ~/.claude/skills/
Then restart Claude Code. (Requires Python 3 for the bundled helper scripts.)
Use it
Just say what you want — in English or Arabic. It maps your intent to the right checks and runs itself.
/fortune-checklist # full audit of the current repo
/fortune-checklist review the security # only the security-related categories
/fortune-checklist check SEO
/fortune-checklist just the P0 blockers
راجع السيكيوريتي # عربي برضه
It will:
- Read your intent (any language) and pick the relevant categories — or run everything.
- Profile the project — framework, auth, database, e-commerce, i18n, PWA, email… — and mark genuinely inapplicable checks N/A so the report reflects real risk.
- Audit P0 first, then the rest, using each check's own expert prompt against your code.
- Report a clean GO / NO-GO with open blockers, a per-category rollup, and the manual external verifications still outstanding.
- Offer to fix the P0 failures in reviewed batches — it audits autonomously but never mass-edits your codebase without a nod.
The 30 categories
| # | Category | # | Category |
|---|---|---|---|
| 01 | Project Scope & Requirements | 16 | Application Security |
| 02 | Repository, Configuration & Build | 17 | Privacy, Cookies & Legal |
| 03 | Content & Brand Quality | 18 | Analytics & Marketing Integrations |
| 04 | Navigation & User Experience | 19 | Email & Notifications |
| 05 | Responsive Design & Device Layout | 20 | CMS & Admin Experience |
| 06 | Browser & Device Compatibility | 21 | E-commerce & Payments |
| 07 | Accessibility | 22 | Internationalization, Localization & RTL |
| 08 | Forms & Data Entry | 23 | PWA & Service Worker |
| 09 | Technical SEO | 24 | Infrastructure & Deployment |
| 10 | Structured Data & Social Sharing | 25 | Monitoring, Logging & Alerting |
| 11 | Performance & Core Web Vitals | 26 | Backups & Disaster Recovery |
| 12 | Frontend Code Quality | 27 | Domain, DNS, SSL & Email DNS |
| 13 | Backend & API Quality | 28 | Testing & Quality Assurance |
| 14 | Database & Data Integrity | 29 | Handover & Documentation |
| 15 | Authentication & Authorization | 30 | Post-Launch Validation |
Every check aligns with public standards — Google Search Essentials, WCAG 2.2, OWASP ASVS / Top 10, Core Web Vitals, PCI DSS, DMARC.
Who it's for
Agencies and freelancers delivering client sites, product teams shipping to production, and anyone who wants a rigorous, repeatable "is this actually ready?" gate that runs itself.
Built by FortuneCode
FortuneCode is a digital solutions studio that builds websites, web & mobile apps, and custom software — with a heavy focus on quality, security, and performance. This skill is the same pre-launch gate we run on our own deliveries.
Need a site or app built to this standard? → fortunecode.org
- 🌐 Website: https://www.fortunecode.org/
- 🐙 GitHub: https://github.com/Fortune-Code-Digital-Sloutions
If Fortune Checklist saves you a rough launch, a ⭐ on the repo helps other teams find it.
Contributing
Issues and PRs welcome — new checks, sharper prompts, framework-specific detection. Keep the core rule intact: no PASS without evidence.
License
MIT © FortuneCode — see LICENSE.