search-docs

Search Lexsis Documentation

Search documentation, skill knowledge, island patterns, and industry guidance via the MCP.

When to Use

• Before generating: look up island props, variant names, content schemas
• For vertical/industry patterns: "beauty hero patterns", "supplements trust signals"
• For conversion techniques: "urgency patterns", "social proof placement"
• For workflow steps: "how to publish", "A/B test setup"
• For troubleshooting: "island not rendering", "publish fails"
• When unsure which island to use for a UI pattern

Workflow

1. Call lexsis_support with action search_docs and the user's query (or your own lookup query)
2. If results include a resource URI, read that exact URI for full content.
3. If results reference an island, read vibe://catalog/islands/{name} for selection guidance. Once selected, read vibe://schema/island/{name} for exact props and source-format markup.
4. Synthesize relevant findings — don't dump raw results, extract what's actionable

Live MCP resources are authoritative. For island contracts, use vibe://schema/island/{name} first, bundled storefront-engine/references/islands/{slug}/schema.json second, and prose examples last.

Tool Usage

Primary search

{
  "name": "lexsis_support",
  "arguments": {
    "action": "search_docs",
    "args": { "query": "<search terms>", "limit": 5 }
  }
}

Narrow by category

Use category to focus results:

• islands — interactive component schemas, props, variants
• tools — MCP tool documentation and parameters
• recipes — end-to-end workflows (ad-to-page, A/B testing, brand setup)
• vibe-page — page schema, theming, animations, publishing
• skills — conversion psychology, craft guide, generation protocols, verticals
• verticals — industry-specific patterns (beauty, supplements, fashion, food, home, luxury)
• troubleshooting — common issues and fixes
• getting-started — setup, auth, quickstart
• resources — MCP resources reference

Deep-read a result

Use only a resource URI returned by lexsis_support action search_docs. Do not invent a resource name or rely on a hard-coded catalog: the search result is the authoritative availability check.

Deep-read an island

Read resource URI: vibe://catalog/islands/{islandName} Returns selection guidance, variants, behavior, and styling surface. Then read vibe://schema/island/{islandName} for the exact prop contract and <lx-island> source example.

Examples

User asks	Search call	Follow-up
"How does BuyBox work?"	lexsis_support.search_docs({ query: "BuyBox", category: "islands" })	Read vibe://catalog/islands/BuyBox
"Beauty landing page patterns"	lexsis_support.search_docs({ query: "beauty landing page", category: "verticals" })	Read the returned resource URI
"Countdown urgency techniques"	lexsis_support.search_docs({ query: "countdown urgency scarcity" })	—
"Publishing workflow"	lexsis_support.search_docs({ query: "publish page workflow", category: "recipes" })	Read the returned resource URI
"What islands handle reviews?"	lexsis_support.search_docs({ query: "reviews testimonials", category: "islands" })	Read vibe://catalog/islands/ReviewCarousel

Tips

• Use specific terms, not vague questions — "BuyBox variant swatches" not "how to show products"
• Combine category filter with query for best results
• If search returns nothing, try broader terms or drop the category filter
• Skill resources contain full implementation guides — always read them when referenced

Optional Follow-Up

This skill can end after returning the concise answer. Its findings can inform any workflow the user explicitly chooses, including visual-page, plan-page, asset-prep, generate, optimize, experiment, cart, or publish.