{"id":77642,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:27.041Z","digest":"891449f74dd968cd23f817ba1175519dd91615dd9471d466fdecf0720ba2a178","against":null,"payload":{"description":"Build or redesign responsive marketing sites, landing pages, portfolios and editorial websites with a distinctive visual hierarchy, genuine content and browser verification.","included_files":[],"name":"build-website","skill_md_contents":"---\nname: build-website\ndescription: Build or redesign responsive marketing sites, landing pages, portfolios and editorial websites with a distinctive visual hierarchy, genuine content and browser verification.\n---\n\n# Build Website\n\n1. Distinguish informational sites from authenticated apps; do not wrap an app in an unnecessary marketing homepage.\n2. Review `../../references/design-quality.md`, `../../references/web-and-pwa.md` and chosen design references. Preserve supplied copy, sections, branding and factual claims; ask only for blocking assets.\n3. Choose an appropriate static/SSR framework based on existing project, SEO, editorial needs and content management. Avoid imposing Next.js on a simple static site.\n4. Implement semantic structure, navigation, functional forms/links, responsive grids, responsive images, safe typography and sensible performance budgets. Generated visuals require asset authorization and actual generation tools.\n5. Run build/lint/tests, check mobile and desktop layout and keyboard navigation, inspect hero/section continuity and interaction states. Never claim browser inspection without captured evidence.\n6. Deliver runnable source, previews where available and test/visual findings. No automatic publish.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}