docs

Reviewed 2h ago.

• tools: 5 tools scanned
• metadata: scanned

No findings.

Tools (5)

• list_products

  List the Free Battery Factory products whose documentation is hosted here, each with a one-line blurb, current docs version, and canonical URLs. Presence here means the docs are published, not that the product is in active development — each blurb states its lifecycle. Call this first to discover the valid `product` ids used by the other tools.

• search_docs

  Full-text search across the product documentation. Returns the best-matching pages with title, description, canonical URL, matched section headings, and a snippet. Omit `product` to search every product at once, or pass one of the ids from list_products to scope it.

• get_doc

  Fetch a single documentation page as Markdown, given a product id and a page slug (both come from list_products / search_docs results, or a doc URL like /liteship/overview). Returns the title, description, a heading outline, and the full Markdown body.

• get_llms_full

  Return a link to the complete, source-linked agent reference (llms-full.txt) for a product — its entire prose, API surface, and examples in one document. This file is large, so it is returned as a resource link and canonical URL rather than inlined; use search_docs/get_doc for targeted lookups and this when you want the whole corpus.

• describe_page_dimensions

  Describe the adaptive dimensions of this site's pages: each named layout regime, the states it can occupy, and the signal and thresholds it is carved from. These are the same boundary definitions that emit the page's @container CSS, so this is the page's real state space rather than a description of it. Read-only — no tool here changes the page. Caveat: each dimension's `current` field is an SSR-time fallback (always the first state), NOT the requesting browser's live state — this manifest is compiled once, server-side, with no viewport to read. HOW to find the live state differs per dimension — some have a `data-czap-state` DOM attribute to read, some do not and must be derived from viewport width against the stated thresholds instead — so read each dimension's own `description` rather than assuming one mechanism for all of them.