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
- Confirm a GEOFlow Laravel workspace:
artisan, routes/web.php, resources/views/site, resources/views/theme.
- Run
scripts/discover_themes.py and scripts/discover_frontend_surfaces.py.
- Choose
target_surface: default_site, channel_site, cross_channel_sync, or template_mapping.
- Prefer reviewed
homepage-design.json over Blade edits when HomepageModuleBuilder/import exists.
- For
lead_form, require an existing active slug and output canonical lead_form_slug; do not create the form here.
- For channel sync, compare default-site supported modules with target-package
frontend-capabilities; downgrade unsupported lead_form to CTA/link or require target upgrade.
- 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.
1---2name: yao-geoflow-design3description: Discover, compare, preview, clone, and orchestrate current GEOFlow frontend experiences across the default site and GeoFlow Agent channel sites, including Laravel Blade themes, homepage module/style JSON, lead_form conversion modules, theme editor, target-package capabilities, and cross-channel sync planning. Use for frontend theme discovery, reference-site mapping, homepage builder design, channel capability audits, and preview-first design iteration. Do not use for CLI operations, backend implementation, lead-form CRUD, raw HTML copying, unsupported remote edits, or direct live activation.4---56# Yao GEOFlow Design78Use this skill for current GEOFlow frontend experience work. It owns design/planning and preview artifacts, not live activation or backend changes.910## Boundary1112- 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.13- Excludes backend/routes/models/migrations, lead-form CRUD, CLI operations, direct production activation, raw HTML copying, and unsupported remote PHP edits.14- Use `yao-geoflow-cli` for operational admin web actions such as creating lead forms, exporting leads, publishing theme-editor drafts, or running system updates.1516## Required Checks17181. Confirm a GEOFlow Laravel workspace: `artisan`, `routes/web.php`, `resources/views/site`, `resources/views/theme`.192. Run `scripts/discover_themes.py` and `scripts/discover_frontend_surfaces.py`.203. Choose `target_surface`: `default_site`, `channel_site`, `cross_channel_sync`, or `template_mapping`.214. Prefer reviewed `homepage-design.json` over Blade edits when HomepageModuleBuilder/import exists.225. For `lead_form`, require an existing active slug and output canonical `lead_form_slug`; do not create the form here.236. For channel sync, compare default-site supported modules with target-package `frontend-capabilities`; downgrade unsupported `lead_form` to CTA/link or require target upgrade.247. Keep preview/import/sync/activation as separate confirmation steps.2526## References2728Read [geoflow-frontend-map.md](references/geoflow-frontend-map.md), [homepage-composition-guide.md](references/homepage-composition-guide.md), and [template-boundary.md](references/template-boundary.md) for default-site work.29For channel work also read [channel-frontend-contract.md](references/channel-frontend-contract.md), [distribution-target-site-map.md](references/distribution-target-site-map.md), and [backend-connection-workflow.md](references/backend-connection-workflow.md).30For package/edit flows read [laravel-theme-contract.md](references/laravel-theme-contract.md), [theme-package-contract.md](references/theme-package-contract.md), [theme-edit-workflow.md](references/theme-edit-workflow.md), and [design-optimization-playbook.md](references/design-optimization-playbook.md).31Review [trigger_cases.json](evals/trigger_cases.json) and [upgrade report](reports/geoflow-skill-upgrade-2026-07-05.md) when checking routing.
yaojingang