Integrate CV Builder MVP foundation and close PR cleanup pass

.claude/commands/evaluate-cv.md

@@ -0,0 +1,16 @@
+---
+description: Score a resume against the CV Builder rubric, fully locally
+argument-hint: <path-to-resume> [--jd <path-to-job-description>]
+---
+
+Evaluate the resume using the `cv-evaluation` skill.
+
+Arguments: $ARGUMENTS
+
+- The first argument is the path to the resume (PDF, markdown, or text).
+- An optional `--jd <path>` adds a job description as keyword context only.
+
+Read the file(s), run the extract → detect → score → validate-claims pipeline,
+validate the result against `EvalResultSchema`, then present the overall score,
+the per-dimension breakdown, the top issues with fixes, and any unsupported
+claims. Nothing leaves this machine.

.claude/commands/setup-profile.md

@@ -0,0 +1,15 @@
+---
+description: Gather a resume to evaluate, three ways
+argument-hint: [path-to-file]
+---
+
+Help the user get a resume ready for `/evaluate-cv`. Pick the path that fits:
+
+1. **File** — if `$ARGUMENTS` names a file, read it and confirm what you found.
+2. **Paste** — if they pasted resume text, use it directly.
+3. **Interview** — if they have nothing prepared, ask a short, focused set of
+   questions (roles, dates, what they built, measurable outcomes, links) and
+   assemble a plain-text resume from their answers.
+
+Once you have the resume text, save it to a file the user chooses and tell them
+to run `/evaluate-cv <that-file>`. Don't invent details they didn't give you.

.claude/settings.json

@@ -0,0 +1,17 @@
+{
+  "permissions": {
+    "allow": ["Read", "Glob", "Grep"]
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/welcome.sh\""
+          }
+        ]
+      }
+    ]
+  }
+}

