---
name: pixelforge-team-web-design
description: Adapt the PixelForge reference-inspired HTML template while preserving its layout and working local interactions.
---

# PixelForge Web Design

## Inputs
Read index.html, README.md and ASSETS.md. Obtain the brand, audience, verified content, approved photographs and real primary action.

## Workflow
1. Inspect the existing page and local assets before editing. Preserve the selected reference’s visual language: Midnight blue · electric purple · Poppins.
2. Replace sample names, products, prices, customer counts and testimonials with verified content. Do not manufacture claims.
3. Keep responsive section geometry, native controls, visible focus, meaningful alt text, reduced-motion handling and working local interactions.
4. Treat every supplied photo and brand mark as reference material with rights not independently verified. Replace it with approved imagery before a commercial launch. Preserve OFL and Phosphor MIT notices.
5. Test navigation, mobile layouts, dialogs, validation and empty/reset states. For shops, verify search, category filters, wishlist, quantity changes, removals and calculated totals.
6. Keep demo state transient. Do not claim authentication, payment, email, persistence or real orders without implementing and testing the requested service.
7. Return actual source files, a concise change list, verification results and any remaining integration boundary.

## Boundaries
No account, key, dependency installation or network service is required to open the template. No credentials, deployments or payments are authorized by this workflow. The code is MIT; imagery has separate rights. Installation of this Markdown skill depends on the coding assistant.