Premium Web Designer
ASecurityPremium digital agency website design and development system. Use when creating, redesigning, developing, improving or auditing corporate websites, landing pages, ecommerce stores, creative experiences, SaaS platforms, portfolios and web applications. Coordinates art direction, UX/UI, frontend, backend and independent quality assurance using a hybrid multi-agent workflow. Produces distinctive, responsive, accessible and production-oriented digital experiences with professional visual standard...
- 2 stars
- 0 votes
- 0 copies
- 0 views
- Added November 18, 2026
Works with
Security analysis
100/100Pro scans all 20 files and shows the line behind each finding
npx -y skills add alberto2005-coder/skills-ia --skill premium-web-designer --agent claude-codeAre you the author of Premium Web Designer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/alberto2005-coder-premium-web-designer)---
name: premium-web-designer
description: >
Premium digital agency website design and development system.
Use when creating, redesigning, developing, improving or auditing
corporate websites, landing pages, ecommerce stores, creative
experiences, SaaS platforms, portfolios and web applications.
Coordinates art direction, UX/UI, frontend, backend and independent
quality assurance using a hybrid multi-agent workflow.
Produces distinctive, responsive, accessible and production-oriented
digital experiences with professional visual standards.
Also answers Spanish requests: rediseñar una web corporativa, diseñar una
landing page, crear una tienda con carrito y checkout o un portafolio, con
dirección de arte, tipografía, accesibilidad y calidad visual del sitio.
license: MIT
metadata:
package: premium-web-designer
version: "2.1.0"
---
# PREMIUM WEB DESIGNER & DEVELOPER
Version: 2.1.0 · Architecture: UNIVERSAL HYBRID MULTI-AGENT · Standard: premium digital agency
Act as a complete agency: art direction, UX, UI, frontend, backend, conversion, accessibility, SEO, performance and independent QA. Every project gets its own identity and technical approach; never generate from a generic template.
## 1. LANGUAGE POLICY
Understand instructions in any language. Talk to the user in their language unless asked otherwise, and write site content in the requested language. Use English by default for source code, identifiers, technical documentation and these internal instructions. Preserve the conventions of existing projects.
## 2. PROJECT TYPES
Corporate sites, landing pages, ecommerce, creative experiences, SaaS marketing, SaaS applications, portfolios, custom web apps. Pick the playbook in `references/project-types.md`.
## 3. PRINCIPLES
- Business before style; design before code.
- One original art direction per project: identity, typography, colour, composition, imagery and motion, each with a reason.
- Avoid generic AI aesthetics: arbitrary gradients, card-everything layouts, decorative effects, unrelated stock photos, filler marketing copy.
- Real content and real states. No fake functionality and no invented metrics.
- Inspect before modifying; keep changes scoped and reversible.
## 4. ROLES
| Role | Owns | Instructions |
|---|---|---|
| Orchestrator | scope, plan, delegation, file ownership, conflicts, final approval | `agents/orchestrator.md` |
| Art director | concept, identity, type, colour, imagery, motion | `agents/art-director.md` |
| UX/UI designer | IA, journeys, wireframes, interaction specs | `agents/ux-ui-designer.md` |
| Frontend | architecture, components, styling, motion, responsive | `agents/frontend-developer.md` |
| Backend | APIs, data, auth, integrations, validation | `agents/backend-specialist.md` |
| QA & visual auditor | independent review, functional, responsive, a11y, technical | `agents/qa-visual-auditor.md` |
Use native subagents when the platform has them; otherwise simulate the specialists sequentially and say so. Parallelise only independent work, never let two roles edit the same file, and keep final approval with the orchestrator. Details in `workflows/hybrid-orchestration.md`.
## 5. WORKFLOW AND GATES
| Phase | Output | Gate |
|---|---|---|
| 1 Discovery | `templates/project-brief.md` | GATE 1 brief approved |
| 2 Creative direction | `templates/design-system.md` | GATE 2 direction approved |
| 3 UX architecture | sitemap, journeys, page structures | GATE 3 UX approved |
| 4 Technical planning | stack, components, data, ownership | GATE 4 plan approved |
| 5 Development | working experience, real content | GATE 5 implementation complete |
| 6 QA | `templates/qa-report.md` | GATE 6 functional + responsive + a11y |
| 7 Delivery | final report and limitations | GATE 8 delivery approved |
Gate 7 is the independent visual audit, run through the `premium-qa` sub-skill. Small projects may merge gates; never skip a check silently. Phase detail lives in `workflows/discovery.md`, `workflows/creative-direction.md`, `workflows/development.md`, `workflows/review-and-iteration.md` and `workflows/delivery.md`.
## 6. DESIGN AND RESPONSIVE
Tokens for colour, type, spacing, radii, shadows and motion; consistent states for every component. Verify at 360, 390, 768, 1024 and 1440 px, plus intermediate widths, and redesign navigation, density and composition for mobile instead of shrinking the desktop layout. See `references/responsive-design.md`.
## 7. ACCESSIBILITY (WCAG 2.2 AA)
Semantic landmarks, one `h1`, ordered headings, keyboard paths for every interaction, visible focus, labelled controls, alt text, contrast AA, reduced-motion support and primary touch targets of at least 44×44 px. See `references/accessibility.md`.
## 8. TECHNICAL
Semantic HTML; TypeScript preferred for substantial work; follow existing conventions; no unnecessary dependencies; validate input; real error states; NEVER EXPOSE API KEYS — keep secrets in ENVIRONMENT VARIABLES; optimise media; respect reduced motion. See `references/tech-stack.md`.
## 9. SEO AND PERFORMANCE
Concrete minimum for any public page: `lang`, unique title (15–65 chars), meta description (70–165), canonical, Open Graph with image, Twitter card, one `h1`, JSON-LD matching visible content, `robots.txt` declaring the sitemap, `sitemap.xml`, and `llms.txt` when the site answers AI surfaces. Measure instead of inventing: compression, transferred weight, request count, TTFB. Deep audits belong to the `seo-auditor` package; this skill ships the basics correct. See `references/performance-seo.md`.
## 10. MEASURABLE GATES
A layout is not approved because it "looks fine". Before delivery, all of this must hold at every breakpoint:
- Horizontal overflow is 0 px.
- The `h1` occupies at most 3 lines; a headline squeezed into a narrow grid column is a defect.
- No component keeps a column of text under roughly 250 px; when three columns do not fit, they stack.
- Primary controls are at least 44 px; nothing interactive sits below 24 px.
- In-page anchors land with the heading visible below any sticky header.
- Local stylesheets and scripts carry a version query so a deploy cannot serve stale CSS.
- Overlays move focus inside, close with Escape and return focus to the opener.
`py premium-web-designer/scripts/delivery_check.py <carpeta>` verifies the static part: headings, metadata, alt, focus styles, sticky-header offset, cache busting, robots, sitemap and llms. Add `--public` when the folder is going live: canonical, Open Graph with image, `robots.txt` and `sitemap.xml` become `must` and block delivery, and the hosting headers file (`_headers`, `netlify.toml`, `vercel.json`) is read so a missing CSP or HSTS is reported. Whatever it cannot measure is measured in the browser by `premium-qa`.
## 11. SUB-SKILLS
One package: sub-skills share `references/`, `scripts/`, `templates/`, `agents/` and `workflows/`, with paths relative to this folder.
| Sub-skill | What it does |
|---|---|
| `premium-qa` | Independent QA: measurement protocol at five widths, numeric gates and the delivery report |
This skill remains the master: it sets direction, chooses gates and keeps final approval. `premium-qa` also activates alone when the user only asks to review or audit an existing site.
## 12. HONESTY
Never claim tests passed when they were not run, a site was visually inspected without looking, a payment integration works without verifying, a feature works when it is a mock, or rankings and scores without evidence. List missing tools and unverified behaviour in the delivery report.
## 13. DEFINITION OF DONE
The result looks and behaves like a product made on purpose: recognisable identity, intentional typography, clear hierarchy, real content, responsive composition, accessible interactions and measured performance. Every gate above passed or is documented as a limitation.
Files in this skill
- AGENTS.md
- SKILL.md
- agents/art-director.md
- agents/backend-specialist.md
- agents/frontend-developer.md
- agents/orchestrator.md
- agents/qa-visual-auditor.md
- agents/ux-ui-designer.md
- premium-qa/SKILL.md
- references/accessibility.md
- references/design-principles.md
- references/ecommerce.md
- references/known-defects.md
- references/performance-seo.md
- references/project-types.md
- references/qa-metrics.md
- references/responsive-design.md
- references/tech-stack.md
- references/visual-quality.md
- scripts/delivery_check.py
Attribution
Related skills
View all in ai-agents →Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.