---

name: yao-geoflow-template description: Use only for explicit legacy GEOFlow template skill questions, old PHP template-package contracts, or historical outputs using root index.php/article.php/category.php/archive.php and includes/*.php. Route current Laravel Blade themes, reference-site cloning, homepage modules, lead_form, theme editor, channel frontend, and target-package mapping to yao-geoflow-design. Do not use for new frontend design, backend implementation, raw HTML copying, or live activation.

Yao GEOFlow Template Legacy Router

Compatibility entrypoint for old GEOFlow PHP template-package notes. Current frontend work belongs in yao-geoflow-design.

Boundary

• Owns legacy output review, old PHP contract explanation, and handoff notes to yao-geoflow-design.
• Excludes new Laravel Blade themes, homepage builder, lead_form, theme editor, channel sync, target-package mapping, backend changes, and activation.
• Old index.php, article.php, category.php, archive.php, and includes/*.php are legacy assumptions, not current preconditions.

Routing

1. Current GEOFlow frontend design or reference-site cloning: use yao-geoflow-design.
2. Explicit “legacy template skill” or “旧 PHP 模板包”: continue here.
3. Read template-boundary.md and theme-package-contract.md before interpreting old files.

References

template-boundary.md, theme-package-contract.md, geoflow-frontend-map.md, trigger_cases.json, upgrade report.