site-brief
Skill0 starsChanged 47 days agoMITView on GitHub
Interview a business owner and turn the answers into the site's content files (business.json, menu or services, page copy). Use at the start of a new site, or when the owner says "set up my website", "here's my business", or pastes notes about their business.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-pageSkill
- seo-checkupSkill
- seo-researchSkill
- site-careSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Gather what the owner already has: Ask them to paste anything useful: an old website URL, a Google Business profile, a menu or price list, …
- Distinctive: line 27
Leave gaps visible: If a page needs something you don't have, stop and ask.
- Very specific: line 29
Run npm run check, fix anything it flags, then summarize for the owner: what you filled in, what you still need from them, and the next …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Site brief
This is the "type a prompt, get a website" moment from tools like Lovable, done properly: the agent asks for real facts first, so nothing on the site is invented.
Steps
- Gather what the owner already has. Ask them to paste anything useful: an old website URL, a Google Business profile, a menu or price list, an "about us" paragraph, photos. If there's an old site, read it (read-only) and pull facts from it.
- Ask only for what's missing, in one short list, not one question at a time:
- Business name, phone, email, street address, and time zone
- Hours for each day (and which days they're closed)
- What they sell or offer, with prices if they publish them
- Who it's for, and what makes them different, in their words
- Two or three websites they like the feel of
- Write the facts into
content/business.json(hours as 24-hour"HH:MM") and offerings intocontent/menu.json(or a services file if it's not a food business). - Draft page copy in
content/pages/*.mdusing only what the owner told you. Keep their voice: short, specific, warm. Each page needs atitle(65 characters or fewer) and adescription(70–165 characters) in the front matter. - Leave gaps visible. If a page needs something you don't have, stop and ask. Never fill space with invented reviews, awards, years in business, or statistics.
- Run
npm run check, fix anything it flags, then summarize for the owner: what you filled in, what you still need from them, and the next step (thebuild-pageskill for design, orseo-researchto find what customers search for).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.