ui-ux-agent-skill-system

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.

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.

Use this skill when the user wants a human-readable project progress screen, agent work visualization, customer-facing status cockpit, immediate bootstrap progress before TASK-PLAN.md exists, task-plan-derived HTML progress page, user decision gates, or auto-updating UI/UX project status for senior-ui-ux-orchestrator workflows. It renders and validates progress views from project-request.json, workflow-log.jsonl, TASK-PLAN v2, progress-state.json, feedback artifacts, reports, and wiki decisions without becoming the source of truth.

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.

Validate proposed or existing backlinks for relevance, editorial legitimacy, link attributes, spam/toxicity risk, platform compliance, anchor quality, target-page fit, and monitoring evidence. Use this skill when the user asks whether an external link opportunity or placed backlink is safe and useful, and reject toxic, irrelevant, paid-undisclosed, fake, or spam placements.

Turn semantic core, business constraints, and user feedback into a site concept and throwaway wireframe prototype before visual design. Use when a public site project needs a pre-design concept, content hierarchy, concept conflicts, or business-idea feedback before Stitch, Pencil, Figma, or code.

Use when planning deployments, build commands, environment checks, CI/CD, release steps, smoke tests, rollback, and monitoring. Dry-run first; do not deploy to production, change secrets, or mutate live services without explicit approval.

Collect, structure, deduplicate, and resolve user and agent feedback on UI/UX skills, subprocesses, design directions, progress-screen gates, Stitch/Pencil/Figma outputs, and implementation steps. Use when comments need statuses such as open, accepted, partially accepted, applied, rejected, or when review-board/progress-page fields must become actionable decisions.

Use when planning DNS records, nameservers, A/AAAA/CNAME/TXT/MX, SPF/DKIM/DMARC, CDN, propagation, and rollback. Dry-run only; do not change production DNS or store provider credentials without explicit approval.

Use when a project needs domain name ideas, naming constraints, availability-check planning, brand/SEO fit, and shortlists. Advisory only; do not purchase domains, call paid APIs, or claim live availability unless checked with evidence.

Use when comparing domain registrars, TLD costs, renewal risks, privacy, DNS features, transfer lock, and purchase steps. Advisory/dry-run only; do not buy domains or log into registrar accounts without explicit approval.

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

Analyze an existing website before improve, redesign, rebuild, or migration decisions. Use when a project has a current URL, local HTML/codebase, screenshots, sitemap, robots, analytics export, asset folder, or legacy site materials and needs a local-first audit with approval-gated crawling or authenticated access.

Find and score legitimate external authority and backlink opportunities as a dry-run register, using relevance, platform rules, risk, target-page fit, and explicit user approval gates. Use this skill when the user asks where links to a target site could be placed effectively, but never post, submit, DM, email, open PRs, or edit external accounts without separate explicit approval.

Convert a semantic core into crawlable SEO and LLM-friendly information architecture. Use this skill when the user asks for URL structure, page taxonomy, canonical rules, hreflang groups, page roles, pillar/topic/news/article/blog/project separation, multilingual route strategy, or a durable content model such as one short brief plus one longform article. It prevents duplicate public content bodies and hands link-graph work to internal-link-graph-architect.

Use when a project needs launch/infrastructure coordination across domains, registrars, servers, DNS, deploy, SSL, webmaster tools, monitoring, and launch readiness. Dry-run first; do not purchase, provision, deploy, or mutate production without explicit approval.

Design intentional internal link graphs for SEO, UX, and LLM-readable sites. Use this skill when the user asks for links between short briefs, longform articles, topics, projects, author pages, breadcrumbs, source trails, related stories, orphan-page checks, overlink checks, anchor intent, or validation that a link graph reinforces the canonical content model without creating duplicate story bodies or hidden links.

Use before launch to audit SEO, schema, accessibility, performance, security, analytics, redirects, sitemap, robots, SSL, monitoring, rollback, and approval gates. Evidence-first; do not mark launch ready unless required checks ran or are explicitly skipped with rationale.

Plan and record evidence-backed LLM and AI-search citation checks across approved assistant/search surfaces with timestamped queries, locales, modes, cited URLs, snippets, screenshots or transcripts, and caveats. Use this skill when the user asks whether ChatGPT, Perplexity, Claude, Gemini, Copilot, or another assistant cites a target site, but do not claim citation without direct evidence.

Design human-visible, machine-readable website layers for AI assistants, RAG, and agentic search. Use this skill when the user asks for llms.txt, LLM discovery plans, visible TLDR or direct-answer blocks, source trails, entity pages, markdown alternates, AI crawler policy, topic-to-URL maps, assistant-readable public content, or LLM-friendly architecture that must preserve canonical SEO strategy without hidden bot-only facts or duplicate story bodies.

Tactical LLM-friendly site optimization for making a website the best citable answer for AI assistants and RAG retrieval. Use for auditing and optimizing sites such as mlllm.io for llms.txt, AI citation readiness, pillar pages, direct-answer blocks, TL;DR sections, FAQ/schema, article/news schema, topic-to-URL matrices, external citation signals, weekly LLM citation monitoring, and content architecture for ChatGPT, Claude, Perplexity, Gemini, Copilot, Google AI features, Bing, Brave, and other assistant/search retrieval systems.

