agentleFS
elevaiteworkselevaiteworks/website-template/.claude/skills/onboard-site/SKILL.md

onboard-site

Skill1 starsChanged 6 months agoMITView on GitHub

5-question pre-flight before a new user starts customizing this website template. Captures site type, target visitor, tone, primary CTA, and 3 reference sites. Writes answers to content/_brief.md so every later edit can refer back to a written declaration of intent. Use when the user opens the template fresh and says "help me get started", "onboard me", "start a new site", "what should I do first", or when CLAUDE.md routes them here.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. PapiScholz/search-visibility-kit★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 11 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If content/_brief.md already exists, ask the user: *"You already have a brief written.

    line 27
  2. Distinctive:

    Before asking questions, check:

    line 33
  3. Very specific:

    Read brand.config.ts so you know the current site name.

    line 35
  4. Very specific:

    Read content/home.md frontmatter so you know what placeholder copy exists.

    line 36
  5. Distinctive:

    Ask one at a time. Wait for each answer before asking the next.

    line 44
  6. Distinctive:

    If the user answers more than one, push back: *"Pick the one that matters most.

    line 70
  7. Distinctive:

    If the user can only name one or two, that's OK — note it in the brief.

    line 78
  8. Distinctive:

    Use Write tool (not Edit) since this is a new file.

    line 115
  9. Very specific:

    If content/ doesn't exist, create it first (it should already exist in this template, but check).

    line 117
  10. Distinctive:

    After writing, show the user:

    line 123
  11. Very specific:

    Wait for their answer. If yes, lead them into brand.config.ts.

    line 136
  12. Distinctive:

    Don't try to write the copy or pick the palette inside this skill.

    line 144
  13. Very specific:

    Don't change brand.config.ts during this skill (that's the next step, not this one)

    line 150
  14. Distinctive:

    Don't suggest reference websites (the user names their own)

    line 151
  15. Distinctive:

    Don't lecture the user about their answers (capture them, write them, move on)

    line 152
  16. Distinctive:

    Don't write a longer brief than the template above (5 sections, no more)

    line 153
  17. Distinctive:

    After the run, check:

    line 159

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboard Site — Pre-Flight Brief

The first thing a new user should do with this template. Five questions, ~5 minutes, output is a single content/_brief.md file that every later skill (match-reference, add-section, add-page) reads as context.

The point: stop people from thrashing on customization before they've declared what they're building. Users who skip this step tend to fiddle with colors for two hours and ship nothing. Users who answer the five questions know what they're building by minute six.


When to use

Trigger phrases:

  • "Onboard me"
  • "Start a new site"
  • "Help me get started with this template"
  • "I just forked this, what now?"
  • "What should I do first?"

Also use when:

  • A content/_brief.md file does NOT exist yet (fresh fork)
  • The user is editing copy or brand config but hasn't named who the visitor is

If content/_brief.md already exists, ask the user: "You already have a brief written. Want me to overwrite it, or keep it?" Default to keep.


Step 1 — Read existing state

Before asking questions, check:

  1. Does content/_brief.md already exist? If yes, surface its contents and ask whether to start fresh.
  2. Read brand.config.ts so you know the current site name.
  3. Read content/home.md frontmatter so you know what placeholder copy exists.

This avoids asking questions the user already answered earlier.


Step 2 — Ask the 5 questions

Ask one at a time. Wait for each answer before asking the next. Don't batch them into a single block — that's overwhelming and people answer poorly.

Q1. What kind of site is this?

Phrasing: "What kind of site are you building? Pick the closest match — personal portfolio, small service business, local business, product or course, event or community, or something else?"

Why this matters: shapes which sections to keep vs delete in content/home.md. A personal portfolio doesn't need a Services list. A local business needs Hours and Location. A product needs Features and Pricing.

Q2. Who is the visitor you're writing for?

Phrasing: "In one sentence — who is the visitor you're writing this site for? Be specific. Not 'small business owners' but 'solo accountants in Brooklyn who hate paperwork' or 'founders who just raised a seed round and need a brand strategy partner'."

