Skip to content
Skills Library
Programming · Building & coding

frontend-implementation

/frontend-implementation

Use when converting a design direction into maintainable production frontend code, selecting architecture within the existing stack, implementing semantics, assets, loading behavior, CSS/layout, components, and progressive enhancement.

Licence
MIT
Last repository change
27.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when converting a design direction into maintainable production frontend code, selecting architecture within the existing stack, implementing semantics, assets, loading behavior, CSS/layout, components, and progressive enhancement.

Original author description

Use when converting a design direction into maintainable production frontend code, selecting architecture within the existing stack, implementing semantics, assets, loading behavior, CSS/layout, components, and progressive enhancement.

How it works

  1. Preserve context
  2. Build order
  3. Engineering rules
  4. Visual fidelity
Original SKILL.md headings · 33 lines, 181 words
SKILL.md preview
---
name: frontend-implementation
description: Use when converting a design direction into maintainable production frontend code, selecting architecture within the existing stack, implementing semantics, assets, loading behavior, CSS/layout, components, and progressive enhancement.
metadata:
  short-description: Implement art direction as maintainable frontend code
---

# Frontend Implementation

## Preserve context

Inspect the repository before changing frameworks, routing, styling strategy or component foundations. Extend the existing stack unless a change has a clear user/maintenance benefit.

## Build order

1. semantic document and information hierarchy;
2. responsive layout primitives;
3. design-system tokens;
4. functional states/interactions;
5. imagery/media loading;
6. motion/creative enhancement;
7. QA instrumentation.

## Engineering rules

- Prefer semantic HTML and native controls before recreating them.
- Keep component boundaries aligned to behavior/content responsibility, not every visual box.
- Use CSS Grid/Flex and fluid values before breakpoint proliferation.
- Reserve dimensions/aspect ratios for media to avoid layout shift.
- Subset/preload fonts intentionally; avoid loading families/weights not used.
- Keep server/client boundaries narrow in frameworks that support them.
- Lazy-load noncritical animation/3D code.
- Avoid global event listeners and per-frame React state updates for visual animation.
- Remove dead experimentation code and unused packages before release.

## Visual fidelity

Do not “fix” a difficult art direction by reverting to standard cards. If a composition is hard to implement, solve the layout constraint or explicitly negotiate the tradeoff.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named frontend-implementation.

Database snapshot: 13.11.2026 · package version 1fdc170dc3e2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85prism
    Frontend engineer — UI components, dashboards, design system implementation, and frontend audits. Use when asked to "build this UI component", "audit the frontend", "implement the design system", or "build a dashboard".
  • 90team-shinchan:frontend
    Use when you need frontend development for UI components, React, CSS, or styling.
  • 80Frontend CSS
    Write maintainable CSS following the project's established methodology, whether using Tailwind utility classes, BEM naming, CSS modules, or styled-components. Use this skill when styling UI components or pages with CSS, applying design system tokens for colors and spacing, or…
  • 100senior-frontend
    Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
  • 100senior-frontend
    Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
  • 100senior-frontend
    Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.