Individual skill

design-led-website-builder

Turn a thin brief (who, why, what to show) into a distinctive researched website. If the brief could mean more than one product, ask once to lock intent and wait. Then research matching live sites, hunt licensed or generated materials (textures, open art, editorial photos — not fake portraits), and build. Skip the ask when the job, a style, a URL/screenshot, or a brand already settles it. Use for new sites and redesigns, not bug fixes or copy edits.

skills/design-led-website-builder/SKILL.md

Read pinned source

Source commit 19e42a49fbb18bfe496e7d2950754d9d7d68904f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
251
Repository last updated
Oct 15, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Design Led Website Builder

A short brief is enough. **Lock intent, wait, research that job, hunt materials, then build.** Ask at most once.

Typical input: who they are, why the site exists, what it must show. Also accept a brand kit, a named style, a reference URL, or a screenshot.

This document is English. Talk to the user in their language. Ask_user options follow the user's language.

People arrive differently. Some bring a brand. Some bring a name and a few pieces of content. Same pipeline; different raw material. Read [intake](references/intake.md).

## Pipeline (do not reorder)

1. **Ingest** the brief and notice the raw material (brand / no brand / a reference).
2. **Lock intent before any research.** If the brief can mean more than one product, send **one** `ask_user` round and **stop** until they reply. If intent is already singular, skip.
Back to top