claude-context-migratelisted

# Claude context migrate ## Guards - If no `docs/` directory exists at `pwd`, stop: `❌ No docs/ directory found.` - If `docs/` contains no `.md` files at the top level, stop: `❌ No markdown files in docs/.` - This skill operates on flat `docs/*.md` only. Subfolders under `docs/` are listed in the output as "manual review needed" and skipped. ## Step 1: discover Run these in parallel from `pwd`: - `ls docs/*.md 2>/dev/null`: list flat markdown files - `ls docs/*/ 2>/dev/null`: detect subfolders for the manual-review note - `ls .claude/context/ 2>/dev/null`: detect already-migrated content for conflict checks - `aitk claude seeds list --json 2>/dev/null`: get the canonical seed list to identify seed-derived files Read each discovered `docs/*.md` file in parallel. ## Step 2: classify For each file, score against this rule order: 1. **Seed-derived.** Filename matches `development.md` or `ci.md` and content shape resembles the toolkit's base seed (frontmatter plus a Setup or Triggers section plus tables for scripts or checks). These belong to the seed-migration path. Do not propose a move here. 2. **Agent-flavored.** Score the following signals. Classify as agent-flavored when two or more match: - Dense file paths in code fences - Sections titled "Anti-patterns", "Layer responsibilities", "Conventions", or "Commands" - Tables of CLI commands - Explicit "do not" rules 3. **Human-only.** Default fallback when no agent signals match. Typical signals: - Tutoria