{
  "note": "Platform knowledge split by the path the task takes. Start with vizen-start: it reads the key passport and asks the three questions that decide the rest — and question 0 before them: a finished site, template or export already exists? Then vizen-transfer moves it as it is. Each skill states the cost of its own path and links to the neighbouring one.",
  "skills": [
    {
      "name": "vizen-catalog",
      "description": "Read and fill a Vizen catalogue through a token — products, categories, filters, images and the resizer, plus what a shop's data can silently fail to tell you. Use before building any page that shows real goods.",
      "url": "https://api.vizen.shop/docs/skill/vizen-catalog"
    },
    {
      "name": "vizen-chrome",
      "description": "Build a Vizen shop's header, menu and footer — configure the platform chrome widgets or replace them with your own markup, assemble a second chrome group, bind it to one section or to a LAYOUT (theme) without touching the rest of the shop, dress the system pages (cart, checkout, account), make a custom header stick, and replace the bundled product card.",
      "url": "https://api.vizen.shop/docs/skill/vizen-chrome"
    },
    {
      "name": "vizen-own-markup",
      "description": "Write your own HTML, CSS and JS into a Vizen shop — vz- keys and substitutions, isolation levels, what the block wrapper does to your layout, images through the resizer, live catalogue data in your own markup, modals and dropdowns, and the component with parameters when the same markup has to stand on many pages. Use when the task asks for a unique design rather than platform widgets.",
      "url": "https://api.vizen.shop/docs/skill/vizen-own-markup"
    },
    {
      "name": "vizen-start",
      "description": "Entry point for building a Vizen shop through a personal API token — read the key passport, learn the map, and pick the right path BEFORE writing anything. Invoke first for any task touching /content-blocks, /html-documents, /design/bindings, categories or products. Question 0 — a finished site, template or export already exists? — routes to vizen-transfer; the rest to vizen-widgets, vizen-own-markup, vizen-chrome, vizen-catalog and vizen-troubleshoot.",
      "url": "https://api.vizen.shop/docs/skill/vizen-start"
    },
    {
      "name": "vizen-transfer",
      "description": "Move a FINISHED site or template — an HTML/CSS/JS folder, a static React/Vite export, a Figma/Webflow/Tilda export — into a Vizen shop through a personal token as it is: folder = level-3 widget in real page DOM, one command per folder, scripts and position:fixed work, no rebuild, no Shadow DOM. Layout folder, header/footer, pages, product/category templates, live-data re-binding, the check. Invoke when the task says transfer, migrate, \"we already have a site\", or hands you a folder, ZIP or repo.",
      "url": "https://api.vizen.shop/docs/skill/vizen-transfer"
    },
    {
      "name": "vizen-troubleshoot",
      "description": "Diagnose Vizen storefront problems where the API answered 200 but nothing changed on the site — silently ignored props, filters without the filter. prefix, clipped dropdowns, a header that will not stick, two product cards on one page. Also holds the acceptance checklist for any storefront change.",
      "url": "https://api.vizen.shop/docs/skill/vizen-troubleshoot"
    },
    {
      "name": "vizen-widgets",
      "description": "Configure Vizen's built-in blocks — header, menu, footer, product listing, product card, covers, cards, slideshow — through their props, and know where their limits are. Use when the shop should look tidy and branded rather than fully bespoke, or when live catalogue data matters more than a custom design.",
      "url": "https://api.vizen.shop/docs/skill/vizen-widgets"
    }
  ]
}