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…
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…
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…
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.
Main Figma orchestration skill for the UI/UX skill system. Use this skill whenever the user asks to read Figma design context, turn Figma frames into implementation plans or code, sync live UI back to Figma, edit Figma canvas objects, manage variables/components/assets/effects, audit Figma MCP workflows, or coordinate…
Senior-architect workflow for creating, editing, auditing, and monitoring SEO, AEO/GEO, LLM-readable, and AI-agent-friendly websites. Use when the user asks about SEO, technical SEO, organic visibility, AI search visibility, ChatGPT/Claude/Perplexity/Gemini readiness, robots.txt, sitemap.xml, llms.txt…
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…
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…
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…
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…
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.
Use this skill when a UI/UX project should use Google Stitch or a Stitch MCP/API workflow for rapid AI UI exploration after ui-ux-pro-max has produced design intelligence and before Figma/code implementation. This skill turns UX, SEO/LLM, brand, accessibility, and Pro Max constraints into Stitch-ready prompts…
Create, refactor, audit, and maintain a multi-agent TASK-PLAN v2 as a canonical Markdown control document with a pre-implementation feature gate, sequential per-task agent orchestration, explicit test/review/rollback fields, wiki sync rules, and a derived HTML dashboard contract. Use when Codex needs to turn loose…
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.
Design deterministic technical SEO and schema.org guidance for crawlable public pages. Use this skill when the user asks for title and meta description rules, canonical and hreflang tags, JSON-LD schema, NewsArticle, Article, TechArticle, BreadcrumbList, WebSite, Organization, Person, OpenGraph, Twitter cards…