create-target

Create a new target implementation for universal-ai-config. A target maps universal template frontmatter and hooks to a specific AI coding assistant's configuration format.

Phase 1 — Research & Approval

1. Research the target's config format — find up-to-date documentation online for how the target AI assistant expects its configuration files. Look for:

   • File locations and naming conventions (e.g., .cursor/rules/*.mdc, .github/instructions/*.md)

   • Frontmatter format for each file type

   • Hook configuration format (JSON structure, event names)

   • MCP tool reference syntax — how the target references MCP tools in hook matchers, agent tools: frontmatter, and any allow/deny lists. Find the exact string format (e.g. mcp__server__tool, server/tool, MCP:tool) and the wildcard convention for "all tools on a server"

   • What it reads from other tools — whether it also loads AGENTS.md (root, nested, when) and project skills from .agents/skills/ (the Agent Skills standard's folder), other tools' folders (.claude/skills, .claude/agents, .claude/settings.json hooks, root .mcp.json), and what it does when it finds its own copy too: loads both, dedupes identical entries, or prefers its own. Docs are often vague here — follow Part 6 of the upstream validation reference to check by running the tool.

   Look through docs for all supported configuration types:

   • Instructions/rules/"system prompt"
   • Skills/Commands
   • Agents
   • Hooks
   • MCP servers

2. Present findings for approval — before writing any code, present a structured summary of your research to the user. For each supported configuration type, include:

   • What it maps to: the universal template type it corresponds to (instructions, skills, agents, hooks)
   • File location & naming: where the target expects these files and what extensions/naming conventions it uses
   • Frontmatter/metadata format: the exact fields, keys, and structure the target uses (with examples from docs)
   • Hook format (if applicable): event names, JSON structure, how handlers are defined, which handler types it runs
   • Cross-tool reads: the other outputs it loads and how it reconciles duplicates (see above)
   • Source links: direct URLs to the official documentation pages you referenced

   Format as a clear table or grouped list so the user can review each mapping. Ask the user to approve or flag any corrections before proceeding. Do not continue until the user explicitly approves.