chore: realign .claude config to the Optia extension#2
Merged
Conversation
Replace leftover Figma-to-React framework tooling with config that actually describes this MV3 Chrome extension. - Rewrite CLAUDE.md: real commands (cd app; dual dev modes), architecture map, SEO scoring model, testing + release notes, and a 'does NOT use' list. - Add project skills: chrome-extension-dev (MV3 message/storage/SW lifecycle contracts) and testing-chrome-extension (real Vitest/chrome-mock/openai-mock patterns). - Add commands: /release-extension (version sync + store checklist) and /add-seo-check (the cross-file contract). Fix /lint (ESLint-only, no Prettier) and /test (Vitest-only, run from app/). - Fix .mcp.json drift: drop the Figma servers (they inject 'use Figma' prompts), declare chrome-devtools (the MCP actually used). - Replace the broken PostToolUse hook with .claude/hooks/guards.mjs: blocks root releases, reminds on extractor-twin and manifest version/permission edits. - Prune 30 irrelevant agents (keep 14), the 9 Figma/React skills, dead commands, scripts/ + templates/ scaffolding, Figma/React docs, and the root release config. Based on a multi-agent audit of the repo. No app/ code changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Realigns the
.claude/configuration (andCLAUDE.md) to describe this MV3 Chrome extension instead of the leftover generic Figma-to-React framework template it was copied from. Based on a multi-agent audit of the repo. Noapp/code changes — config/docs only.Why
Every file an agent read for "context" pointed at the wrong project:
CLAUDE.mddocumented Next.js/Storybook/Figma commands that don't exist here, the 9 skills auto-fired Figma/React guidance on everyday keywords,.mcp.jsondeclared Figma servers (which inject "use Figma whenever UI is mentioned" prompts) while omitting the chrome-devtools MCP actually in use, the lone hook was broken, and the root release config taggedtemplate-v*without bumpingmanifest.json.What changed
CLAUDE.md— full rewrite: real commands (cd app;pnpm dev= web preview at/dev.htmlvspnpm dev:ext= crxjs), architecture map, SEO scoring model, testing + release notes, and an explicit "this repo does NOT use" list.chrome-extension-dev(MV3 message catalog, storage schema, SW/side-panel lifecycle, the two-extractor rule, dev-mode detection) andtesting-chrome-extension(real chrome-mock / load-order / OpenAI-mock / RTL patterns). Both grounded in actualfile:linereferences./release-extension(version-sync + zip + Web Store checklist) and/add-seo-check(the ~8-file cross-file contract). Fixed/lint(ESLint-only, no Prettier) and/test(Vitest-only, fromapp/)..mcp.json— dropped the Figma servers, declaredchrome-devtools.$TOOL_INPUT-grepping hook with.claude/hooks/guards.mjs: blocksstandard-version/release runs from the repo root, and reminds on twin-extractor andmanifest.jsonversion/permission edits.build-from-figma/create-blog-article, thescripts/+templates/scaffolding, the Figma/React docs, and the root release config + vestigial root lockfile.Net: 108 files, −15.7k / +0.6k. JSON + hook validated;
app/untouched so the 309 tests are unaffected.🤖 Generated with Claude Code