Use when the task involves a filesystem-based LLM Wiki or Obsidian vault, especially Ar9av/obsidian-wiki projects using .skills, .env, ~/.obsidian-wiki/config, AGENTS.md, .manifest.json, index.md/log.md/hot.md, ingest/query/lint workflows, or Russian prompts like "добавь в вики", "сделай ingest", "lint wiki", "обнови index/log", or "разложи по obsidian-wiki".

Plan safe website migrations when existing URLs, redirects, sitemap, robots, schema, canonical pages, metadata, analytics, webmaster tools, or launch monitoring may change. Use after existing-site analysis or rebuild decisions; never apply production redirects, DNS, deploy, or webmaster mutations without explicit approval.

Use when a site needs communication workflow planning: forms, inboxes, chat, booking, email/SMS/Telegram/CRM handoffs, operator queues, routing, templates, consent, and escalation. Workflow design only; never send real messages or mutate CRM channels without explicit approval.

Use when a website needs paid traffic planning: campaigns, audience hypotheses, UTM maps, landing requirements, creative briefs, budget placeholders, and SEO/ads handoffs. Planning only; never launch campaigns, spend budget, or mutate ad accounts without explicit approval.

Bridge approved UI/UX direction briefs into Pencil design workflows without treating `.pen` files as plain text. Use when a project needs Pencil MCP/tool handoff, editable design exploration, design-system-aware canvas work, or review of Pencil outputs after senior-ui-ux-orchestrator, ui-ux-pro-max, Stitch, or Figma constraints are known.

Manage sanitized project memory and Obsidian/LLM wiki gates for large UI/UX, SEO, Figma, Stitch, progress-screen, skill-system, migration, launch, or multi-session agent projects. Use when a project needs durable context, llms-context packs, decision capture, handoff notes, or wiki sync without storing secrets.

Decide whether an existing site should be improved in place, redesigned, partially rebuilt, or fully rebuilt after an evidence-backed audit. Use when the project needs a governed improve/redesign/rebuild recommendation balancing UX, SEO/LLM, migration risk, technical debt, timeline, and implementation cost.

Build evidence-labeled semantic cores for SEO, LLM-readable architecture, and site information design. Use this skill when the user asks for semantic core, query clusters, search intents, audience segments, entity/topic maps, language or locale priorities, competitor/source evidence, pillar-topic planning, or a structured handoff before URL architecture and internal linking. It must mark unknown search volume, difficulty, and ranking data as unknown instead of inventing metrics.

Build an evidence-labeled semantic core and crawlable site structure from keyword harvests, existing content, or user-provided search-demand data. Use before SEO/LLM site architecture, concept prototypes, paid traffic planning, IA, or public-site redesign decisions.

Validate SEO and LLM-readability claims against live HTML, local fixtures, and generated artifacts. Use this skill when the user asks to prove whether title, meta description, canonical, hreflang, JSON-LD, NewsArticle.image, OpenGraph, Twitter cards, RSS autodiscovery, robots.txt, llms.txt, sitemap, news-sitemap, crawler access, or performance evidence is actually present, and when subjective audits must become timestamped pass/fail reports.

Collect and normalize search-demand inputs for public site projects before semantic-core work. Use when a UI/UX or SEO project needs seed keywords, SERP snapshots, autocomplete ideas, People Also Ask, related searches, or a dry-run keyword harvest with approval-gated external search APIs.

Configure SERP/search-demand source settings before keyword harvesting. Use when a UI/UX, SEO, or site project needs a user-facing source setup gate, OpenSERP self-host settings, proxy provider/API-key fields such as AKE, checkbox selection of Google/Yandex/Bing/DuckDuckGo/Ecosia/Baidu/manual sources, paid-proxy/budget limits, approval notes, or preflight checks before `serp-keyword-harvester` sends external queries.

Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots/llms/sitemap checks, and exported summaries while protecting raw IP and private query data. Use this skill when the user asks whether crawlers or AI bots reached a site, whether public SEO/LLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.

Use when preparing server provisioning plans, IaC drafts, SSH hardening, users, firewalls, backups, monitoring, and rollback. Dry-run by default; do not create, mutate, or destroy production servers without explicit approval.

Use when choosing hosting/server architecture for a site or app: static hosting, VPS, PaaS, CDN, region, cost assumptions, scaling, security, and ops tradeoffs. Advisory only; do not provision servers or create paid resources without explicit approval.

Use when a public website needs an AI assistant with source-bounded answers, RAG/content scope, injection protection, escalation, logging, rate limits, refusals, and no hallucinated product/legal/price claims. Planning or implementation handoff only; do not expose secrets or give destructive tools.

Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.

Use when planning SSL/TLS, HTTPS redirects, HSTS, security headers, CSP, cookie flags, backups, monitoring, and basic launch hardening. Dry-run first; do not mutate production server, DNS, certificates, or secrets without explicit approval.

Select or review the frontend/CMS/deployment stack for UI/UX site projects after concept definition and before design-to-code or launch work. Use when choosing between static HTML, React/Next/Vite, CMS/admin needs, Figma/Pencil handoff, SEO constraints, existing-site rebuild, or maintainability tradeoffs.