yao-geoflow-design

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.

Ir a la instalación

Repositorio: yaojingang/yao-geo-skills
Última actividad en el origen: 5 de julio de 2026 a las 14:20
Idioma detectado de SKILL.md: inglés
Estrellas: 740
Forks: 148

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/yaojingang/yao-geo-skills --skill yao-geoflow-design

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

43 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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