sergekostenchuk/ui-ux-agent-skill-system

existing-site-analyzer

Analyze an existing website before improve, redesign, rebuild, or migration decisions.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill existing-site-analyzer

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Existing Site Analyzer

This skill creates the evidence base for existing-site work. It does not decide rebuild strategy by itself and does not mutate the live site.

Operating Modes

  • local-inventory: inspect local HTML, source files, assets, sitemap, robots, and reports.
  • public-url-review: review public URLs or fetched HTML only after network/crawling approval.
  • screenshot-review: analyze screenshots when URL or source is unavailable.
  • asset-inventory: inventory images, videos, docs, icons, maps, and brand assets.
  • handoff: produce evidence for rebuild-or-improve-advisor and migration-planner.

Required Workflow

  1. Read references/existing-site-analysis-contract.md.
  2. Confirm source type and privacy:
  • local files and user-provided public screenshots: allowed;
  • public URL crawling/fetching: approval required if not already requested;
  • authenticated/private pages, analytics, CRM, or CMS: explicit approval and data-handling note required.
  1. Use assets/existing-site-audit.template.md for the report.
  2. Record evidence status for every source: Ran, Skipped, Planned, or Manual.
  3. Capture:
  • page inventory;
  • content and IA;
  • SEO/LLM surface;
  • UX and conversion issues;
  • technical constraints;
  • asset inventory;
  • migration risks.
  1. Hand off to rebuild-or-improve-advisor; involve migration-planner if URL structure, redirects, sitemap, robots, schema, or launch risk may change.

Safety Rules

  • Do not crawl private/authenticated pages without explicit approval.
  • Do not store private analytics exports, cookies, tokens, private URLs, or .env values in reports.
  • Do not claim Lighthouse, browser, crawler, or DOM evidence unless it was actually run.
  • Do not change production content, redirects, robots, sitemap, DNS, CMS, or deployment settings.

Handoff Shape

text
Mode:
Sources:
Evidence status:
Major findings:
SEO/LLM risks:
UX risks:
Technical constraints:
Asset inventory:
Migration risk:
Next owner:

Validation

When editing this skill, run:

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/existing-site-analyzer
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/existing-site-analyzer
python3 -m json.tool $CODEX_HOME/skills/existing-site-analyzer/evals/evals.json >/dev/null

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
sergekostenchuk
コミュニティ

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.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

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.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

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.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

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.

導入数
1
GitHub Stars
32
更新日
9月13日