.claude/skills/cv-evaluation/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: cv-evaluation
+description: Evaluate a resume against the CV Builder rubric and return a scored, schema-valid EvalResult. Use when the user wants their CV or resume scored, critiqued, or checked for ATS issues and unsupported claims.
+---
+
+# CV Evaluation
+
+Run a resume through the same four-step evaluation the hosted product uses,
+entirely locally. Everything you need lives in this repo — read the source, don't
+guess.
+
+## Inputs
+
+- A resume file (PDF, markdown, or plain text). For PDF, read the text content.
+- Optionally a job description, used only as keyword context (Phase 1 does not
+  fit-score against a JD).
+
+## Pipeline
+
+1. **Extract.** Apply `packages/prompts/prompts/extract.md` to the raw resume
+   text to produce a structured `Resume`.
+2. **Detect archetype.** Match the resume against the role archetypes in
+   `packages/intelligence/src/archetypes/`. Pick the best fit; default to
+   Software Engineer when there's no clear signal. See [archetypes](./archetypes.md).
+3. **Score.** Apply `packages/prompts/prompts/score.md` with the detected
+   archetype's weights and the rubric. See [rubric](./rubric.md) and
+   [scoring](./scoring.md). Surface **at least 3** issues, each quoting the exact
+   resume text and giving a concrete fix.
+4. **Validate claims.** Apply `packages/prompts/prompts/validate-claims.md` to
+   flag unsupported claims. See [claim-validation](./claim-validation.md).
+
+## Output
+
+Produce one `EvalResult` (schema: `packages/schemas/src/evaluation.ts`). It must
+carry `rubricVersion` and `archetypeVersion`. Validate the object against
+`EvalResultSchema` before presenting it — never show an unvalidated result.
+
+Run the validation from inside `packages/schemas` (zod only resolves there under
+pnpm's layout). Pipe the JSON to node over stdin rather than writing it to a
+file, so nothing derived from the resume touches the working tree. If
+dependencies aren't installed, don't error out: check the object field by field
+against `evaluation.ts` instead, and tell the user that running `pnpm install`
+enables strict validation.
+
+Then summarize for the user: overall score, the per-dimension breakdown, the top
+issues with their fixes, and any unsupported claims.

.claude/skills/cv-evaluation/archetypes.md

@@ -0,0 +1,10 @@
+# Archetypes
+
+Each role archetype (keywords, dimension weights, action verbs, anti-patterns)
+is one file in `packages/intelligence/src/archetypes/`. Read the relevant file —
+the weights there drive the overall score, so use them exactly.
+
+To detect the archetype: count how many of each archetype's keywords appear in
+the resume and pick the highest. The same heuristic is implemented in
+`packages/intelligence/src/detect.ts` (`detectArchetype`). When nothing clearly
+matches, use Software Engineer.

.claude/skills/cv-evaluation/claim-validation.md

@@ -0,0 +1,9 @@
+# Claim Validation
+
+The prompt and the rules for what counts as an unsupported claim are in
+`packages/prompts/prompts/validate-claims.md` (rules sourced from
+`packages/intelligence/src/validators/claims.ts`).
+
+Goal: catch what a recruiter would quietly distrust — a metric with no scope, a
+tool listed but never used in a bullet, a seniority claim with no team size or
+reach. For each flagged claim, say what's missing, not just that it's weak.

.claude/skills/cv-evaluation/rubric.md

@@ -0,0 +1,8 @@
+# Rubric
+
+The six dimensions, their 0–5 anchors, and the current `RUBRIC_VERSION` are
+defined in `packages/intelligence/src/rubric.ts`. Read that file — it is the
+source of truth. Don't reproduce the anchors from memory.
+
+Score each dimension on its own 0–5 scale, then weight by the archetype (see
+[archetypes](./archetypes.md)) to get the overall 0–5 score.

.claude/skills/cv-evaluation/scoring.md

@@ -0,0 +1,12 @@
+# Scoring
+
+The scoring instructions and exact output shape are in
+`packages/prompts/prompts/score.md`. Fill its `{{...}}` placeholders from the
+detected archetype's weights and the rubric.
+
+Hold the line on quality:
+
+- Every issue quotes the exact resume text it's about — no paraphrasing.
+- Every issue has a concrete fix, not "consider improving this".
+- Overall score = sum(dimension score × weight), on the 0–5 scale.
+- Be honest. A weak resume should score low; inflating it doesn't help anyone.

.claude/welcome.sh

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# Emits the CV Builder menu as a SessionStart hook systemMessage, shown to the
+# user when they open Claude Code at the repo root.
+
+# No jq → skip the banner rather than break the session start.
+command -v jq >/dev/null 2>&1 || exit 0
+
+read -r -d '' MENU <<'EOF'
+CV Builder — evaluate your resume locally and privately. Nothing leaves your machine.
+
+  /evaluate-cv <resume.pdf|.md|.txt> [--jd <job.md>]   Score a resume against the rubric
+  /setup-profile                                       Assemble a resume if you don't have a file yet
+
+No build or install needed to evaluate.
+
+What would you like to do?
+EOF
+
+jq -n --arg msg "$MENU" '{systemMessage: $msg}'

.coderabbit.yaml

@@ -1,10 +1,12 @@
-# yaml-language-server: $schema=https://docs.coderabbit.ai/schema.json
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
 language: en-US
+early_access: false
 
 reviews:
   profile: chill
   request_changes_workflow: false
   high_level_summary: true
+  poem: false
   review_status: true
   auto_review:
     enabled: true
@@ -13,6 +15,38 @@ reviews:
       - main
   path_filters:
     - "!**/pnpm-lock.yaml"
+    - "!**/dist/**"
+    - "!**/.turbo/**"
+    - "!**/node_modules/**"
+    - "!**/*.snap"
+  path_instructions:
+    - path: "packages/core/**"
+      instructions: >
+        This is the core CV evaluation/builder logic. Prioritize correctness of
+        rules, evaluator scoring, and types. Flag changes to public APIs in
+        src/index.ts and anything in src/types.ts that could break consumers.
+        New rules/archetypes/evaluator behavior should have matching vitest tests.
+    - path: "packages/cli/**"
+      instructions: >
+        CLI for the CV builder. Watch for unhandled errors, confusing output,
+        and missing input validation. Behavior changes should be covered by tests.
+    - path: "packages/web/**"
+      instructions: >
+        Web frontend. Check accessibility, error/loading states, and that UI
+        stays consistent with the core package's data model.
+    - path: "**/*.md"
+      instructions: >
+        Docs for an open-source project. Check clarity and that setup/commands
+        match the actual scripts in package.json.
+  tools:
+    eslint:
+      enabled: true
+    markdownlint:
+      enabled: true
 
 chat:
   auto_reply: true
+
+knowledge_base:
+  learnings:
+    scope: auto

.github/ISSUE_TEMPLATE/bug_report.md

@@ -3,7 +3,7 @@ name: Bug Report
 about: Something isn't working correctly
 title: "[Bug] "
 labels: bug
-assignees: ''
+assignees: ""
 ---
 
 ## What happened?

.github/ISSUE_TEMPLATE/feature_request.md

@@ -3,7 +3,7 @@ name: Feature Request
 about: Suggest a new feature or improvement
 title: "[Feature] "
 labels: enhancement
-assignees: ''
+assignees: ""
 ---
 
 ## Problem

.github/ISSUE_TEMPLATE/new_archetype.md

@@ -3,7 +3,7 @@ name: New Role Archetype
 about: Add a new role type (e.g., "Mobile Engineer", "Security Engineer")
 title: "[Archetype] "
 labels: archetype, good first issue
-assignees: ''
+assignees: ""
 ---
 
 ## Role name
@@ -26,14 +26,14 @@ List the key terms recruiters look for in this role:
 
 How should the 6 dimensions be weighted for this role?
 
-| Dimension | Suggested weight |
-|-----------|-----------------|
-| Shipped Evidence | ? |
-| Quantified Impact | ? |
-| Tooling Visibility | ? |
-| ATS Compatibility | ? |
-| Keyword Match | ? |
-| Public Proof | ? |
+| Dimension          | Suggested weight |
+| ------------------ | ---------------- |
+| Shipped Evidence   | ?                |
+| Quantified Impact  | ?                |
+| Tooling Visibility | ?                |
+| ATS Compatibility  | ?                |
+| Keyword Match      | ?                |
+| Public Proof       | ?                |
 
 ## Action verbs (10+)
 

.github/ISSUE_TEMPLATE/new_rule.md

@@ -3,7 +3,7 @@ name: New Evaluation Rule
 about: Propose a new CV evaluation rule (anti-pattern or positive pattern)
 title: "[Rule] "
 labels: rules, good first issue
-assignees: ''
+assignees: ""
 ---
 
 ## Rule type

.github/PULL_REQUEST_TEMPLATE.md

@@ -4,7 +4,7 @@ Brief description of the change.
 
 ## Related issue
 
-Closes #___
+Closes #\_\_\_
 
 ## Type of change
 
@@ -25,5 +25,5 @@ Closes #___
 
 ## Screenshots (if UI change)
 
-Before | After
---- | ---
+| Before | After |
+| ------ | ----- |

.github/workflows/ci.yml

@@ -29,4 +29,6 @@ jobs:
 
       - run: pnpm test
 
+      - run: pnpm eval
+
       - run: pnpm build

CLAUDE.md

@@ -0,0 +1,25 @@
+# CV Builder
+
+Open source, privacy-first resume evaluator. This repo doubles as a **power-user
+pack**: clone it, open Claude Code here, and evaluate your resume locally with
+your own agent — nothing leaves your machine.
+
+## Power-user commands
+
+- `/evaluate-cv <resume.pdf|.md|.txt> [--jd <job.md>]` — score a resume against
+  the rubric and surface issues + unsupported claims.
+- `/setup-profile` — assemble a resume if you don't have a file ready.
+
+## No build needed for evaluation
+
+The `cv-evaluation` skill (`.claude/skills/cv-evaluation/`) reads the prompts in
+`packages/prompts/prompts/` and the rubric/archetypes in
+`packages/intelligence/src/` straight from the repo, and returns an `EvalResult`
+validated against `packages/schemas`. `pnpm install` is only needed to run the
+package tests or the web app — not for the power-user flow.
+
+## Repo shape
+
+pnpm + turbo monorepo. `packages/schemas` (contract) → `packages/intelligence`
+(rubric + archetypes) → `packages/prompts` (the prompt pack) → the skill ties
+them together.