sergekostenchuk/ui-ux-agent-skill-system

internal-link-graph-architect

Design intentional internal link graphs for SEO, UX, and LLM-readable sites.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill internal-link-graph-architect

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Internal Link Graph Architect

Use this skill after information-architecture-seo has defined page roles and canonical policy.

Read references/link-graph-rules.md before producing a full graph.

Owns

  • intentional internal link graph;
  • brief-to-longform and longform-to-brief links;
  • breadcrumbs;
  • topic, project, author, community, and source-trail links;
  • anchor intent;
  • orphan-page checks;
  • overlink and duplicate-intent risk checks.

Does Not Own

  • canonical and hreflang policy;
  • final URL architecture;
  • external backlink placement;
  • hidden links;
  • visual UI layout;
  • schema implementation.

Workflow

  1. Read url-map.yaml, page roles, canonical model, language groups, and content model.
  2. Identify required structural links: breadcrumbs, brief-longform pairs, topic/project/author/entity links.
  3. Add source-trail links only when they are visible and useful to users.
  4. Assign link_type, anchor_intent, user_reason, seo_reason, and risk.
  5. Flag orphan pages, circular links without purpose, irrelevant exact-match anchors, and duplicated story-body routes.
  6. Produce internal-link-graph.yaml using assets/internal-link-graph.template.yaml.
  7. Hand off schema/head implications to technical-seo-schema-engineer and rendered navigation checks to ui-ux-llm-product-architect.

Link Rules

  • Every link must have a user reason.
  • A short brief should link to its one longform article when a longform exists.
  • A longform article should link back to its brief when the brief remains a standalone news surface.
  • Topic pages organize related pages with summaries; they do not duplicate story bodies.
  • Author and project links support trust and entity understanding.
  • Breadcrumbs clarify hierarchy; they are not keyword stuffing.
  • Related links should be sparse and defensible.
  • External authority placement is out of scope.

Safety And Privacy Boundaries

  • Do not recommend hidden links, cloaked links, injected footers, irrelevant exact-match anchors, or link stuffing.
  • Do not link public pages to admin, private API, private analytics, raw IP logs, staging URLs, secret files, or unpublished drafts.
  • Do not create extra public story pages to increase link count.
  • Do not weaken UX or accessibility for SEO anchors.

Validation

Before marking work complete:

  • every link has source URL, target URL, type, anchor intent, user reason, SEO reason, and risk;
  • every page expected to be discoverable has at least one logical incoming link;
  • brief and longform pages are paired without creating extra story bodies;
  • topic/project/author links have entity or navigation purpose;
  • hidden or irrelevant link recommendations are absent.

Validate skill edits with:

bash
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $HOME/SKILL/skills/internal-link-graph-architect
python3 $HOME/SKILL/plans/seo-llm-skill-cluster/scripts/lint_skill_cluster.py $HOME/SKILL

Forward tests live in evals.json.

Output Shape

Return:

  1. Link graph summary.
  2. Required structural links.
  3. Optional related links.
  4. Orphan/overlink risks.
  5. Handoff notes for technical SEO/schema and UX.

관련 작업

같은 저장소의 Skills

더 많은 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일