CLAUDE.md · git:20260914.ff6d12f · 2026-09-14 · sha256 07eec48318229173
CLAUDE.md git:20260914.ff6d12fA
Immutable. This exact content never changes and is served at /api/v1/blob/07eec48318229173.
# CLAUDE.md This repository contains shared skills for GitHub Copilot, Claude Code, and Codex. ## Required Session Start Rule - Every new session in this workspace must begin by reading `LESSON.md`. - Treat `LESSON.md` as required startup context before analysis, planning, edits, validation, reviews, or advisory work. - If `LESSON.md` is missing or unreadable, stop and report that blocker before continuing. ## Required Completion, Sync, and Publish Rule - For every user-requested mutation task in this workspace, complete the requested work in `C:\Users\LOQ\.copilot\skills` first. - After the work is complete, run the repo validation, then sync outward to the downstream skill folders every time. - If the AI agent judges the result satisfactory, commit and push to GitHub without asking for another confirmation. - Treat work as satisfactory only when validation passes, sync completes, the task is complete, no requested step was skipped, no required command was rejected, no unresolved secret/security/privacy issue remains, and the final diff matches the user's request. - Elevate to the user before commit or push when there are security concerns, incomplete work, skipped steps, rejected or blocked required commands, validation/sync failures, unexpected unrelated dirty files that make staging unsafe, or any other reason the work is not satisfactory. - For read-only or advisory tasks with no file changes, do not create empty sync, commit, or push churn; report that no mutation workflow was needed. ## Repository Role - Main branch: `C:\Users\LOQ\.copilot\skills` - New maintained skills must be added or imported here first - Maintained skills live here and are synced outward to downstream targets - Copied official superpowers are tracked here for discovery and Codex sync, but they are not maintained the same way ## Current Counts Snapshot date: `2026-09-14`. Local overlay totals can differ by machine. - Git-tracked catalog in this repository: - `248` tracked skill folders - `216` tracked maintained skills - `32` tracked copied official Superpowers - Live local workspace snapshot (includes local-only overlays such as `gws-*` and `recipe-*` when present): - `306` local skill folders detected - `274` local maintained skills detected - `32` local copied official Superpowers detected Copied official superpowers are identified by the explicit `copied_official_superpowers` list in `scripts/skill-registry.json`, not by whether a skill folder has a `CHANGELOG.md`. All `248` tracked skills use catalog `version: "2.0"`. The `166` pre-existing tracked skills retain their prior catalog baselines; the 66 platform skills retain their import provenance, five Codex Router skills were promoted from the personal Codex root, and one reviewed Codex plugin scanner was vendored. Three official Playwright workflows are now maintained from pinned Microsoft sources. The catalog-wide maintenance baseline is `last_updated: 2026-09-08` for the unchanged catalog; the Playwright entries use `last_updated: 2026-09-12`, and the imported `humanizer` entry uses `last_updated: 2026-09-14`. The `58` local-only Google Workspace overlays retain upstream `version: "0.22.5"` while receiving the same retained-client sections and maintenance date. The tracked imports `docx`, `jupyter-notebook`, `pptx`, and `xlsx` now have finalized canonical provenance in `scripts/skill-registry.json`. The Tavily suite is sourced from `tavily-ai/skills` at commit `ea5e8201b0d3ed9c10b70b71187589bd761fe2d2`. Claude Code sessions using the GLM Coding Plan endpoint should use the external `tvly` CLI, official SDK, or a healthy configured Tavily MCP server; they must not assume subscription-only browser integrations. The selected Matt Pocock import is sourced from `mattpocock/skills` at the current audited commit `6654f6b60cd9d5be8b54c6fafe44346dabeb3b76`. It adds eight cross-client gaps for architecture, domain modeling, prototypes, primary-source research, conflict resolution, handoffs, and agent-document writing. Keep the existing catalog equivalents for TDD, debugging, review, implementation, planning, and skill authoring as the canonical overlapping workflows. The compact `humanizer` workflow is sourced from `blader/humanizer` v3.0.0 at revision `9862685f575c65a8247f90369951df1b3416e3d6`. It is a direct, facts-preserving 25-pattern rewrite workflow; route detection, file edits, preservation checks, and iterative convergence to the broader `avoid-ai-writing` suite. The Playwright package refresh is pinned in `scripts/skill-registry.json`: `playwright-cli` comes from `@playwright/cli@0.1.19` at the tagged `microsoft/playwright-cli` revision, while `playwright-component-testing` and `playwright-trace` come from stable `microsoft/playwright@v1.63.0`. The old broad `playwright` folder is retired; its wrapper and practical catalog guides are retained under `playwright-cli`. The 2026-08-14 source refresh audited current upstream heads and updated the mapped `avoid-ai-writing`, Stitch, Xquik, and Matt Pocock domain-modeling workflows, plus the affected copied Superpowers workflows. Exact-path audits left unchanged mapped skills untouched, and imported support material was reviewed for removed-client paths, credential handling, and no-MCP fallbacks. The 2026-08-16 child reconciliation promoted eleven byte-for-byte verified official skills from the personal Codex root: Supabase, Gemini API, Vercel React performance, and the web-quality audit router plus five focused leaves. The focused leaves remain separate from one another and from the existing React, frontend-design, and visual-review workflows. `frontend-design` is the only general frontend creation and art-direction skill. Use it instead of the retired `frontend-skill` and `premium-frontend-ui` names. Keep `web-design-reviewer` separate for post-implementation visual QA and keep framework, Figma, and Stitch skills for their specialized workflows. The 2026-08-16 related-skill consolidation audit found no safe content merges. Supabase platform/Postgres, Gemini API/Live/Omni, React implementation/ performance, and aggregate/focused web-quality workflows remain separate with explicit routing links. Plugin-managed Supabase and React copies remain external; this parent catalog is canonical for maintained cross-client content. ## 2026-08-20 VoltAgent Platform Import The VoltAgent repository is a discovery index; canonical vendor repositories were pinned before import. `scripts/platform_skill_manifest.py` records 66 selected skills: 8 Vercel, 15 Netlify, 7 MongoDB, the existing current 2-skill Supabase import, 12 Figma, and 24 non-CLI Hugging Face skills. The source commits and exact paths are regenerated into `REFERENCE_SOURCES.md`. CLI gating used commands detected on this laptop: `vercel`, `netlify`, and `supabase` were present; `hf`, `huggingface-cli`, `mongosh`, `mongo`, and `figma` were absent. Vercel, Netlify, and existing Supabase CLI guidance is therefore included, with no Hugging Face, MongoDB, or Figma CLI skill imported. Authentication, runtime installation, and MCP configuration remain explicit user-authorized actions. Repeat imports with `python scripts/import-platform-skills.py --source-root <pinned-clones>`. ## 2026-09-14 Humanizer Import And Catalog Routing - Audited the current `blader/humanizer` main revision `9862685f575c65a8247f90369951df1b3416e3d6` (v3.0.0) and passed its upstream package validator before importing the root skill. - Retained only the runtime-relevant `SKILL.md`, OpenAI-compatible `agents/openai.yaml`, MIT license, and attribution notice. Upstream Claude marketplace metadata, CI files, README duplication, and packaging validator were intentionally omitted; this catalog's validator is authoritative. - Kept `humanizer` separate from `avoid-ai-writing` because the former is a compact direct-rewrite prompt while the latter owns detection, preservation, edit-in-place, and iterative routing workflows. - Re-audited only the three approved personal child roots. The scan found 914 skill files: 819 already represented in the parent, 101 excluded as protected/system/Superpowers material, and zero eligible child-only skills; project-specific paths were not scanned. - No additional Codex plugin skill was vendored in this pass after review for cross-client usefulness and bloat. ## 2026-09-14 Mapped Source Refresh - Checked all `27` recorded upstream heads and refreshed exactly `13` mapped entrypoints whose exact source paths changed: Avoid AI Writing and its detector/router/preservation leaves, NeMo Retriever, MongoDB Search and AI, four Figma workflows, and three Hugging Face cloud workflows. - Updated provenance pins for the remaining `68` mapped skills without rewriting unchanged paths. Avoid AI Writing retains the current runtime CLI/gate and focused local regression helpers; upstream marketplace, CI, package-publishing metadata, and the large evaluation corpus remain omitted to avoid bloat. Its final live pin is `aa4da8b255eb9821f0dae2a059762de900bb5d1f` (v3.35.0); the Awesome Copilot head moved outside mapped paths and is recorded provenance-only. ## 2026-09-12 Playwright CLI Skills And Canonical Consolidation - Installed and verified the latest global `@playwright/cli@0.1.19` package on Node 22, then ran the official `playwright-cli install --skills=agents --global` and `--skills=claude --global` installers. - Imported the package's `playwright-cli` workflow and the stable Playwright component-testing and trace workflows into the parent first. Component testing retains the stable templates and `references/typing.md`; its `mount` fixture correctly requires project-local `@playwright/test`. - Kept the three Playwright activation boundaries separate and retired the old broad `playwright` folder. The sync script prunes only that exact known name from approved mirrors and preserves unknown personal folders. - Reviewed available Claude marketplace and Codex plugin Playwright candidates; none met the cross-client usefulness-without-bloat bar, so no additional plugin skill was vendored. ## 2026-09-08 Catalog Refresh, CodeGraph Index, And Mirror Preparation - Refreshed the nine mapped Awesome Copilot workflows and the Avoid AI Writing v3.33.2 root plus six leaves after exact-path upstream comparison. - Added the current pattern reference and quote-normalization helpers while retaining the flattened-parent router compatibility tests and removing upstream-deleted support files. - Re-audited only `.codex`, `.agents`, and `.claude`; no eligible child-only skills or useful non-overlapping Codex plugin additions were found beyond the existing `agent-skillguard` scanner. - The local CodeGraph index lives under `.codegraph`; commit only its `.gitignore`, keep the generated database ignored, and use `codegraph status`, `codegraph explore`, and `codegraph sync .` for repository-structure work. ## 2026-09-05 Catalog Freshness, Plugin Review, And Mirror Preparation - Rechecked all 24 source heads against their exact mapped paths. Refreshed Avoid AI Writing v3.29 and six focused leaves, both NVIDIA DeepStream workflows, seven Tavily workflows, Gemini API/Live/Omni, and changed Figma support; unrelated head movement remains provenance-only. - Retired `gemini-interactions-api` after its migration content was confirmed in `gemini-api-dev`. The exact name is now in the sync retirement list. - Re-audited only the personal `.codex`, `.agents`, and `.claude` roots. No eligible child-only skills remained after protected/system/project exclusions. Of the reviewed Codex plugin skills, only the self-contained read-only `agent-skillguard` scanner was vendored; its absent upstream rule corpus helper is documented as unavailable. - Current inventory: `245` tracked folders (`213` maintained and `32` copied Superpowers) and `303` live folders (`271` maintained plus `58` local-only overlays). Validation, helper checks, Blender refresh, and three-root sync are required before publishing. - Nineteen CRLF shell helpers were normalized to LF after WSL parsing exposed portability failures; no shell logic was changed. ## 2026-08-31 Catalog Freshness And Corpus Refresh - Rechecked all 24 recorded source heads against live remotes. Only `avoid-ai-writing` had a new installed-path change: its corpus manifest now records small documentation and conversational pre-LLM seeds, and its selector-aware extraction helper and tests were refreshed. - `awesome-copilot` and NVIDIA moved only outside the installed mappings, so their provenance pins were updated without broad content rewrites. - Re-audited `.codex`, `.agents`, and `.claude`; no eligible child-only skills remained. The protected Blender/local-only set, Codex `.system`, Superpowers, and project-specific paths were not promoted or overwritten. ## 2026-08-29 Catalog Refresh And Mirror Repair - Re-audited all 24 recorded source heads against live remotes. Refreshed the exact mapped paths for `avoid-ai-writing` 3.28.0, `x-twitter-scraper`, both Gemini workflows, `react-view-transitions`, and the web-quality support trees. Head movement outside installed paths was recorded without broad rewrites. - Updated the catalog to the current 69-category detector, rendered-Markdown masking, Gemini transcription/Omni/embedding guidance, current React view transition troubleshooting, and field/agentic web-quality references. - The current Xquik source removed its MCP setup surface, so the registry now uses the honest no-MCP fallback instead of advertising an obsolete preferred server. - Re-audited only `.codex`, `.agents`, and `.claude` skill roots. No eligible child-only skills remained. The approved sync restored a missing top-level Codex `doc` copy without touching `.system`, Blender, Superpowers, or any project-specific path. - The required Blender refresh remains at commit `8f778d2405a214b508d4c7d80742be8e43acdd52`: 94 upstream skills plus one separately protected local entry. ## 2026-08-24 Catalog Refresh And Child Promotion - Compared every recorded upstream source head with its exact mapped skill path. Refreshed material changes in `avoid-ai-writing`, the eight selected Matt Pocock workflows, and `x-twitter-scraper`; unrelated source head movement was recorded without rewriting unchanged mapped paths. - Promoted five eligible personal-Codex child skills: `codex-app-threads`, `codex-computer-use`, `codex-in-app-browser`, `codex-router`, and `codex-router-media`. Their host marker files remain outside the parent; package and tree-digest provenance is recorded in the registry. - Child reconciliation scanned only `.codex`, `.agents`, and `.claude` skill roots. It excluded Codex `.system`, the 94-skill Blender overlay plus the separately protected local entry, copied official Superpowers, and all project-specific `C:\Assumption University` paths. No additional eligible skills remained in `.agents` or `.claude`. - The required Blender refresh completed at upstream commit `8f778d2405a214b508d4c7d80742be8e43acdd52` with 94 upstream skills plus one separately protected local entry and no promotion to the parent, shared, or Claude roots. ## Downstream Sync Targets The only approved downstream sync destinations are these three personal-global roots: - `C:\Users\LOQ\.agents\skills` - `C:\Users\LOQ\.codex\skills` - `C:\Users\LOQ\.claude\skills` There must be no downstream sync to any other path. The sync script enforces this list and refuses to write anywhere else. Per-target routing: - Maintained skills sync to `C:\Users\LOQ\.codex\skills`, `C:\Users\LOQ\.agents\skills`, and `C:\Users\LOQ\.claude\skills`. - Copied official superpowers sync only to the `superpowers` subfolder of the shared mirror: `C:\Users\LOQ\.agents\skills\superpowers` (this is inside the approved `.agents\skills` root, not a separate destination). - The six `codex_system_managed_skills` stay authoritative under Codex `.system` and are skipped by top-level Codex mirror writes. Their normalized parent copies still sync to the shared and Claude roots. - Sync removes known catalog-owned top-level route conflicts, but preserves unknown personal skills and all Codex `.system` folders. - Sync removes the exact retired catalog copies `frontend-skill` and `premium-frontend-ui` from these three approved roots. Treat those paths as synced mirrors or branch targets, not as the place to author new maintained skills. Host-provided or plugin-managed skills that are not part of this maintained catalog should stay external unless you intentionally vendor them into this repo. Do not mirror copied official superpowers into `C:\Users\LOQ\.claude\skills` unless you explicitly want local overrides over Claude's plugin-managed copies. ## Codex-Only Blender Skills Overlay - The `arjun988/blender-skills` pack is an explicit exception to normal child promotion. - Its 94 upstream skills plus the separately protected local `raw-scan-to-aaa-preserve-texture` entry (95 protected names total) must remain installed only under `C:\Users\LOQ\.codex\skills`, with its source checkout under `C:\Users\LOQ\.codex\vendor\blender-skills`. - Never promote these skill names into this parent catalog and never sync them to `C:\Users\LOQ\.agents\skills` or `C:\Users\LOQ\.claude\skills`. - `scripts/skill-registry.json` records the protected names and the Codex-only source configuration; generic promotion and sync tooling must honor that boundary. - During parent source-maintenance or "update all skills" work, run `scripts/update-codex-local-blender-skills.ps1`. It fetches upstream, refreshes only the owned Codex copies and shared Blender references, updates the ownership manifest and source commit, and verifies that no Blender skill escaped to a forbidden root. ## Claude Code With GLM Coding Plan - The GLM Coding Plan endpoint changes the model provider through Claude Code's Anthropic-compatible environment variables. It does not change the personal skill root: use `C:\Users\LOQ\.claude\skills`. - Do not assume native Claude in Chrome is available. Anthropic's current native integration requires direct paid-plan and authentication prerequisites that third-party API endpoints do not satisfy. - Inspect `claude mcp list` and the active session tool list before naming or calling a browser tool. A connected external Chrome DevTools, Puppeteer, or Playwright MCP can provide browser automation; a search or reader tool cannot publish through an authenticated LinkedIn session. - Keep login, CAPTCHA, upload, and final-submit actions confirmation-gated. Stop at a manual handoff when no healthy authenticated browser surface is exposed. ## Upstream-Only Skill Sources Normal child promotion is limited to the personal `.codex`, `.agents`, and `.claude` roots. Project-local paths such as `C:\Assumption University` are not scanned or written unless a later user request explicitly places them in scope. To pull a skill from such a root into this parent catalog, promote it upstream and record provenance: - Use `python scripts/promote-child-skills.py --map <source> <name>` for an explicit child skill or `--discover <root>` to flatten a categorized skill tree. Normalize invalid underscore or title-style names to lowercase hyphen-case. - Then run `python scripts/update-skill-registry.py` to refresh provenance, copied-official classification, and `REFERENCE_SOURCES.md`. The only downstream sync call is to the three approved personal-global roots: ```powershell powershell -ExecutionPolicy Bypass -File .\scripts\sync-skills.ps1 ``` ## CodeGraph Repository Index When `.codegraph/` exists, use CodeGraph before broad text searches or source reads for repository-structure questions. `codegraph explore "<question>"` provides symbol and call-path context; it does not replace direct file review, the validator, helper tests, or the real mirror sync. Commit only `.codegraph/.gitignore`. The generated `codegraph.db` is ignored, machine-local, and must not be copied to any downstream skill root. Use `codegraph status` to check freshness and `codegraph sync .` after source changes. Initialize only this catalog with `codegraph init -y .`; do not index project-specific `C:\Assumption University` paths. Set `CODEGRAPH_TELEMETRY=0` for a no-telemetry local run. ## Catalog Skill Expectations Every skill folder in this catalog should have: - `SKILL.md` - `CHANGELOG.md` Recommended support folders: - `references/` - `scripts/` Optional: - `examples/` - `LICENSE.txt` ## SKILL.md Rules Every `SKILL.md` in this repo should: - use valid YAML frontmatter - keep the `name` aligned with the folder name - include the catalog frontmatter fields: `name`, `version`, `last_updated`, `tags`, and `description` - use only approved extra top-level metadata fields when needed: `license`, `compatibility`, and `metadata` - use activation-focused descriptions - include the generated portability section - include the MCP or no-MCP fallback section - include `## Anti-Patterns` - include `## Verification Protocol` - end with `## Related Skills` ## MCP Rules When editing MCP-aware skills: 1. Name the preferred MCP server explicitly. 2. Add a practical fallback path for environments without that MCP surface. 3. Avoid claiming a host-specific tool wrapper exists unless you verified it. 4. Prefer local scripts, CLIs, or browser workflows as the fallback evidence path. The MCP mapping source lives in `scripts/skill-registry.json`. ## Validation Workflow After meaningful changes: 1. Run `python scripts/validate-skills.py` 2. Sync outward if the repo is in a good state For a catalog-wide documentation refresh, treat validation and sync as required even when the inventory counts stay the same. The validator now expects the catalog frontmatter fields plus the portability, MCP, Anti-Patterns, Related Skills, and `CHANGELOG.md` baseline. Catalog policy also expects each `SKILL.md` to include `## Verification Protocol` immediately after `## Anti-Patterns`. Changelog entries should use `Added`, `Changed`, and `Fixed` sections only; the validator rejects `### Tested` and `### Verified` headings. The tracked imports `docx`, `jupyter-notebook`, `pptx`, and `xlsx` now validate against the shared catalog structure and have finalized provenance metadata. After adding a new maintained skill: 1. Install or import it into this repo first 2. Prefer the canonical upstream source when a discovery list points to a stronger maintained original 3. Update `REFERENCE_SOURCES.md` and `scripts/skill-registry.json` when the source was external 4. Smoke-test any bundled helper scripts or local fallback workflow 5. Update root docs and the relevant changelogs 6. During source maintenance, run `scripts/update-codex-local-blender-skills.ps1` 7. Then sync it to the downstream targets ## Documentation Rules When repo behavior, counts, sync flow, portability, or supported clients change: - update `README.md` - update `AGENTS.md` - update `CHANGELOG.md` - update `CLAUDE.md` - update `LESSON.md` - update `MIGRATION.md` when a breaking client or sync boundary changes ## Codex Notes - Treat `C:\Users\LOQ\.codex\skills` as the primary Codex install root. - Treat `C:\Users\LOQ\.agents\skills` as a shared mirror that other local workflows can reuse. - Do not describe the shared mirror as the only Codex path in repo docs or skill guidance. - The Codex install root can contain extra local skills outside this catalog, so verify sync by checking the expected maintained set rather than raw folder totals alone. ## Related Repo Files - `README.md`: catalog and maintenance commands - `CHANGELOG.md`: repo-wide change history - `CONTRIBUTING.md`: contribution workflow and repo validation expectations - `LESSON.md`: maintenance lessons and gotchas - `MIGRATION.md`: version 2.0 breaking migration and rollback guidance - `SECURITY.md`: vulnerability reporting and sensitive-disclosure guidance