taste-skill: An Agent Skill that helps coding agents build professional company websites instead of generic landing pages.
What problem it solves
Coding agents tend to assemble generic landing pages rather than distinctive company websites. The skill addresses this by fixing a page system (one section per screen, equal edges, one design system), dealing art direction such as palettes, type pairings and hero layouts, using real photographs, brand icons and product UI, and verifying the result in a real browser.
Key features
One page system and dealt design tokens — Each build starts from a shared starter with one section per screen and equal left and right edges, and the palette, Google Fonts pairing and hero layout are dealt at random so no two pages look alike.
Source: README, assets
Real photographs, icons and product UI — Photographs come from a vetted library and are credited in one footer line, brand and interface icons are resolved into local SVG files, and software pages show rewritten HTML UI fragments and diagrams.
Source: README, examples/v2/CREDITS.md
Effects reserved for tech and gaming — Shader grounds, creative moments, scroll scenes and procedural 3D prints are dealt only for software, tech and gaming pages within a four-context WebGL cap, with static fallbacks for phones and reduced motion.
Source: README
Browser-based verification — A checker renders the built page in headless Chrome over HTTP at four widths and flags empty visuals, broken shaders, contrast drops, misaligned columns, placeholder text and slow-network image gaps.
Source: README
Plain Node scripts with no API keys — Everything in the skill folder is a Node 22+ script that installs nothing and needs no API keys; bundled Wikimedia Commons photographs work offline, while extra photographs and icons use network access.
Source: README
Quick start
Copied verbatim from the project's README.
npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend"Who it may suit
Inference: may suit developers and designers who ask coding agents to build or redesign company websites and want deterministic art direction and a browser-checked result.
Topics to discuss
Which page kinds (software, tech, gaming, product, service, place) still need the most art-direction rules?
How should the checker decide when a shader or scroll moment is appropriate for a page?
What would you want the four-context WebGL budget to look like for heavy pages?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/Leonxlnx/taste-skill#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…