webbuild
Build professional, distinctive, pitch-ready business websites — including scroll-driven "3D" heroes (AI video scrubbed by scroll), real-time Three.js / React Three Fiber scenes, GSAP + Lenis motion, and treated-video shaders — that do NOT look AI-generated. Covers the brief, reverse-engineering reference sites, design system (type, colour, layout, copy), hero/asset pipeline, performance and accessibility, visual QA with screenshots, a slop linter, deployment, and pitching the site to a local business. Use this whenever the user wants to build, redesign or polish a website or landing page, mentions 3D websites, scroll animations, Awwwards-style or "$10K" sites, Three.js/GSAP/Spline, wants a site "like" another site, wants to rebuild a business's site to pitch or sell it, or complains a site looks generic / like AI slop — even if they don't say "webbuild".
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/harishisonline--webbuild-skill)HTML
<a href="/listings/harishisonline--webbuild-skill"><img src="/api/listings/harishisonline--webbuild-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
git clone https://github.com/Harishisonline/webbuild-skill ~/.claude/skills/webbuild
Restart Claude Code, then ask for a website ("build a premium homepage for the barbershop on my street", "make a 3D landing page for my coffee brand", "this site looks like AI slop, fix it"). The skill triggers on its own. You can also say "use webbuild".
The browser scripts need Playwright once per project:
npm i -D playwright && npx playwright install chromium
`frames.sh` needs ffmpeg (`brew install ffmpeg`). `rea-teardown.sh` needs Google Chrome (or Playwright's Chromium); it fetches REA and a compatible Node through npx on first run.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 173 lines
- ---
- name: webbuild
- description: Build professional, distinctive, pitch-ready business websites — including scroll-driven "3D" heroes (AI video scrubbed by scroll), real-time Three.js / React Three Fiber scenes, GSAP + Lenis motion, and treated-video shaders — that do NOT look AI-generated. Covers the brief, reverse-engineering reference sites, design system (type, colour, layout, copy), hero/asset pipeline, performance and accessibility, visual QA with screenshots, a slop linter, deployment, and pitching the site to a local business. Use this whenever the user wants to build, redesign or polish a website or landing page, mentions 3D websites, scroll animations, Awwwards-style or "$10K" sites, Three.js/GSAP/Spline, wants a site "like" another site, wants to rebuild a business's site to pitch or sell it, or complains a site looks generic / like AI slop — even if they don't say "webbuild".
- ---
- # webbuild
- Make websites a business owner would pay for: specific to *them*, fast on a phone, one
- memorable moment, and nothing that screams "an AI made this". The craft is mostly in the
- choices before code and in looking at the result honestly afterwards.
- Paths below are relative to this skill's folder (`scripts/`, `references/`, `assets/`).
- ## 0. Set up the project (2 min)
- - New site → copy `assets/starter/` into the project folder (plain HTML + CSS + ES modules,
- pinned CDN imports, no build step: deploys anywhere, easy to edit). Use Next.js / Astro / R3F
- only if the user asks or the project already uses them (`references/3d-playbook.md` §5).
- - Existing project → keep its framework, tokens and components; this skill adds direction,
- motion and QA, not a rewrite.
- - Create `BUILD_NOTES.md` in the project. It's the memory across context resets: brief,
- decisions, open questions, fixes that worked.
- ## 1. Brief — get the real business
- Gather (from the user, the business's current site, Google Business Profile, Instagram):
- name, what they sell, where, since when, the **one primary action** (call / book / order /
- quote / visit), real proof (rating + count, years, licences, press), real photos, logo/colours,
- hours, address, phone. Write the 5-line brief from `references/design-system.md` §2 into
- `BUILD_NOTES.md`.
- Never invent facts — fabricated reviews, stats, prices or addresses in a pitch destroy trust
- the moment the owner reads them. Instead:
- - **Write around unknowns** so the demo still reads finished: "Koregaon Park, Pune" instead of
- a made-up street number; "Rated 4.7 on Google" instead of invented quotes; service names
- without prices, or "from ₹…" only if known.
- - Where a fact is genuinely required (phone, exact address, hours), use a visible
- `{{placeholder}}` — `slop_check.py` blocks shipping until it's filled.
- - Put every unknown and assumption on an "Ask the client" list for the final report.
- For a creator or channel site, ask for (or pull) the dashboard numbers and the profile
- picture up front: YouTube Studio / Instagram insights screenshots, plus vidIQ or similar if
- connected. A Results section built from real numbers is what sells it.
- If the brief is thin and the user is around, ask at most 3 questions (business + city,
- primary action, any site they love). If they want you to just go, make sensible assumptions,
- write them down, and keep moving.
- ## 2. Reference (when the user names a site, sends a recording, or wants a "rebuild")
- Follow `references/reverse-engineer.md`: `node scripts/teardown.mjs <url>` measures the stack,
- fonts, palette, media and shader evidence and screenshots the scroll; screen recordings become
- frames you read and turn into a beat-by-beat motion spec. When that quick pass can't explain
- an effect, go deeper with REA's engine: `scripts/rea-teardown.sh <url>` captures the page,
- fingerprints the bundle and exports every script so you can read how it's actually built
- (guides in `references/rea/`). Record OBSERVED → INFERENCE → DECISION. Learn the technique;
- never copy brand, copy, assets or code.
- ## 3. Direction — plan, then attack the plan
- Read `references/design-system.md` (the anti-slop rules — classic *and* the newer
- "tasteful AI" tells like cream + terracotta, ALL-CAPS eyebrows, editorial hairlines). In
- `BUILD_NOTES.md` write:
- - 4–6 named colour tokens taken from the business, type pairing + roles, radius language
- - ASCII wireframe of each section (vary the rhythm — no hero → 3 cards → logos → testimonials)
- - the **signature moment** (exactly one) and why it fits *this* business
- - 3 principles that make it distinctive
- Then review the plan against the tell list and, for each choice that reads as a default,
- justify it for this business or change it. Asking "could this belong to another business if
- I swapped the logo?" catches most problems here, where they're cheap.
- For an undecided direction the user wants to choose, show 2–3 genuinely different directions
- (a still or a quick HTML sketch each) before building — `21st-ui-explore` can help if installed.
- ## 4. Hero — pick the mode that serves the business
- `references/3d-playbook.md` §1 has the decision table. Short version:
- - **still** (great photo/type) — places, food, salons, clinics, services. Often the right call.
- - **video** — atmosphere loop, ideally *treated* with `assets/starter/grade.js` so AI/stock
- footage gets a bespoke grade (grain, halation, lift/gamma/gain, vignette). Pick a LOOK and
- keep it subtle.
- - **frames** — the "$10K 3D website": AI start/end keyframes → first/last-frame video →
- `scripts/frames.sh` → canvas scrubbed by scroll. Read `references/scroll-video-playbook.md`
- for the keyframe rules, prompts and blending.
- - **scene** — live Three.js / R3F when 3D *is* the product story (configurable product,
- architecture, tech). Subject must be the business's thing, never the placeholder knot.
- - **whole page** — when the owner asks for a "3D website", they usually mean 3D throughout,
- not a 3D hero. Use one fixed scene with a camera station per section
- (`references/3d-playbook.md` §6).
- Generate assets with whatever is connected (Higgsfield / Kling / kie.ai / Nano Banana MCPs or
- skills), or ask the user to drop files in. If nothing is available, build with a clearly
- labelled placeholder and list exactly what asset to generate, with the prompt.
- ## 5. Build
- Order: tokens (`styles.css :root`) → semantic HTML sections with real copy → layout at 390px
- and 1440px → hero mode → motion last.
- - Copy rules: `references/design-system.md` §8 (outcome + place + specifics, real CTA verbs,
- banned words).
- - Required for a business site: one obvious CTA above the fold and again at the end, `tel:` /
- booking / form, hours + address + map link, real proof, title + description + OG image,
- LocalBusiness JSON-LD, favicon, sticky call/book bar on mobile when the action is a call.
- - Motion: one signature moment + quiet 150–300 ms micro-feedback; ease-out, never bounce;
- `transform`/`opacity` only; reduced-motion shows end states.
- - Components: search `references/resources.md` registries (21st.dev, React Bits, Aceternity,
- Motion Primitives…) before hand-writing complex effects, then restyle to the tokens. In a
- static site, rebuild React components in vanilla rather than adding React for one effect.
- - Footer: build it to `references/design-system.md` §11 (brand block, link columns with
- platform logos, contact buttons, oversized wordmark, bottom row). Owners judge the whole site
- by it. The small builder credit is already in the starter; the client can ask to remove it.
- - Buttons and scroll: follow `references/design-system.md` §12 (tactile 0.16 s buttons, cursor
- ring via the starter's `cursor.js`, no native scrollbar: the starter's `blockbar.js` replaces it).
- - Before you call it done, reread `references/design-system.md` §10: the things owners still
- call slop after every rule passes.
- ## 6. Look at it — this is where good sites are made
- Serve locally (`npx serve .` or the project's dev server), then:
- 1. `node scripts/shoot.mjs http://localhost:3000 ./shots` — phone / laptop / desktop
- screenshots along the scroll + console errors, overflow, LCP, weight. **Read the PNGs.**
- (Or use the browser pane / Playwright MCP if available.) Also run once with
- `--reduced-motion`.
- 2. `python3 scripts/slop_check.py .` — must end with 0 FAIL. Treat WARNs as questions.
- (`npx impeccable detect` is a good second opinion if installed.)
- 3. Critique honestly against the brief: hierarchy, type, colour, the signature moment, mobile,
- copy specificity. Fix in batches with clear intent ("lower sections feel generic — make
- them more expensive, not busier").
- 4. **Subtract one decorative element** before calling it done.
- Expect 3–6 rounds; nobody one-shots this. Log what fixed what in `BUILD_NOTES.md`.
- ## 7. Ship + pitch
- - Deploy: Vercel / Netlify / Cloudflare Pages / GitHub Pages. **Commit the frames folder**
- (the most common "the hero vanished in production" bug). Add `<meta name="robots"
- content="noindex">` to spec demos until the client buys.
- - If it's a pitch, read `references/pitch-and-sell.md`: before/after video, outreach scripts,
- pricing anchors, the pitch-ready checklist, handover.
- ## Final report to the user
- Keep it short and concrete:
- - What was built (direction in one line, signature moment, hero mode) and where (paths, URL)
- - How to run it (`npx serve .` or the dev command)
- - QA results: slop_check FAIL/WARN counts, shoot.mjs LCP / errors per viewport, what you
- looked at and fixed
- - **Ask the client** list: every `{{placeholder}}` and assumption
- - Assets still to generate (with ready-to-use prompts), if any
- ## Reference map
- | Read | When |
- |---|---|
- | `references/design-system.md` | Always, before choosing colour/type/layout/copy |
- | `references/3d-playbook.md` | Choosing the hero; any Three.js/R3F; performance + a11y budget |
- | `references/scroll-video-playbook.md` | Scroll-scrubbed "3D" hero from AI video |
- | `references/reverse-engineer.md` | A reference site, a recording, or rebuilding a prospect's site |
- | `references/rea/README.md` | Going deeper than teardown.mjs with REA's tools |
- | `references/resources.md` | Component registries, effect tools, inspiration, companion skills |
- | `references/pitch-and-sell.md` | Spec site for a prospect, pricing, outreach, handover |
- | Script | Does |
- |---|---|
- | `scripts/teardown.mjs <url>` | Measure a reference site (stack, fonts, palette, media, shaders, screenshots) |
- | `scripts/rea-teardown.sh <url>` | Deep teardown with REA's engine: page capture, bundle fingerprints, exported scripts |
- | `scripts/frames.sh <video> <out>` | Video → WebP frame sequences (desktop + mobile) + manifest |
- | `scripts/shoot.mjs <url> [out]` | Screenshots at 3 widths along the scroll + errors/LCP/overflow |
- | `scripts/slop_check.py <dir>` | AI-slop + ship-readiness linter (0 FAIL to ship) |
- Playwright for the `.mjs` scripts: `npm i -D playwright && npx playwright install chromium`.
README.md · README · 87 lines
- # webbuild — a Claude Code skill for websites that don't look AI-made
- **webbuild** turns Claude Code into a careful web studio. It builds professional, pitch-ready
- business websites, including scroll-driven "3D" heroes, real-time Three.js scenes, GSAP + Lenis
- motion and treated-video shaders. It then checks its own work so the result doesn't read as
- generic AI output.
- It came out of studying the most-watched 2026 "build $10K websites with Claude Code" tutorials,
- 40 professionally built 3D demo sites, the REA reverse-engineering method, and the current
- anti-slop design guidance (Anthropic's frontend-design skill, Impeccable, Taste Skill). That
- research is condensed into one workflow, four scripts and a starter.
- ## What it does
- 1. **Brief.** Gets the real business: its one primary action and real proof. It never invents reviews or stats.
- 2. **Reference.** `teardown.mjs` measures any site you admire: stack, fonts, palette, media,
- shader uniforms and scroll screenshots. For a deeper look, `rea-teardown.sh` runs
- [REA](https://github.com/morluto/rea)'s browser engine to fingerprint the bundle and export
- every script. You learn the technique without cloning the site.
- 3. **Direction.** Plans named colour tokens, a type pairing, wireframes and one signature
- moment, then reviews that plan against a list of classic and 2026 AI tells.
- 4. **Hero.** Picks one of four modes: still, treated video (WebGL grading shader), scroll-scrubbed frame sequence (the
- "$10K 3D website"), or live Three.js.
- 5. **Build.** A zero-build starter with pinned CDN imports, Lenis, ScrollTrigger, DPR caps and
- reduced-motion and low-power fallbacks.
- 6. **Look.** `shoot.mjs` screenshots phone, laptop and desktop along the scroll and reports
- errors, LCP and overflow. `slop_check.py` lints for AI slop and ship-readiness. It must show 0 FAIL.
- 7. **Ship and pitch.** Deploy notes, outreach scripts, pricing anchors and a pitch-ready checklist.
- ## Install
- ```bash
- git clone https://github.com/Harishisonline/webbuild-skill ~/.claude/skills/webbuild
- ```
- Restart Claude Code, then ask for a website ("build a premium homepage for the barbershop on my
- street", "make a 3D landing page for my coffee brand", "this site looks like AI slop, fix it").
- The skill triggers on its own. You can also say "use webbuild".
- The browser scripts need Playwright once per project:
- ```bash
- npm i -D playwright && npx playwright install chromium
- ```
- `frames.sh` needs ffmpeg (`brew install ffmpeg`). `rea-teardown.sh` needs Google Chrome (or
- Playwright's Chromium); it fetches REA and a compatible Node through npx on first run.
- ## What's inside
- ```
- SKILL.md the workflow Claude follows
- references/
- design-system.md anti-slop rules, type pairings, colour, layout, copy
- 3d-playbook.md hero-mode decision table, Three.js/R3F recipes, perf + a11y budget
- scroll-video-playbook.md keyframes → AI video → frames → scroll scrub, with prompts
- reverse-engineer.md evidence-first teardown of reference sites
- rea/ REA's web reverse-engineering guides (MIT, vendored)
- resources.md 21st.dev, React Bits, Aceternity, GSAP, Spline, inspiration…
- pitch-and-sell.md finding clients, outreach scripts, pricing, handover
- scripts/
- teardown.mjs measure a reference site
- rea-teardown.sh deep teardown with REA's engine (runs via npx)
- frames.sh video → WebP frame sequences + manifest
- shoot.mjs multi-viewport screenshots + errors/LCP/overflow
- slop_check.py AI-slop + ship-readiness linter
- assets/starter/ index.html, styles.css, main.js, scene.js, grade.js
- evals/ test cases (runnable with `claude plugin eval`)
- ```
- ## Credits
- - [REA](https://github.com/morluto/rea) by morluto (MIT): its web guides are vendored in
- `references/rea/` with its license, and `rea-teardown.sh` runs its engine from npm.
- - Design guidance draws on Anthropic's [frontend-design skill](https://github.com/anthropics/skills),
- [Impeccable](https://impeccable.style) and [Taste Skill](https://github.com/Leonxlnx/taste-skill).
- - Technique notes from tutorials by Metics Media, Nate Herk, Jack Roberts, Nick Saraev,
- Chase AI, AI Chris Lee, AyzZ, Komputer Mechanic, MiladiCode and DesignCourse (links in
- `references/scroll-video-playbook.md`).
- - Apart from REA's guides (MIT), no third-party code or assets are copied. `grade.js` is an
- original implementation of the treated-video idea.
- ## Author
- Built by Harish: [LinkedIn](https://www.linkedin.com/in/harishpradhan0131/) · [GitHub](https://github.com/Harishisonline)
- MIT licensed.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.