Why this matters: every copy decision flows from this. A vague answer here ('anyone interested in X') predicts vague copy later. Push back if the answer is too broad — "Can you narrow that further? Picture one real person."

Q3. What tone?

Phrasing: "How should this site sound? Pick 2-3 words: confident, warm, minimal, bold, playful, expert, friendly, sharp, calm, urgent, anything else that fits."

Why this matters: directly informs copy edits. Two of the same words used as a constraint is enough — "warm + expert" is a different brief than "bold + urgent".

Q4. What's the ONE action you want a visitor to take?

Phrasing: "By the end of a visit, what is the single most important thing you want a visitor to do? Book a call, buy a product, sign up for a newsletter, read a portfolio piece, contact you?"

Why this matters: this is the primary CTA. Every page should funnel toward it. Without naming it, sites end up with 5 equally weighted asks and visitors do none of them.

If the user answers more than one, push back: "Pick the one that matters most. The other things can exist on the site but they're secondary."

Q5. Pick 3 reference sites you love the feel of

Phrasing: "Name three websites you love the feel of. They don't have to be in your industry — you're picking the design vocabulary, not the content. URLs are fine, or take screenshots and drop them into references/."

Why this matters: gives match-reference something to work with later. Three is the magic number — one ref is too narrow, five+ is too diffuse, three forces you to identify a real pattern across them.

If the user can only name one or two, that's OK — note it in the brief. If they name zero, suggest they browse siteinspire.com or land-book.com for 10 minutes and come back.


Step 3 — Write content/_brief.md

Once all 5 answers are in, write a clean markdown file with this structure:

# Site Brief

_Captured: <YYYY-MM-DD> via /onboard-site_

## Site type
<answer to Q1>

## Visitor
<answer to Q2 — verbatim, don't sanitize>

## Tone
<answer to Q3 — 2-3 words>

## Primary action
<answer to Q4 — single CTA>

## References
1. <answer to Q5, item 1>
2. <answer to Q5, item 2>
3. <answer to Q5, item 3>

## Next moves
- Update `brand.config.ts` with site name + reference-inspired palette
- Drop the first reference screenshot into `references/` if you only gave URLs
- Run match-reference against your top reference
- Rewrite `content/home.md` with copy that addresses your Visitor in your Tone, ending with your Primary action

Use Write tool (not Edit) since this is a new file.

If content/ doesn't exist, create it first (it should already exist in this template, but check).


Step 4 — Surface the brief + suggested next move

After writing, show the user:

✓ Wrote content/_brief.md with your answers.

Next moves (in order):
1. Update brand.config.ts → set name to "<their site name>" and pick palette inspired by reference #1
2. Run match-reference on your top reference (drop the screenshot in references/ if you only gave a URL)
3. Rewrite content/home.md addressing the visitor you named

Want me to start with #1 right now?

Wait for their answer. If yes, lead them into brand.config.ts. If no, stop — they'll come back when ready.


Honest limits

This skill doesn't replace having taste or judgment. It surfaces gaps in the user's own thinking. If their Q2 answer is vague, the brief reflects that — don't pad it. A vague brief is honest signal that the user should think more before building.

Don't try to write the copy or pick the palette inside this skill. That's later work, handled by separate skills. This one is declaration only.


Out of scope

  • Don't change brand.config.ts during this skill (that's the next step, not this one)
  • Don't suggest reference websites (the user names their own)
  • Don't lecture the user about their answers (capture them, write them, move on)
  • Don't write a longer brief than the template above (5 sections, no more)

Self-improvement loop

After the run, check:

  • Did the user push back hard on any question? If yes, note which one — phrasing might need a polish
  • Did they answer Q2 (visitor) vaguely after one prompt? If yes, the push-back phrasing needs work
  • Did content/_brief.md get written and never opened again? That's a sign the brief isn't load-bearing — should be referenced by match-reference + add-section skills explicitly

Surface notes at the end of the run; don't edit this skill mid-run.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.