Discussion

Générateur complet de liste de vérification de préparation avant le lancement

De Wikiprompt, l’encyclopédie libre de prompts

Nureddin Gökbey İnaç

13 mars 2026

Générateur complet de liste de vérification de préparation avant le lancement Un invite détaillé pour générer une liste de contrôle avant lancement couvrant la fonctionnalité, le contenu, les espaces réservés visuels, le SEO, la performance, la sécurité, le multi-plateforme, l'infrastructure et la remise, avec un format de sortie spécifique.

Contenu du PromptEnregistrer

🌐
# Pre-Launch Checklist: [Project Name] **Project Type:** [e.g., E-commerce Web App] **Tech Stack:** [e.g., Next.js 14 / Vercel / Supabase] **Launch Type:** [e.g., Public Launch] **Domain:** [e.g., DNS configured - Yes/No] --- ## 1. Functionality - [ ] **All critical user flows work end-to-end** *Verify:* Run through the 5 most important user journeys (e.g., signup → browse → checkout) in a production-like environment. - [ ] **All forms submit correctly and show appropriate feedback** *Verify:* Submit each form with valid, invalid, and empty inputs; confirm success/error messages appear. - [ ] **Payment flow works (if applicable) - test with real sandbox** *Verify:* Process a test transaction using Stripe/PayPal sandbox credentials; confirm webhook events fire. - [ ] **Authentication works (login, logout, password reset, session expiry)** *Verify:* Test full auth cycle; confirm session tokens expire and redirect to login. - [ ] **Email notifications send correctly (check spam folders)** *Verify:* Trigger all email types (welcome, receipt, password reset) and confirm delivery in inbox and spam. - [ ] **Third-party integrations respond correctly** *Verify:* Ping each API (e.g., CRM, analytics, shipping) and confirm expected responses. - [ ] **Error handling works (what happens when things break?)** *Verify:* Force a 500 error, network failure, and invalid API response; confirm user-friendly error pages/messages. --- ## 2. Content & Copy - [ ] **No lorem ipsum remaining** *Verify:* Search codebase for `lorem` and visually scan all pages. - [ ] **All links work (no 404s)** *Verify:* Crawl site with a tool (e.g., Screaming Frog) or manually click all nav, footer, and in-content links. - [ ] **Legal pages exist (privacy policy, terms, cookie consent)** *Verify:* Confirm `/privacy`, `/terms`, and cookie banner are live and linked in footer. - [ ] **Contact information is correct** *Verify:* Check email, phone, and address on contact page and footer. - [ ] **Copyright year is current** *Verify:* Check footer and any other date references. - [ ] **Social media links point to correct profiles** *Verify:* Click each social icon and confirm it opens the right profile in a new tab. - [ ] **All images have alt text** *Verify:* Use an accessibility checker (e.g., axe) or manually inspect `<img>` tags. - [ ] **Favicon is set (all sizes)** *Verify:* Check browser tab, bookmarks, and mobile home screen icons. --- ## 3. Visual Placeholder Scan ### Codebase Scan Results | # | File Path | Line | Type | Current Value | Severity | Action Needed | |---|-----------|------|------|---------------|----------|---------------| | 1 | `src/app/page.tsx` | 42 | Image URL | `via.placeholder.com/800x400` | Critical | Replace with hero image | | 2 | `public/favicon.ico` | - | Framework default | Next.js default favicon | Critical | Replace with brand favicon | | 3 | `src/components/Card.tsx` | 18 | Missing fallback | No image = broken layout | High | Design empty state | | 4 | `public/vercel.svg` | - | Boilerplate asset | Vercel logo | Low | Remove from public folder | | 5 | `src/components/Avatar.tsx` | 7 | Library default | Generic user icon | Medium | Design custom fallback | | 6 | `src/app/layout.tsx` | 15 | OG image | `og-image.png` (framework default) | Critical | Replace with branded OG image | | 7 | `public/images/hero-bg.jpg` | - | Stock photo | Unpurchased stock (watermark visible) | High | Replace with licensed image | | 8 | `src/components/ProductGrid.tsx` | 23 | Repeated test image | `test-product.jpg` used 6 times | High | Replace with real product images | ### Checklist Items - [ ] **No placeholder image URLs remain** (e.g., `via.placeholder.com`, `picsum.photos`) *Verify:* Run `grep -r "placeholder\|picsum\|dummyimage" .` in codebase. - [ ] **No framework boilerplate images remain** (e.g., `next.svg`, `vercel.svg`) *Verify:* Check `public/` folder for unused default assets. - [ ] **All avatar components have designed fallbacks** *Verify:* Log out and view user avatars; confirm custom empty state, not library default. - [ ] **All card components handle missing images gracefully** *Verify:* Temporarily remove an image prop and confirm a designed placeholder renders. - [ ] **Hero/banner sections use final images** *Verify:* Visually inspect hero on homepage and key landing pages. - [ ] **Product/portfolio grids use unique, real images** *Verify:* Scroll through all grid items; confirm no repeated test images. - [ ] **Logo component uses final logo file** *Verify:* Check header, footer, and favicon for text placeholder or old logo. - [ ] **OG image is a designed asset** *Verify:* Test with Facebook Sharing Debugger and Twitter Card Validator. - [ ] **No stock photo watermarks visible** *Verify:* Manually inspect all images >500kb for watermarks. - [ ] **No images with `lorem` or `test` in alt text** *Verify:* Search codebase for `alt="lorem` or `alt="test`. --- ## 4. SEO & Metadata - [ ] **Page titles are unique and descriptive** *Verify:* Check each page's `<title>` in browser tab; confirm no duplicates. - [ ] **Meta descriptions are written for each page** *Verify:* View source or use SEO extension to confirm meta description exists and is relevant. - [ ] **Open Graph tags for social sharing (test with sharing debugger)** *Verify:* Run URL through Facebook Sharing Debugger and LinkedIn Post Inspector. - [ ] **Robots.txt is configured correctly** *Verify:* Visit `/robots.txt`; confirm it allows desired crawlers and blocks admin routes. - [ ] **Sitemap.xml exists and is submitted** *Verify:* Visit `/sitemap.xml`; confirm it lists all public pages; submit to Google Search Console. - [ ] **Canonical URLs are set** *Verify:* View source on key pages; confirm `<link rel="canonical">` points to correct URL. - [ ] **Structured data / schema markup (if applicable)** *Verify:* Test with Google Rich Results Test for products, articles, or FAQs. --- ## 5. Performance - [ ] **Lighthouse scores meet targets** *Verify:* Run Lighthouse in Chrome DevTools (mobile + desktop); target ≥90 for Performance, Accessibility, SEO. - [ ] **Images are optimized and responsive** *Verify:* Check image sizes (target <200KB for above-the-fold); confirm `srcset` and `sizes` attributes. - [ ] **Fonts are loading efficiently** *Verify:* Check network tab; confirm fonts use `display=swap` and are preloaded if critical. - [ ] **No console errors in production build** *Verify:* Open browser console on live site; confirm zero errors/warnings. - [ ] **Analytics is installed and tracking** *Verify:* Load site and confirm event fires in GA4/Plausible dashboard in real-time view. --- ## 6. Security - [ ] **HTTPS is enforced (no mixed content)** *Verify:* Visit site via `http://` and confirm redirect to `https://`; check console for mixed content warnings. - [ ] **Environment variables are set in production** *Verify:* Confirm all `NEXT_PUBLIC_*` and server-side vars are configured in hosting dashboard. - [ ] **No API keys exposed in frontend code** *Verify:* Search codebase for `sk-`, `api_key`, `secret`; check browser network tab for sensitive headers. - [ ] **Rate limiting on forms (prevent spam)** *Verify:* Submit a form rapidly; confirm throttling or CAPTCHA appears. - [ ] **CORS is configured correctly** *Verify:* Test API calls from the live domain; confirm no CORS errors in console. - [ ] **CSP headers (if applicable)** *Verify:* Check response headers for `Content-Security-Policy`; test with CSP Evaluator. --- ## 7. Cross-Platform - [ ] **Tested on: Chrome, Safari, Firefox (latest)** *Verify:* Manually test key flows on each desktop browser. - [ ] **Tested on: iOS Safari, Android Chrome** *Verify:* Test on real devices or BrowserStack; check touch targets and viewport. - [ ] **Tested at key breakpoints** *Verify:* Resize browser to 320px, 768px, 1024px, 1440px; confirm no horizontal scroll. - [ ] **Print stylesheet (if users might print)** *Verify:* Use `Ctrl+P` on a content page; confirm readable print layout. --- ## 8. Infrastructure - [ ] **Domain is connected and SSL is active** *Verify:* Visit `https://yourdomain.com`; confirm valid SSL certificate (no warnings). - [ ] **Redirects from www/non-www are configured** *Verify:* Visit both `www.yourdomain.com` and `yourdomain.com`; confirm they resolve to one canonical version. - [ ] **404 page is designed (not default)** *Verify:* Visit a non-existent URL; confirm branded 404 with navigation. - [ ] **Error pages are designed (500, maintenance)** *Verify:* Temporarily trigger a server error; confirm branded 500 page. - [ ] **Backups are configured (database, if applicable)** *Verify:* Check hosting dashboard for automated backups; test a restore in staging. - [ ] **Monitoring / uptime check is set up** *Verify:* Confirm UptimeRobot or similar is monitoring the production URL. --- ## 9. Handoff (if client project) - [ ] **Client has access to all accounts (hosting, domain, analytics)** *Verify:* Send credentials via secure password manager; confirm client can log in. - [ ] **Documentation is complete (FORGOKBEY.md or equivalent)** *Verify:* Review docs for setup, deployment, and troubleshooting steps. - [ ] **Training is scheduled or recorded** *Verify:* Confirm training session date or share recorded walkthrough video. - [ ] **Support/maintenance agreement is clear** *Verify:* Signed agreement defines response times, scope, and pricing. --- ## Final Sign-Off - [ ] **All Critical and High severity items resolved** *Verify:* Review placeholder scan table; confirm all Critical/High items have "Action Needed" completed. - [ ] **Stakeholder approval received** *Verify:* Get written sign-off from project owner. - [ ] **Launch date/time confirmed** *Verify:* Coordinate with team on go-live window. --- **Launch Readiness Status:** [ ] Ready to Launch | [ ] Not Ready - Blockers Identified

Connectez-vous pour voir le prompt complet

Continuer avec:

En vous connectant, vous acceptez nos Conditions et Confidentialité

Utilisation

Ce prompt est conçu pour être utilisé avec productivity. Copiez le contenu ci-dessus et collez-le dans votre outil d’IA préféré.

Pour de meilleurs résultats, personnalisez les espaces réservés (indiqués par des crochets ou des majuscules) selon vos besoins.

Références

Catégories :productivity| prompts.chat| pre-launch-checklist| development

Discussion