yao-geoflow-design

Yao GEOFlow Design

Use this skill for current GEOFlow frontend experience work. It owns design/planning and preview artifacts, not live activation or backend changes.

Boundary

• Owns Laravel Blade theme discovery, preview edit sessions, reference-site mapping, homepage homepage-design.json, lead_form modules with existing lead_form_slug, default-vs-channel frontend comparison, target-package capability gaps, and sync-preview planning.
• Excludes backend/routes/models/migrations, lead-form CRUD, CLI operations, direct production activation, raw HTML copying, and unsupported remote PHP edits.
• Use yao-geoflow-cli for operational admin web actions such as creating lead forms, exporting leads, publishing theme-editor drafts, or running system updates.

Required Checks

1. Confirm a GEOFlow Laravel workspace: artisan, routes/web.php, resources/views/site, resources/views/theme.
2. Run scripts/discover_themes.py and scripts/discover_frontend_surfaces.py.
3. Choose target_surface: default_site, channel_site, cross_channel_sync, or template_mapping.
4. Prefer reviewed homepage-design.json over Blade edits when HomepageModuleBuilder/import exists.
5. For lead_form, require an existing active slug and output canonical lead_form_slug; do not create the form here.
6. For channel sync, compare default-site supported modules with target-package frontend-capabilities; downgrade unsupported lead_form to CTA/link or require target upgrade.
7. Keep preview/import/sync/activation as separate confirmation steps.

References

Read geoflow-frontend-map.md, homepage-composition-guide.md, and template-boundary.md for default-site work. For channel work also read channel-frontend-contract.md, distribution-target-site-map.md, and backend-connection-workflow.md. For package/edit flows read laravel-theme-contract.md, theme-package-contract.md, theme-edit-workflow.md, and design-optimization-playbook.md. Review trigger_cases.json and upgrade report when checking routing.