kai-topical-map

Build a topical map optimized for AI search engines and traditional search together. Every decision is driven by retrievability, entity clarity, source quality, and measurable user demand, not by promises that a specific AI engine will cite a page.

Why This Matters

AI search visibility is sampled, volatile, and engine-specific. Treat any traffic, citation, or conversion benchmark as context until it is verified for the client with a source, retrieval date, evidence tier, and confidence label.

This skill builds the map that can be measured: pages to create, entities to clarify, passages to make retrievable, sources to cite, and follow-up checks to run.

Phase 0: Load Product Context

Check if MARKETING.md exists in the project root (same directory as CLAUDE.md, README.md, package.json).

If it exists: Read it — skip product discovery questions. It has the product name, ICP, value prop, monetization, brand voice, current channels, and competitive landscape.

If it does NOT exist: Auto-explore the codebase to create it in the project root (next to CLAUDE.md). Do NOT ask the user what the product is. Read CLAUDE.md, README.md, PROJECT.md, package.json, landing pages, and any project files. Search for email/ad/analytics config. Then create MARKETING.md using the template from /kai-email-system. Present draft to user for confirmation.