agentleFS
awaikawaik/direct-mcp-ai-project/.claude/skills/lidfly-page-migration/SKILL.md

lidfly-page-migration

Skill20 starsChanged 4 days agoMITView on GitHub

Перенести или улучшить существующую страницу в LidFly 1:1 через MCP v3: полный инвентарь секций без сжатия и выдумывания, безопасная работа с существующим design_template_id, полный replacement payload, перенос изображений и посекционная сверка.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the inventory and template-deviation rules below.

    line 18
  2. Very specific:

    If the existing site has an active design_template_id, call lidfly_audit_site_design_template before the first write.

    line 24
  3. Very specific:

    After the page write, compare it with the inventory (step 13).

    line 45
  4. Distinctive:

    Keep the original wording.

    line 62

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

LidFly Page Migration

Use when the user asks to migrate, copy, or recreate an existing page from another platform, or to use it as a reference for improving a managed LidFly page. This workflow supports both a new or empty target and a site that already has pages, content, and an active design template. The goal is a faithful 1:1 transfer: same sections, same order, same content, same visual character. A migration that compresses 12 sections into 5 blocks or invents content the original does not have is a failed migration.

Workflow

For visual analysis and final review, use the creative-page-direction, frontend-page-craft, visual-assets and visual-qa references of lidfly-site-commerce (load that skill, then the needed get_skill_resource paths). Compare desktop and mobile renders of the whole source and target. During a faithful transfer these guides refine implementation and expose defects; they do not authorize new content, a different composition or an unrequested redesign. Keep the inventory and template-deviation rules below.

  1. Fetch the original page HTML and its CSS files (in the built-in LidFly chat, read the source as described in the next section). Identify the platform (WordPress/Elementor, Tilda, Bitrix) to pick the right section markers: Elementor top-level containers use e-parent, Tilda uses t-rec records.
  2. Build a section inventory before writing anything: one line per section, top to bottom, with heading, body summary, image count, button labels, and forms. Number the sections.
  3. Extract design tokens from the CSS: background, text, card, and accent colors by frequency; heading and body font families; card border radius. Note whether the heading font differs from the body font. This is a comparison input, not permission to change the whole site's theme.
  4. Resolve the target with get_provider_context({ provider: "lidfly", query }) and copy only returned tool_args. Before the first write, call lidfly_list_pages. If the target page exists, read it with lidfly_get_page, call lidfly_get_block for every saved block index, and keep the complete page state plus the exact latest publication_revision from that read. If the page is new, use the current site state and creation contract returned by the read tools and current schema; do not invent replacement fields or a revision. Stop if the target is a static artifact, generated Commerce route, or otherwise not editable through managed page tools.
  5. If the existing site has an active design_template_id, call lidfly_audit_site_design_template before the first write. Inspect the applied template, starter block sequence, inheritance, page-local overrides, key features, Commerce readiness, and route conflicts. Explain relevant warnings before proposing the migration write.
  6. Map every source section to a LidFly block via lidfly_list_blocks. Do not drop a section because no block feels perfect: pick the closest block and keep the content. Do not add blocks that have no counterpart in the original (FAQ, quizzes, calculators) unless the user asks.
  7. Prepare and show the section mapping and every intended template deviation before changing the page. By default preserve inherit_site_design=true, inherited chrome, starter structure, and the site's design system. If 1:1 styling requires a page-local theme, custom CSS, disabled inheritance, local header/footer, or a starter-structure change, explain the impact and obtain explicit textual confirmation before the write. Only then may the exact call use confirm_template_deviation: true; auto-approve is not confirmation.
  8. Transfer all images: download originals, upload through lidfly_upload_images_batch, and use the returned asset references in block props. Never hotlink the source site.
  9. For an existing managed page, reconstruct every block with its complete type, id, and props, then call lidfly_update_page with a complete replacement payload from the same page read: the same exact slug; all reconstructed blocks; the saved title, description, og_image, theme_preset, theme, page_kind, inherit_site_design, and auto_structured_data, except fields the user explicitly changes; plus the exact latest expected_publication_revision required by the tool schema. Missing blocks are deletions, and omitted optional fields can reset to defaults. Never automatically retry a stale CAS conflict: reread and rebuild the payload. Do not carry custom_css through this call: CSS has its own tools (step 11) and does not belong in a block replacement.
  10. For a change confined to one existing block, prefer lidfly_update_block with all current props instead of replacing the whole page. Do not call lidfly_update_site_theme for a page-only migration or improvement. A site-wide theme change is a separate operation that requires the user to ask for the whole site to change and to confirm its stated cross-page impact before the write.
  11. Custom CSS is a separate operation with its own tools; never rewrite a page through lidfly_update_page to change styles. Read the effective CSS of both levels with lidfly_get_css, edit one page with lidfly_update_page_css, and put rules shared by several pages into lidfly_update_site_css instead of copying them per page. Pass expected_custom_css_sha256 from the same read so a parallel edit is not overwritten silently. The cascade is site theme tokens → platform block CSS → site CSS → page CSS; an empty string clears a level; the limit is 64 KiB per level and </style is rejected. On a templated site a non-empty CSS write still needs explicit user consent and confirm_template_deviation: true, and it reports the deviation as CSS only.
  12. Write CSS against the declared anchors, never against generated scope classes (ossk4dv8j-*) or class substrings ([class*='-card']): those break silently when block markup changes. Every section carries data-lf-block, data-lf-block-index, and data-lf-block-id when an anchor id is set; internal elements carry the data-lf-part values the block declares in lidfly_list_blocks. Example: [data-lf-block="messenger-lead-band"] [data-lf-part="item"]{width:56px}. Before reaching for CSS at all, check whether the block already exposes a typed style prop for the same thing.
  13. Reread the page after the write and compare it section by section with the inventory from step 2. After structural, theme, chrome, storefront-route, or homepage changes, rerun lidfly_audit_site_design_template. Report the mapping table, effective page fields, and any remaining deliberate deviations.

