SkillsAdd

yaojingang/yao-geo-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 imp…

First seen Apr 23, 2026

Installation

$ npx skills add yaojingang/yao-geo-skills --skill yao-geoflow-design
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from yaojingang/yao-geo-skills · top by installs.

npx skills add yaojingang/yao-geo-skills
yao-geo-tracking 22 yao-geoflow-cli 21 yao-geoflow-template 20 yao-geo-panorama-audit 20 yao-geo-page-audit 20 yao-geo-knowledge-base-builder 20 yao-geo-intent-miner 20 yao-geo-page-blueprint 19 yao-geo-execution-roadmap 19 yao-geo-effect-monitor 18

Browse all from yaojingang/yao-geo-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 736
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,167 B
  • docs README.md 4,529 B
  • docs SUMMARY.md 624 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 20 installs

SKILL.md

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, leadform modules with existing leadform_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/discoverthemes.py and scripts/discoverfrontend_surfaces.py.
  3. Choose targetsurface: defaultsite, channelsite, crosschannelsync, or templatemapping.
  4. Prefer reviewed homepage-design.json over Blade edits when HomepageModuleBuilder/import exists.
  5. For leadform, require an existing active slug and output canonical leadform_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

Read [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. For 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). For 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). Review [triggercases.json](evals/triggercases.json) and [upgrade report](reports/geoflow-skill-upgrade-2026-07-05.md) when checking routing.