Yao geoflow design

Skill ShenyuanNext/wepr-growth-skills/skills/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.From its SKILL.md

Install

npx -y skills add ShenyuanNext/wepr-growth-skills --skill yao-geoflow-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, 538 tokens by cl100k_base, as published. Nobody here has run it

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