diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index ac5c8d9..a9201e8 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -6,10 +6,10 @@ The project uses British English - strictly. ## Tech Stack -- **Framework**: Next.js 16 (React 19, App Router, React Compiler, TypeScript 6) +- **Framework**: Next.js 16.2 (React 19, App Router, React Compiler, TypeScript 6) - **Styling**: Tailwind CSS 4 - **Auth**: Clerk 7 (`@clerk/nextjs`, `@clerk/ui` shadcn theme) -- **Testing**: Vitest 4 + Testing Library (unit), Playwright 1.58 (E2E) +- **Testing**: Vitest 4.1 + Testing Library (unit), Playwright 1.59 (E2E) - **Quality**: Biome 2.4 (lint + format, replaces ESLint/Prettier) - **Git Hooks**: Lefthook 2.1 (pre-commit: lint, typecheck, unit; pre-push: E2E) - **Deployment**: Vercel (Preview on PR, Production on merge) diff --git a/.claude/commands/coderabbit.md b/.claude/commands/coderabbit.md deleted file mode 100644 index 27198eb..0000000 --- a/.claude/commands/coderabbit.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -description: Evaluate CodeRabbit comment and recommend whether to action it -argument-hint: -allowed-tools: Bash(gh api:*), Read, Glob, Grep ---- - -## 1. Fetch - -Parse `$1` to extract owner, repo, and comment ID. - -```bash -# strips analysis chain, includes diff context -gh api repos/OWNER/REPO/pulls/comments/COMMENT_ID \ - --jq '"## Diff context\n\n```diff\n" + .diff_hunk + "\n```\n\n## Comment\n\n" + (.body | gsub("
\\s*🧩 Analysis chain[\\s\\S]*?
\\s*"; ""))' \ - > x_coderabbit_COMMENT_ID.md -``` - -**Important:** Write `x_coderabbit_COMMENT_ID.md` to the project root. - -## 2. Evaluate - -CodeRabbit AI is not always right. - -Evaluate the comment `x_coderabbit_COMMENT_ID.md` against the context of our codebase and files it references. Assess: - -| Criterion | Question | -|-----------|----------| -| **Contextually valid** | Does it make sense with full codebase context? | -| **Valuable** | Worth doing? Good practice? Or is it over-engineering? | -| **Elegant** | Is the suggested fix pragmatic and clean? | - -## 3. Recommend - -1. **Summary**: Explain the comment (2-4 simple sentences) - -2. **Verdict**: [Action | Skip | Clarify] - - **Action** - Valid and valuable; implement (or with modifications) - - **Skip** - Not applicable, over-engineered, or incorrect - - **Clarify** - Need more information before deciding - -3. **Reasoning**: Why this verdict (2-3 sentences) - -## Output Format - -Well structured, use emojis, if using tables keep width <100 chars for readability. - -## Replying to CodeRabbit on GitHub - -When you recommend skipping a fix, ask whether the user would like to reply to CodeRabbit. - -To reply to a PR review comment, use `in_reply_to` on the pull comments endpoint: - -```bash -gh api repos/OWNER/REPO/pulls/PULL_NUMBER/comments \ - -f body="@coderabbitai ..." \ - -F in_reply_to=COMMENT_ID -``` - -Never reply to a CodeRabbit comment unless confirmed by the user. diff --git a/.claude/commands/commit.md b/.claude/commands/commit.md deleted file mode 100644 index b721a49..0000000 --- a/.claude/commands/commit.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -description: Create git commit message following template -argument-hint: "[additional instructions]" ---- - -# Create a clear Git commit message for **staged** changes - -Additional user instructions: $ARGUMENTS - -1. Analyse staged changes with commands in `` tags -2. Read and adhere to these rules in `` tags -3. Apply commit template `