In The Built-In LidFly Chat

The chat cannot fetch HTML or CSS. Replace the source reading of steps 1 and 3 and keep the rest of the workflow:

  • Without a source address, ask once for the URL of the page to migrate. Propose the site name and subdomain yourself from the read source instead of asking for them first.
  • Read the source with read_website (max_pages = pages to migrate, 1–5) and continue a long page with read_website_page. When a page has a details summary, call read_website_page with part: "details" and follow next_offset until end_of_images: it returns image URLs with alt and the nearest section heading, header and footer Markdown with links, and forms with their fields.
  • Without details, say that texts and section order will be transferred and the images must be attached to the chat.
  • Styles are unavailable. Take the visual direction from the closest LidFly design template or theme and say that colors and fonts are approximate unless the user attaches screenshots of the source.
  • An account without sites first gets lidfly_prepare_create_site → lidfly_create_site. After creation, prefer one lidfly_preview_site_changeset → lidfly_apply_site_changeset package for pages with their images and supported shared chrome/forms; describe its exact scope before confirmation. Split only when the supported operations or size limits require it.
  • Images needed by a page: include import_image and upsert_page operations in the same site package, using exact @asset:key references. Independent asset-library imports may use lidfly_upload_images_batch or lidfly_upload_image. Preserve returned canonical paths; recover a legacy result with lidfly_list_assets in the exact site scope, never by guessing the filename URL.
  • Pages: build the inventory (step 2) from the text and the details sections, map blocks (step 6), show the mapping (step 7), then prepare the page write (steps 9–10). Transfer the header menu and footer requisites through lidfly_get_site_chrome → lidfly_update_site_chrome, and forms through lidfly_list_site_forms → lidfly_manage_site_forms.
  • After the page write, compare it with the inventory (step 13). If the user attached screenshots of the source, offer lidfly_inspect_site_visual with them as reference_attachment_ids.

Block Mapping Hints

  • Personal intro with a photo, or text plus illustration: feature-split.
  • Three to four advantage cards: features-grid.
  • Service chips or tag strips: logo-service-rail with wordmark labels.
  • Large service cards with photos, bullets, and per-card CTA: overlap-services-showcase.
  • Case studies with metrics: case-study per case, badges via stats-counter.
  • Price plans with bullet lists: pricing-3col or stacked-pricing-groups for four and more plans.
  • Client logo walls: logo-cloud with grayscale, logo-cloud-cases when captions matter.
  • Contact section with address, hours, phone: contact-card plus a lead form block.

Rules

  • MCP clients follow MCP v3 order: search_tools, then get_tool_schema, then call_tool for reads and call_write_tool for writes.
  • Page and site updates, uploads, and publication are writes and must use call_write_tool; all prerequisite reads use call_tool.
  • Keep the original wording. Fix only obvious typos, and tell the user about each fix.
  • Respect legal blocks: transfer privacy policy links, offer links, and footer requisites as they are.

Перенос popup-форм

Для существующих CTA сначала прочитай action_controls выбранного блока и lidfly_list_site_forms; переноси popup заявки в общую форму, затем назначай site_form_modal с прочитанным formRef и рабочим fallbackUrl. Вложенные массивы сохраняй целиком. Формы доступны при inheritSiteDesign:false, поддерживают image/imageAlt; не переноси произвольный JS модалки. modal-form создаёт отдельную кнопку и локальную форму, buttonId не связывает его с чужой CTA. Создание формы/загрузка изображения требует нового чтения ревизии; update заменяет props целиком. При pending/unknown проверь operation_id перед повторной записью. Открытие окна и доставку заявки проверяй отдельно.

Материалы и доказательства клиента — 18.10.2026

История клиента или авторский рассказ — редакционный блок, не выдуманный отзыв. Не добавляй звёзды, оценки, число клиентов, результаты, сертификаты или цитаты, если клиент не дал эти данные и источник. Сохраняй происхождение предоставленного текста в заметке задачи/проекте: файл, сообщение или URL; не выдавай редактуру за дословную цитату. Недостающие фотографии, отзывы и подтверждения перечисляй как оставшуюся работу, не заполняй их вымышленными доказательствами. При точечной правке сохраняй остальные блоки, адреса файлов и выбранное оформление.

Источник: аудит chat-site-flow 18.10.2026; решения владельца и контракт lidfly-site-changeset-schema.ts проверены 18.10.2026.

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.