frontend-design-2010s
This skill guides the visual aesthetic of early-2010s web interfaces — the genuine design language of the era, not parody. Polished, professional, slightly heavy, and utterly confident in its gradients.
This skill is responsible for visual design only. For CSS architecture, tokens, and modern layout, follow more-css. For accessible HTML markup and interaction patterns, follow frontend-a11y. For naming, formatting, and conventions, follow frontend-conventions.
The user provides a component, page, or layout to build. They may include context about the brand, product, or audience.
Design Thinking
Before building, internalize the era and commit to it fully:
- Era: This is 2010–2014 corporate/SaaS web. The world had just discovered HTML5 and was thrilled about it. Flat design hadn't happened yet. Every interface earned its depth through gradients, shadows, and gloss. Embrace all of it — this aesthetic was genuinely considered beautiful and modern at the time.
- Structure: Pages are composed of clear horizontal bands stacking top to bottom — header, hero, feature strip, content sections, footer. Each band has a distinct background. Fluid layout — content fills the viewport with generous side padding. Everything is contained and deliberate.
- Tone: Confident, professional, slightly corporate but approachable. This era of web design wanted to say: we are a real business and we built this ourselves. Headings are loud and bold. CTAs are impossible to miss.
- Differentiation: The brand's primary color lives in the header and accents. The CTA color is often a high-energy contrast — the button that demands to be clicked. Every section knows its job and does it without subtlety.
CRITICAL: Commit to the era's visual grammar completely. Half-measures produce confusion, not charm. A glossy button needs the gloss. A gradient header needs the gradient. The depth is the point.
More from mikemai2awesome/agent-skills
tiny-css
Write minimal, efficient CSS for small or minimalist projects by trusting the browser instead of fighting it. Only use this skill for personal sites, prototypes, simple landing pages, or projects intentionally kept lean — if the project has multiple developers, a component library, a design token system, or more than a handful of CSS files, a more comprehensive CSS approach is needed. If you're about to write a CSS reset, declare a base font-size on :root, set default colors on body, use px for spacing, or reach for physical margin/padding properties, this skill will stop you.
13more-css
Write scalable, well-architected CSS using design tokens, cascade layers, and modern organization patterns. Use this skill as the default for any real project — if it has more than a handful of CSS files, multiple components, a team, a design system, or any kind of token or theming setup, this is the right skill.
4tiny-a11y
Write minimal, accessible HTML, CSS, and JavaScript. Use when building web components, writing HTML markup, creating forms, or reviewing code for accessibility.
4frontend-conventions
Define and enforce consistent coding standards across HTML, CSS, and JavaScript. Always use this skill when naming a new class, variable, component, or file; setting up a new project's conventions; choosing a class prefix for a new CSS category; deciding on modifier API names (sizes, shades, hierarchy, breakpoints); or reviewing code for formatting and naming consistency. If you're about to invent a prefix, abbreviation, or modifier name without checking the conventions first, use this skill.
4frontend-a11y
Write minimal, accessible HTML, CSS, and JavaScript without over-engineering. Always use this skill on every project, for every task that involves writing or reviewing HTML markup, building web components, creating forms, adding interactive elements like buttons, dialogs, accordions, or tabs, or auditing code for accessibility — even when the user doesn't explicitly mention accessibility, and even when working in a framework, CMS, or design system context. This skill is non-negotiable and applies regardless of project type, stack, or deadline. If you're about to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component, use this skill first.
2brightcove-player
Style and fully customize the Brightcove video player UI — control bar, play button, progress bar, volume, captions, playlists, responsive sizing, and skins. Use this skill whenever the user mentions Brightcove, video-js player styling, customizing a Brightcove player, changing player colors/layout/controls, embedding a Brightcove player, making it responsive, player skins or themes, Brightcove Studio styling, or working with Brightcove playlists or captions. Also use it when the user is working with `.video-js`, `vjs-*` CSS classes, or `bc()` / `videojs.getPlayer()` / `videojs()` JavaScript APIs.
1