{"id":"8bfe4eae-af8b-4aec-9db3-19683cabd623","slug":"fortune-checklist","kind":"skill","name":"fortune-checklist","summary":"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.","owner":"Fortune-Code-Digital-Sloutions","repoUrl":"https://github.com/Fortune-Code-Digital-Sloutions/fortune-checklist","license":"MIT","licenseTier":"permissive","trust":"community","stars":1,"match":null,"fewStars":true,"format":"skill","createdAt":"2026-07-27T13:52:21.000Z","addedAt":"2026-10-21T13:23:07.404Z","logoUrl":"https://avatars.githubusercontent.com/u/256387388?v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["developer-tools","writing"],"tags":["accessibility","claude-code","claude-plugin","launch","performance","pre-launch-checklist","qa","security"],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-26T08:40:23.323Z","sample":false,"url":"https://conduits.dev/tools/fortune-checklist","language":"Python","transports":["stdio"],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# Fortune Checklist\n\n**An autonomous, 518-point pre-launch QA for web projects — as a Claude Code skill.**\n\nType `/fortune-checklist` in any repository and it explores the codebase, figures out the\nstack, scopes the relevant checks, audits each one with real evidence, and hands you a\n**GO / NO-GO** report. No flags, no config, no copy-pasting rows from a spreadsheet.\n\nBuilt and open-sourced by **[FortuneCode](https://www.fortunecode.org/)** — the quality bar\nwe hold our own client websites, web apps, and software to before they ship.\n\n<p align=\"center\">\n  <a href=\"https://www.fortunecode.org/\"><img alt=\"Made by FortuneCode\" src=\"https://img.shields.io/badge/made%20by-FortuneCode-111111\"></a>\n  <img alt=\"Checks\" src=\"https://img.shields.io/badge/checks-518-2e7d32\">\n  <img alt=\"Launch blockers\" src=\"https://img.shields.io/badge/P0%20blockers-222-b00020\">\n  <img alt=\"Categories\" src=\"https://img.shields.io/badge/categories-30-1565c0\">\n  <img alt=\"License\" src=\"https://img.shields.io/badge/license-MIT-555\">\n</p>\n\n---\n\n## Why\n\nMost sites ship with the same avoidable holes: a missing security header, an unindexed page,\na form with no validation, an image that tanks Core Web Vitals, a payment path nobody tested\nend to end. A checklist helps — but a 500-row spreadsheet nobody fills in doesn't.\n\nFortune Checklist turns that spreadsheet into something an AI agent actually *runs for you*,\nagainst your real code, with one rule that makes it trustworthy:\n\n> **Never mark PASS without direct evidence.** If it can only be proven outside the code\n> (DNS, SSL, live payments, real email, analytics, a physical device), it stays **PARTIAL**\n> with the exact manual step written out — never a hopeful green check.\n\n## What's inside\n\n- **518 checks** across **30 categories** — scope, build, content, UX, responsive design,\n  browser support, accessibility (WCAG 2.2), forms, technical SEO, structured data,\n  performance & Core Web Vitals, frontend & backend quality, database integrity, auth,\n  application security, privacy & legal, analytics, email, CMS/admin, e-commerce & payments,\n  i18n/RTL, PWA, infrastructure, monitoring, backups, DNS/SSL, testing, handover, and\n  post-launch validation.\n- **222 P0 launch blockers** — the subset that must be green (or a justified N/A) before go-live.\n- **A domain-tailored prompt for every single check** — the security checks think like an\n  application-security engineer, the SEO checks like a technical-SEO engineer, the a11y checks\n  to WCAG 2.2 AA, and so on. 26 distinct expert personas, not one generic template.\n- **Evidence-based grading** — PASS / FAIL / PARTIAL / N/A, each with cited files, routes,\n  headers, commands, and results.\n\n## Install\n\n**Option A — as a Claude Code plugin (recommended):**\n\n```\n/plugin marketplace add Fortune-Code-Digital-Sloutions/fortune-checklist\n/plugin install fortune-checklist\n```\n\n**Option B — drop in the skill folder:**\n\nCopy `skills/fortune-checklist/` into your skills directory:\n\n```bash\ngit clone https://github.com/Fortune-Code-Digital-Sloutions/fortune-checklist\ncp -r fortune-checklist/skills/fortune-checklist ~/.claude/skills/\n```\n\nThen restart Claude Code. (Requires Python 3 for the bundled helper scripts.)\n\n## Use it\n\nJust say what you want — in English or Arabic. It maps your intent to the right checks and runs itself.\n\n```\n/fortune-checklist                     # full audit of the current repo\n/fortune-checklist review the security # only the security-related categories\n/fortune-checklist check SEO\n/fortune-checklist just the P0 blockers\nراجع السيكيوريتي                        # عربي برضه\n```\n\nIt will:\n\n1. **Read your intent** (any language) and pick the relevant categories — or run everything.\n2. **Profile the project** — framework, auth, database, e-commerce, i18n, PWA, email… — and\n   mark genuinely inapplicable checks **N/A** so the report reflects real risk.\n3. **Audit** P0 first, then the rest, using each check's own expert prompt against your code.\n4. **Report** a clean GO / NO-GO with open blockers, a per-category rollup, and the manual\n   external verifications still outstanding.\n5. **Offer to fix** the P0 failures in reviewed batches — it audits autonomously but never\n   mass-edits your codebase without a nod.\n\n## The 30 categories\n\n| # | Category | # | Category |\n|---|---|---|---|\n| 01 | Project Scope & Requirements | 16 | Application Security |\n| 02 | Repository, Configuration & Build | 17 | Privacy, Cookies & Legal |\n| 03 | Content & Brand Quality | 18 | Analytics & Marketing Integrations |\n| 04 | Navigation & User Experience | 19 | Email & Notifications |\n| 05 | Responsive Design & Device Layout | 20 | CMS & Admin Experience |\n| 06 | Browser & Device Compatibility | 21 | E-commerce & Payments |\n| 07 | Accessibility | 22 | Internationalization, Localization & RTL |\n| 08 | Forms & Data Entry | 23 | PWA & Service Worker |\n| 09 | Technical SEO | 24 | Infrastructure & Deployment |\n| 10 | Structured Data & Social Sharing | 25 | Monitoring, Logging & Alerting |\n| 11 | Performance & Core Web Vitals | 26 | Backups & Disaster Recovery |\n| 12 | Frontend Code Quality | 27 | Domain, DNS, SSL & Email DNS |\n| 13 | Backend & API Quality | 28 | Testing & Quality Assurance |\n| 14 | Database & Data Integrity | 29 | Handover & Documentation |\n| 15 | Authentication & Authorization | 30 | Post-Launch Validation |\n\nEvery check aligns with public standards — Google Search Essentials, WCAG 2.2, OWASP ASVS /\nTop 10, Core Web Vitals, PCI DSS, DMARC.\n\n## Who it's for\n\nAgencies and freelancers delivering client sites, product teams shipping to production, and\nanyone who wants a rigorous, repeatable \"is this actually ready?\" gate that runs itself.\n\n---\n\n## Built by FortuneCode\n\n**[FortuneCode](https://www.fortunecode.org/)** is a digital solutions studio that builds\n**websites, web & mobile apps, and custom software** — with a heavy focus on quality, security,\nand performance. This skill is the same pre-launch gate we run on our own deliveries.\n\nNeed a site or app built to this standard? → **[fortunecode.org](https://www.fortunecode.org/)**\n\n- 🌐 Website: https://www.fortunecode.org/\n- 🐙 GitHub: https://github.com/Fortune-Code-Digital-Sloutions\n\nIf Fortune Checklist saves you a rough launch, a ⭐ on the repo helps other teams find it.\n\n## Contributing\n\nIssues and PRs welcome — new checks, sharper prompts, framework-specific detection. Keep the\ncore rule intact: **no PASS without evidence.**\n\n## License\n\nMIT © FortuneCode — see [LICENSE](LICENSE).\n"}