Add Playwright MCP server config (#215)

Adds a project-scoped .mcp.json registering the Playwright MCP server
so browser automation tooling is available to anyone using Claude Code
in this repo.

Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

.github/workflows/ci-test.yml

@@ -14,13 +14,14 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version-file: '.tool-versions'
+          cache: 'pnpm'
       - name: Install Dependencies
-        run: |
+        run: pnpm install --frozen-lockfile
-          npm install -g yarn
-          yarn install
       - name: Lint solution
-        run: yarn check
+        run: pnpm check

.github/workflows/deploy.yml

@@ -13,16 +13,17 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version-file: '.tool-versions'
+          cache: 'pnpm'
       - name: Install Dependencies
-        run: |
+        run: pnpm install --frozen-lockfile
-          npm install -g yarn
-          yarn install
       - name: Build solution
-        run: yarn build
+        run: pnpm build
       - name: Archive artifacts
         uses: actions/[email protected]
         with:

.gitignore

@@ -2,8 +2,6 @@
 logs
 *.log
 npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
 pnpm-debug.log*
 lerna-debug.log*
 
@@ -22,12 +20,3 @@ dist-ssr
 *.njsproj
 *.sln
 *.sw?
-
-# Yarn 2+
-.pnp.*
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/sdks
-!.yarn/versions

.husky/pre-commit

@@ -1 +1 @@
-yarn check
+pnpm check

.mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "playwright": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "@playwright/mcp@latest"
+      ],
+      "env": {}
+    }
+  }
+}

.yarnrc.yml

@@ -1,2 +0,0 @@
-nodeLinker: node-modules
-yarnPath: .yarn/releases/yarn-3.5.1.cjs

CLAUDE.md

@@ -4,14 +4,14 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Commands
 
-This project uses **Yarn 3 (Berry)** — pinned via `packageManager` in `package.json`. Use `yarn`, not `npm`.
+This project uses **pnpm** — pinned via `packageManager` in `package.json` (enable it with `corepack enable`). Use `pnpm`, not `npm` or `yarn`.
 
-- `yarn dev` — start the Vite dev server
+- `pnpm dev` — start the Vite dev server
-- `yarn build` — production build to `dist/`
+- `pnpm build` — production build to `dist/`
-- `yarn preview` — serve the production build locally
+- `pnpm preview` — serve the production build locally
-- `yarn check` — type-check with `svelte-check` (the only "lint"/CI gate; there is no ESLint/Prettier and no test suite)
+- `pnpm check` — type-check with `svelte-check` (the only "lint"/CI gate; there is no ESLint/Prettier and no test suite)
 
-`yarn check` runs automatically on `git commit` via the Husky `pre-commit` hook, and on every PR / push to `main` via the `ci-test` workflow. There are no unit tests, so `yarn check` is the check to run before considering a change done.
+`pnpm check` runs automatically on `git commit` via the Husky `pre-commit` hook, and on every PR / push to `main` via the `ci-test` workflow. There are no unit tests, so `pnpm check` is the check to run before considering a change done.
 
 ## Architecture
 
@@ -28,8 +28,8 @@ A single-page, statically-generated personal résumé site — no router, no bac
 - Prefer `<script lang="ts">` with a typed props object for new components (see `components/Link.svelte`, `components/Hero.svelte`). Some older section files use plain `<script>` — match the file you are editing.
 - **Tailwind CSS v4** with **no config file**. It is enabled via the `@tailwindcss/vite` plugin and `@import "tailwindcss"` in `src/app.css`; customize through CSS, not a `tailwind.config.js`. `tailwind-merge` is available for conditional class composition.
 - Styling is Tailwind utility classes in markup; the dark theme base (`bg-gray-950 text-white`) is set on `<body>` in `index.html`.
-- `checkJs` is on and `.js`/`.svelte` files are type-checked — keep JSDoc/types valid so `yarn check` passes.
+- `checkJs` is on and `.js`/`.svelte` files are type-checked — keep JSDoc/types valid so `pnpm check` passes.
 
 ## Deploy
 
-Pushing to `main` triggers the `deploy` workflow: `yarn build` → upload `dist/` → GitHub Pages (https://dankotowski.dev). Note CI uses Node 20, while local dev is pinned to Node 22.14.0 in `.tool-versions`.
+Pushing to `main` triggers the `deploy` workflow: `pnpm build` → upload `dist/` → GitHub Pages (https://dankotowski.dev). CI reads its Node version from `.tool-versions` (pinned to 22.14.0), matching local dev — pnpm 11 requires Node >=22.13.

package.json

@@ -23,7 +23,7 @@
     "typescript": "^5.8.2",
     "vite": "^6.2.4"
   },
-  "packageManager": "[email protected]",
+  "packageManager": "[email protected]",
   "dependencies": {
     "tailwind-merge": "^3.1.0"
   }

pnpm-workspace.yaml

@@ -0,0 +1,5 @@
+# esbuild ships its native binary via an optional dependency; its postinstall
+# is only a launcher optimization. Allowed so pnpm 11 doesn't block install on
+# the undecided build script.
+allowBuilds:
+  esbuild: true