AI Skill Report Card

Crafting Modern Websites

A-80·Nov 19, 2026·Source: Web
Markdown
--- name: crafting-modern-websites description: Creates, fixes, and improves websites and web pages with professional, modern design standards, proactively suggesting all necessary improvements and edits to maximize visual appeal, usability, and efficiency. Use when a user asks to build a new site/page, repair a broken one, or enhance an existing web project's design and performance. --- # Crafting Modern Websites
14 / 15

When given a web project request, immediately:

  1. Restate the page/site goal and target audience in one line.
  2. Deliver complete, working files (HTML/CSS/JS or framework equivalent) — fully connected, no missing pieces.
  3. Apply a modern design by default: clean layout, good whitespace, readable typography, consistent color palette, responsive behavior, and subtle interactions (hover states, smooth transitions).
  4. End with a Suggested Improvements section listing concrete design, UX, performance, and SEO upgrades.

No long preamble. Choose sensible modern defaults instead of asking many questions.

Recommendation▾
Add a concrete before/after code snippet example instead of only prose descriptions of outputs
13 / 15
  • Identify the type of request: new build, bug fix, or enhancement of existing code.
  • If fixing/editing: locate the broken or weak part first, explain the root cause briefly, then provide the corrected full file(s) — not just a diff snippet, unless the file is very large.
  • If building new: pick a modern stack by default (semantic HTML5 + CSS3/Flexbox/Grid + vanilla JS, or React/Tailwind if the project implies a larger app) and state the choice.
  • Ensure responsiveness (mobile-first breakpoints) and accessibility (alt text, contrast, semantic tags, keyboard navigation).
  • Optimize for performance: minimize render-blocking resources, lazy-load images, compress/avoid heavy unused libraries.
  • Add on-page SEO basics: title, meta description, Open Graph tags, proper heading hierarchy.
  • Verify all links, imports, and asset paths are consistent across delivered files.
  • Write the Suggested Improvements section: cover visual design, UX flow, performance, SEO, and conversion/engagement (CTAs, forms, load speed).
Recommendation▾
Include a bad-output example to contrast with good practices
15 / 20

Example 1

Input: "Build me a restaurant landing page, make it modern and eye-catching"

Output: Complete index.html, style.css, and script.js (or single-file if small) with a hero section, menu highlights, image gallery, testimonials, reservation/contact form, modern color palette and font pairing, mobile-responsive layout, smooth scroll/hover animations. Followed by a Suggested Improvements list: adding online ordering integration, optimizing images (WebP), adding schema markup for local SEO, A/B testing the CTA button color/placement.

Example 2

Input: "My site is slow and looks outdated, fix it"

Output: Review provided code structurally, identify issues (e.g., outdated table-based layout, unminified large images, inline styles, no responsive meta tag). Deliver the corrected, modernized files (semantic layout, CSS Grid/Flexbox, compressed/responsive images, mobile viewport meta tag). Explain briefly what was wrong and what changed. Followed by Suggested Improvements: enabling browser caching, adding a CDN, converting to a modern font stack, improving Core Web Vitals.

Recommendation▾
Provide a brief checklist or template for the 'Suggested Improvements' section format to ensure consistency across runs
  • Default to a modern visual style: generous whitespace, legible font pairs (e.g., a strong display font + clean body font), consistent spacing scale, accessible color contrast, rounded/soft UI elements where appropriate, subtle micro-interactions.
  • Always deliver mobile-first, fully responsive layouts.
  • Keep code modular and organized (separate CSS/JS files for anything beyond a trivial page).
  • Always include the Suggested Improvements section — this is the key differentiator the user expects every time, regardless of request size.
  • Match the user's language in explanations; keep code, class names, and comments in English.
  • State assumed stack/tools briefly instead of asking (e.g., "Assuming plain HTML/CSS/JS since no framework was specified").
  • Prioritize real improvements relevant to the specific page's purpose (landing page → conversion; blog → readability/SEO; portfolio → visual showcase/performance).
  • Do not deliver outdated patterns (table layouts, inline <font> tags, non-responsive fixed-width pages) unless explicitly requested.
  • Do not give generic, copy-paste design advice unrelated to the actual page content or purpose.
  • Do not provide partial/broken snippets when fixing code — deliver the complete corrected file(s).
  • Do not skip the Suggested Improvements section, even for small edits.
  • Do not over-explain basic HTML/CSS concepts; focus on decisions and recommendations.
  • Do not ignore accessibility and performance in favor of visuals only — a "modern" site must also be fast and usable.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
13/15
Examples
15/20
Completeness
17/20
Format
15/15
Conciseness
13/15