# Yao Geoflow Design

Discover, compare, preview, clone, and orchestrate current GEOFlow frontend experiences...

- Repository: https://github.com/yaojingang/yao-geo-skills (912 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add yaojingang/yao-geo-skills --skill yao-geoflow-design -g -a claude-code -y`
Codex: `npx skills add yaojingang/yao-geo-skills --skill yao-geoflow-design -g -a codex -y`
Cursor: `npx skills add yaojingang/yao-geo-skills --skill yao-geoflow-design -g -a cursor -y`
Gemini CLI: `npx skills add yaojingang/yao-geo-skills --skill yao-geoflow-design -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

The rest: https://github.com/yaojingang/yao-geo-skills/blob/HEAD/skills/yao-geoflow-design/SKILL.md