docs: sync README, CLAUDE.md, AGENTS.md with latest skill changes

- Add 93-tui-designer to all doc files and directory layouts
- Remove phantom 42-jamie-journal-editor (directory never existed)
- Update GTM directory names: 61-gtm-manager → 61-gtm-editor,
  62-gtm-guardian → 62-gtm-validator in CLAUDE.md layout
- Fix skill count: README 64→62, AGENTS.md 52→62
- Add .claude/commands/ slash command definitions
- Add SEO comprehensive audit gotcha notes (JHR, SLA)

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

custom-skills/11-seo-comprehensive-audit/code/gotcha/JHR-josunhotel.md

@@ -0,0 +1,28 @@
+# JHR — josunhotel.com Gotchas
+
+Client: **JHR** (Josun Hotels & Resorts / 조선호텔앤리조트)
+Domain: josunhotel.com + subdomains (gjb, gjj, jpg, grp)
+
+---
+
+## 1. Intentionally Truncated Directory Names in robots.txt
+
+**Date discovered**: 2026-03-20
+**Audit ID**: COMP-20260320-001
+
+The following `Disallow` paths in robots.txt look like typos but are **intentional directory names** on the server:
+
+| robots.txt path | Looks like it should be | Actual status |
+|-----------------|------------------------|---------------|
+| `/cnfirm` | `/confirm` | **Intentional** — real directory name |
+| `/mber` | `/member` | **Intentional** — real directory name |
+
+**Do NOT recommend renaming these** in audit reports. The server-side application uses these truncated names by design.
+
+### Context
+
+The josunhotel.com backend (Java/.do endpoints) uses shortened directory names for certain internal paths. This is likely a legacy naming convention from the original application architecture.
+
+### Audit Impact
+
+When running Technical SEO audits (Stage 1), skip the "typo in Disallow paths" finding for `/cnfirm` and `/mber`. These are valid paths that correctly block crawler access to confirmation and member-related pages.

custom-skills/11-seo-comprehensive-audit/code/gotcha/JHR-lescapehotel.md

@@ -0,0 +1,30 @@
+# JHR — lescapehotel.com Gotchas
+
+Client: **JHR** (Josun Hotels & Resorts)
+Domain: lescapehotel.com → les.josunhotel.com (migrated)
+
+---
+
+## 1. Domain Migration Complete — Monitor Redirects & Link Juice
+
+**Date discovered**: 2025-12-14
+**Updated**: 2026-03-20
+**Status**: Migration COMPLETE
+
+The L'Escape Hotel domain migration from `lescapehotel.com` to `les.josunhotel.com` has been completed.
+
+### What to Monitor (Watchtower)
+
+- **301 redirects**: Verify all old lescapehotel.com URLs still 301 to correct les.josunhotel.com counterparts
+- **Link juice preservation**: Check that backlinks from external sites pointing to lescapehotel.com are passing authority through redirects
+- **Redirect chains**: Watch for double redirects (lescapehotel.com → old intermediate → les.josunhotel.com)
+- **GSC coverage**: Monitor les.josunhotel.com indexing in Google Search Console
+- **Referring domains**: Track referring domain count in Ahrefs/GSC to ensure backlink equity is maintained
+
+### Audit Checklist (Run Periodically)
+
+1. Sample 10-20 old lescapehotel.com URLs — verify 301 status
+2. Check for any 404s on les.josunhotel.com that should have redirects
+3. Compare organic traffic trends pre/post migration
+4. Verify old sitemap URLs are all redirecting properly
+5. Check Naver Search Advisor for indexing status

custom-skills/11-seo-comprehensive-audit/code/gotcha/SLA-shillahotels.md

@@ -0,0 +1,40 @@
+# SLA — shillahotels.com Gotchas
+
+Client: **SLA** (Shilla Hotels & Resorts / 신라호텔)
+Domain: shillahotels.com
+
+---
+
+## 1. www1 / www2 Are Dev/Stage Hosts, NOT Production
+
+**Date discovered**: 2026-03-20
+**Context**: SLA new integrated website under construction
+
+The Shilla Hotels domain uses numbered subdomains for development environments:
+
+| Subdomain | Purpose | Status |
+|-----------|---------|--------|
+| `www1.shillahotels.com` | Development | Active — deployed intermittently |
+| `www2.shillahotels.com` | Staging | Active — deployed intermittently |
+| `www.shillahotels.com` | Production (current) | Live |
+| TBD (new integrated site) | Production (future) | **Target launch: end of June 2026** |
+
+**Do NOT run technical SEO audits against www1 or www2** unless specifically instructed. These are pre-production environments and will have:
+- No robots.txt
+- No XML sitemap
+- Incomplete meta tags
+- Missing canonical/hreflang tags
+
+These are expected states for dev/stage, not audit findings.
+
+### When to Scan
+
+The client will notify when www1/www2 need technical SEO element checks. Do NOT proactively audit these subdomains.
+
+## 2. No robots.txt or Sitemap on Dev/Stage Hosts
+
+**Date discovered**: 2026-03-20
+
+robots.txt and sitemap.xml are intentionally not deployed to www1 and www2. This is expected for pre-production environments. Do NOT flag as issues.
+
+Wait for client instruction before scanning technical SEO elements on these hosts.