replit-qualitylisted

Quality, UX/QA, and debugging reference for Replit React + Vite + Express apps. Covers two needs. Pre-ship UX behavior rules and a pre-delivery QA checklist for websites built in Replit (navigation, loading, mobile, forms, links, accessibility, visual consistency, deployment). And post-ship debugging patterns and fixes (SSR/hydration, meta tags, server stability, build/deploy, CSS, layout, routing, performance, email, PDF, image handling, OG/social, analytics, database, component patterns). Living document updated as new Replit-specific issues surface. Invoke when building or QAing a Replit website, running a pre-delivery checklist, or debugging a recurring bug in a React + Vite + Express Replit project.
donatassimkus/claude-ai-skills · ★ 1 · Web & Frontend · score 77

Install: claude install-skill donatassimkus/claude-ai-skills

Two halves. Pre-ship UX & QA validation comes first: the UX behavior rules and the pre-delivery checklist you run before presenting any finished Replit website. Debugging-by-pattern comes second: a reference of recurring bugs, root causes, and fixes across React + Vite + Express Replit projects, organized by category. Use the first half while building and before delivery. Use the second half when something breaks. For any new content-heavy, SEO-focused website on Replit, the recommended stack is React + Vite + TypeScript + Tailwind. Write a short project-specific stack-and-SEO document up front (the chosen stack, the SEO infrastructure the site needs, and the performance targets) and attach it to the first Replit prompt, so the build starts from your standards rather than the platform's defaults. --- ## Pre-ship UX & QA checklist ### Website UX Rules These are the UX rules for the website. Follow all "Always Apply" rules on every page. Follow "Check When Relevant" rules when the context applies. If additional instruction files are provided for design, SEO, or conversion, follow those as well. If no additional files are provided, this section is the complete set of rules. --- ### Always Apply: Navigation Behavior - Every page navigation scrolls to the top of the new page. Users expect to start at the top, not land halfway down. - The back button works as expected. It returns to the previous page, not to some internal app state. - Every internal link can be opened in a