feat: add Claude skills and hooks for platform workflows

Add project-specific skills (/validate, /setup-repo, /docs-preview)
and an auto-invoked spec-context skill. Add PostToolUse hook to
remind about doc cross-references when editing docs/ files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: baijum

.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "filepath=\"$TOOL_INPUT_file_path\"; case \"$filepath\" in */docs/*) echo '[Hook] Editing a docs/ file — check cross-references between spec.md, ecosystem.md, governance.md, and ROADMAP.md' ;; esac; exit 0"
+          }
+        ]
+      }
+    ]
+  }
+}

.claude/skills/docs-preview/SKILL.md

@@ -0,0 +1,15 @@
+---
+disable-model-invocation: true
+allowed-tools: Bash
+description: Start MkDocs local server for documentation preview
+---
+
+# /docs-preview — Preview Documentation
+
+Start a local MkDocs development server for previewing documentation.
+
+## Instructions
+
+1. Run `mkdocs serve` in the background
+2. Tell the user to visit http://127.0.0.1:8000
+3. If mkdocs is not installed, suggest: `pip install mkdocs`

.claude/skills/setup-repo/SKILL.md

@@ -0,0 +1,17 @@
+---
+disable-model-invocation: true
+allowed-tools: Bash
+argument-hint: "<repo-name>"
+description: Run the governance setup script for a towlion repository
+---
+
+# /setup-repo — Configure Repository Governance
+
+Run the governance setup script to configure repo settings, branch protection, and standard labels for a towlion repository.
+
+## Instructions
+
+1. `$ARGUMENTS` must contain the repository name (e.g., `app-template`, `uku-companion`)
+2. If no argument is provided, tell the user they need to specify a repo name
+3. Run: `bash scripts/setup-repo.sh $ARGUMENTS`
+4. Show the output to the user

.claude/skills/spec-context/SKILL.md

@@ -0,0 +1,41 @@
+---
+user-invocable: false
+description: Use when discussing app structure, deployment, or spec compliance
+---
+
+# Towlion Spec Context (v1.0)
+
+Key rules from the Towlion platform specification:
+
+## Required Structure
+- `app/` — FastAPI backend with `Dockerfile` and `main.py`
+- `deploy/` — `docker-compose.yml`, `docker-compose.standalone.yml`, `Caddyfile`, `env.template`
+- `.github/workflows/deploy.yml`
+- `scripts/health-check.sh`
+- `README.md`
+- `frontend/` — optional (Next.js)
+
+## Backend
+- HTTP server on **port 8000**: `uvicorn app.main:app --host 0.0.0.0 --port 8000`
+- Health endpoint: `GET /health` returns `200` with `{"status": "ok"}`
+
+## Environment Variables
+- **Required**: `APP_DOMAIN`, `DATABASE_URL`, `REDIS_URL`
+- **Optional**: `S3_ENDPOINT`, `S3_BUCKET`, `S3_ACCESS_KEY`, `S3_SECRET_KEY`, `EMAIL_API_KEY`, `EMAIL_FROM`
+
+## Dependencies
+- `requirements.txt` (at repo root) or `pyproject.toml`
+- Must include `fastapi` and `uvicorn`
+
+## Docker
+- `app/Dockerfile` is required, `frontend/Dockerfile` if frontend exists
+- Container must expose port 8000 and read config from env vars
+
+## Compose Files
+- `docker-compose.yml` — app containers only (multi-app setup, no infra)
+- `docker-compose.standalone.yml` — full stack with postgres/redis/minio/caddy (for self-hosted forks)
+
+## Validation Tiers
+- **Tier 1**: Structure — required files and directories exist
+- **Tier 2**: Content — YAML valid, port 8000 referenced, env vars present, FastAPI used, no hardcoded secrets
+- **Tier 3**: Runtime — containers build, compose validates, health endpoint responds

.claude/skills/validate/SKILL.md

@@ -0,0 +1,22 @@
+---
+disable-model-invocation: true
+allowed-tools: Bash, Read
+argument-hint: "[path-to-app-repo]"
+description: Run the Towlion spec validator against an application repository
+---
+
+# /validate — Run Spec Validator
+
+Run the Towlion spec conformance validator against an app repo.
+
+## Instructions
+
+1. Determine the target directory:
+   - If `$ARGUMENTS` is provided, use it as the path
+   - Otherwise, default to the current working directory
+2. Run: `python validator/validate.py --tier 2 --dir <target>`
+   - The validator script is at `validator/validate.py` in the platform repo
+   - Use tier 2 by default (structure + content checks)
+   - If the user specifies `--tier 1` or `--tier 3` in arguments, respect that
+3. Show the output to the user
+4. If there are failures, summarize what needs to be fixed