Who it is forA developer or founder with an existing site who wants a stronger visual design and a pre-launch quality check.
The problemA working landing page often looks generic, and checking every breakpoint and reduced motion state by hand takes time.
The outcomeA redesigned page in the project, a DESIGN.md design system, real-browser screenshots, and a score from the same blind critic used by /awwwards.
What you need first
- Node 22.20+ for the skills CLI (helper scripts need Node 20+)
- An agent that supports skills, such as Claude Code, Codex, Cursor or Gemini CLI
- A model that can read images, so the QA loop can check its own screenshots
- Playwright and a Chromium browser (the skills install them when needed)
- A Vercel, Netlify or Cloudflare account only if you want the site deployed
Steps
- Run
npx skills add juliobsz/skills -gin a terminal. - Open a new agent session inside your project folder.
- Type
/awwwardsand ask: redesign this landing page so it could win site of the day. - If the agent reports Playwright missing, run
npm i -D playwrightin the project, thennpx playwright install chromiumonce. - Review the new screenshots and the DESIGN.md before accepting the changes.
Prompt for your agent
Using the juliobsz/skills repo, run /awwwards inside <project folder> to redesign the landing page at <page path>. Expect updated page files, a DESIGN.md and screenshots for desktop, mobile and reduced motion. Verify that the production build still succeeds before you report the redesign as complete.
Caveat. The README says the skill installs Playwright as a dev dependency in your project, so expect changes to package.json, and the 1 hour figure is an estimate.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page