Menu
First-run onboarding for a new project. Scans for unfilled {CONFIGURE:} placeholders, asks project-specific questions, fills them in, and logs decisions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.
Open two files side by side in VSCodium diff view. Use when comparing original vs modified, before vs after, or any two files.
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
| name | onboard |
| description | First-run onboarding for a new project. Scans for unfilled {CONFIGURE:} placeholders, asks project-specific questions, fills them in, and logs decisions. |
Interactive onboarding that customizes the framework for a specific project.
python .claude/skills/onboard/scripts/scan-placeholders.py exits with code 1python .claude/skills/onboard/scripts/scan-placeholders.py --json
Parse the JSON output. This gives you every {CONFIGURE:} placeholder
with its file, line number, and tier (core or optional).
Present questions one category at a time. Confirm each before moving on.
Category 1 — Core (AGENTS.md) — cannot skip:
Category 2 — Agents — cannot skip:
content-editor.mdfullstack-engineer.mdCategory 3 — Testing (test-strategy) — can skip:
If user skips: replace each {CONFIGURE:} with [Not applicable].
Category 4 — Translation (translator) — can skip:
{CONFIGURE:} with [Not applicable]. Done.For each answer, use the Edit tool to replace {CONFIGURE: ...} with
the actual value. The replacement must NOT contain {CONFIGURE: — that's
how the scan knows it's been filled.
Set initiative health to "On Track", last updated to current date
(from python .claude/scripts/now.py), and active work to a brief
summary of the initiative.
python .claude/skills/onboard/scripts/scan-placeholders.py
Expected: "All placeholders filled." Exit code 0.
If placeholders remain, show the user what's left and ask if they want to fill or skip each one.
echo "configured" > .claude/.onboarded
This prevents the SessionStart hook from running the scan on future sessions.
python .claude/skills/workflow/scripts/log-entry.py \
--event "Onboarding complete" \
--summary "Framework configured for {project name}" \
--what-changed "Filled {N} placeholders, skipped {M}" \
--status-update "Onboarding: complete"