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 para a instalação

Repositório: yaojingang/yao-geo-skills
Última atividade na origem: 5 de julho de 2026 às 14:20
Idioma detectado do SKILL.md: inglês
Estrelas: 740
Forks: 148

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

43 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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