create-project-skills

# Create Project Skills Generates one skill per detected convention area in the project's skill directory so future Claude or Codex sessions auto-load them when working in the repo. ## Task Tracking At the start, use `TaskCreate` to create a task for each phase: 1. Survey codebase 2. Extract patterns in parallel 3. Evaluate patterns 4. Propose skill list 5. Run `/create-skill` skill ## Step 1: Survey Codebase If `$ARGUMENTS` specifies paths, scope the scan to those paths; otherwise scan the whole repository. Build the extraction context: 1. Detect primary languages and frameworks from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, `go.mod`, `Package.swift`, `pom.xml`, `Gemfile`, and others appropriate to the stack). 2. Map the top-level source directory structure and note test directory conventions. 3. Read `CLAUDE.md`, `.claude/rules/`, `AGENTS.md`, and any `.cursor/rules` or `.cursorrules`. Note the conventions already documented there. The generated skills must not duplicate them. 4. Determine the target skill directory: - Check candidate paths `.claude/skills/` (Claude Code), `.agents/skills/` (Codex), and a top-level `skills/` directory (match case-insensitively so `Skills/` or similar non-standard casing is detected too). Resolve symlinks so co-linked paths are treated as one logical location. - Use `AskUserQuestion` to confirm where generated skills should live. List each distinct resolved location as an option, noting any symlink alias i...