sergekostenchuk/ui-ux-agent-skill-system

semantic-core-builder

Build an evidence-labeled semantic core and crawlable site structure from keyword harvests, existing content, or user-provided search-demand data.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill semantic-core-builder

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Semantic Core Builder

This skill turns raw keyword/search inputs into a structured semantic core. It hands the result to seo-llm-site-architect, concept-prototyper, and later design/implementation skills.

Operating Modes

  • build: create reports/semantic-core.json and docs/site-structure.md.
  • merge: merge existing-site keywords, user-provided terms, and harvested demand.
  • audit: review a semantic core for missing provenance, duplicate clusters, or weak intent mapping.

Required Workflow

  1. Read references/semantic-core-contract.md.
  2. Load reports/keyword-harvest.json or a user-provided equivalent.
  3. Cluster keywords by intent and topic; label any LLM grouping as Inference.
  4. Produce cluster records: intent, priority, canonical URL candidate, page type, evidence, and confidence.
  5. Write machine-readable reports/semantic-core.json and human-readable docs/site-structure.md.
  6. Hand off to concept-prototyper and seo-llm-site-architect.

Safety And Evidence

  • Do not invent search volume or SERP facts.
  • If no real SERP/source evidence exists, label the output as Manual or Inference.
  • Do not bury conflicts; record cannibalization, unclear intent, or missing evidence.

Handoff Shape

text
Input path:
Clusters:
High-priority URLs:
Conflicts:
Evidence gaps:
Output paths:
Next skills: concept-prototyper, seo-llm-site-architect

Validation

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/semantic-core-builder
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/semantic-core-builder

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
sergekostenchuk
Community

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

installazioni
1
GitHub Stars
32
Aggiornato
13 set
sergekostenchuk
Community

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

installazioni
1
GitHub Stars
32
Aggiornato
13 set
sergekostenchuk
Community

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

installazioni
1
GitHub Stars
32
Aggiornato
13 set
sergekostenchuk
Community

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

installazioni
1
GitHub Stars
32
Aggiornato
13 set