tasteskill v2.1 builds the screens people work in, not only the pages they read, and keeps every page's frame clean.
Install or upgrade
npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend"The install name did not change. Needs Node 22+ and Chrome, Edge or Chromium. Installs nothing, uses no API keys.
What is new
- Dashboards and app screens. The skill tells a page from an app screen. An app screen gets its own run: a style dealt from seven styles distilled from real product screens, a face taken from the brief, a shell, real data that adds up, charts that annotate what happened, every state, and its own checks (
inspect.mjs --app). Ships withassets/app.cssandassets/charts.js. - Product pages that show their app build those screens by the same rules, so the hero's screenshot looks like a working product, not grey bars.
- The frame of a page. The inspector now fails the things readers name first when a page looks wrong: no clear title, margins that do not match, a section shoved to one side with half the screen empty, random blank stretches, untitled sections, text against the edge, a title that is not readable 1.2 s after load.
- A study of the latest 100 Awwwards Sites of the Day: where pictures and footage go, how strong pages move (measured curves, durations, ten recipes), empty space and the frame.
- The scroll-scene engine: a sticky stage scrubbed by native scroll (GSAP ScrollTrigger, optional Lenis),
scripts/scenes.mjsto photograph a scene at every point of its scroll, andinspect.mjs --film. The library of tested scenes follows in v2.2.
Four blind test rounds on dashboards: round 1 lost to building without the skill (6.7 against 6.8 and 7.1); after the fixes, rounds 2 to 4 averaged 7.2 to 7.3 on the same and on unseen briefs.
Full notes: CHANGELOG.md