What This Skill Does Not Cover

Required Preconditions

Confirm the target workspace is a GEOFlow codebase with index.php, article.php, category.php, archive.php, and includes/header.php.
Read the GEOFlow frontend contract in references/geoflow-frontend-map.md before proposing any clone plan.
Preserve the existing module/data contract unless the user explicitly asks for a system change.
Treat preview and activation as separate steps. A cloned template should be previewed before it is considered for activation.

Identify the GEOFlow workspace and confirm the canonical frontend files.
Read references/geoflow-frontend-map.md to understand current modules, variables, and rendering boundaries.
Read references/template-boundary.md to separate safe style replacement from prohibited contract changes.
If a reference URL is provided, inspect its visual tokens and layout patterns.
Map the reference site's style direction onto GEOFlow's stable modules rather than copying full pages verbatim.
Produce a theme package that targets:
- homepage
- category page
- article detail page
- archive page
- header / footer
- article detail ad block
When helpful, emit concrete package artifacts:
- outputs/<template-id>/tokens.json
- outputs/<template-id>/mapping.json
- outputs/<template-id>/manifest.json
- preview/<template-id>/... preview pages
Prefer a preview URL over prose-only output when the user wants to inspect the mapped style.
Keep output preview-first. Activation should only happen after review and explicit confirmation.
If the user asks for system implementation later, use the generated package and contract as the source of truth for the GEOFlow-side template feature.

When the user asks for template cloning, begin from GEOFlow's existing frontend contract, not from generic redesign advice.
Always state which modules can be restyled safely and which contracts must remain fixed.
Prefer module mapping, design tokens, and theme package structure over raw HTML replacement.
If a requested reference site pattern conflicts with GEOFlow's data contract, say so and offer the closest compatible mapping.

Read references/geoflow-frontend-map.md for the authoritative frontend module and variable map.
Read references/template-boundary.md for safe/unsafe modification boundaries.
Read references/theme-package-contract.md for the expected output of a clone run.