Merge pull request #32 from New1Direction/feat/brand-identity

feat(brand): Mono Ink identity — Vee-eye icon + scan animation, default theme, voice

Author: New1Direction

CHANGELOG.md

@@ -4,15 +4,17 @@ Every release of RepoLens, newest first. Want the friendly highlights instead of
 the full detail? See **[What's new](README.md)** in the README.
 
 This project follows [Semantic Versioning](https://semver.org/) and groups changes
-by theme. Dates are when the release landed on `main` — 1.1.0 through 1.6.0 shipped
+by theme. Dates are when the release landed on `main`. 1.1.0 through 1.6.0 shipped
 the same day, as a rapid burst of improvements, so they share a date.
 
 ## [Unreleased]
 
 ### Added
 
+- **Mono Ink identity.** RepoLens ships a new dark-tile lens icon, a "Mono Ink" default theme (cool near-black, white, and cobalt), and a wordmark lockup. The toolbar icon now animates only while a scan runs: the aperture grows and spins and the ring breathes grey to blue, then it resets to static. Turn the animation off in **Options**, and it honors your OS reduced-motion setting. The other 13 themes stay one click away.
+- **A warmer Vee.** Vee's onboarding copy reads like a person now. The repo also vendors the stop-slop writing standard under `docs/style/` so the voice stays consistent.
 - **Vee-guided first-run walkthrough.** New users are met by Vee on their first Library open; the coachmark steps through a seeded demo repo (Library card → Verdict tab → Blueprint canvas) with plain narration and a spotlight on each target element. Implemented in `onboarding.js` / `coachmark.js`; copy lives in `onboarding-copy.js`.
-- **Milestone "power tour"** offered after approximately five real scans: a second coachmark sequence introducing the cross-library tools — Ask, Corkboard (Alternatives / Synergies), multi-select Compare, Radar / auto-organize, and Discover.
+- **Milestone "power tour"** offered after approximately five real scans: a second coachmark sequence introducing the cross-library tools: Ask, Corkboard (Alternatives / Synergies), multi-select Compare, Radar / auto-organize, and Discover.
 
 ---
 

README.md

@@ -1,10 +1,10 @@
 <div align="center">
 
-# 🔭 RepoLens
+# RepoLens
 
-### One click opens the case file on any repo.
+### Click any repo. Get a straight answer on whether to use it.
 
-**The verdict · the evidence · the red flags · how it's actually built — in plain English, before the README's pitch.**
+**The verdict, the evidence, the red flags, and how it's built. In plain English, before the README's pitch.**
 
 ![Chrome Manifest V3](https://img.shields.io/badge/Chrome-Manifest_V3-1a73e8?logo=googlechrome&logoColor=white)
 ![Zero build](https://img.shields.io/badge/build-none-0e1722)
@@ -17,9 +17,9 @@
 
 ---
 
-RepoLens is a **Manifest V3 Chrome extension**. Land on a GitHub, GitLab, npm, or PyPI page, click the toolbar icon, and it reads the repo, runs it past the AI provider of your choice, and opens a tab with a **verdict-first** breakdown — it opens with a straight answer (*should you use this?*) before any prose, not the README's marketing.
+RepoLens is a **Manifest V3 Chrome extension**. Open a GitHub, GitLab, npm, or PyPI page and click the toolbar icon. RepoLens reads the repo, runs it past the AI provider you picked, and opens a tab that leads with a straight answer: should you use this? You see the verdict before any of the README's pitch.
 
-> Stars tell you a project is popular. They don't tell you whether it fits *your* problem. RepoLens answers the question you actually have: **should I use this, and what am I signing up for?**
+> Stars tell you a project is popular. They don't tell you whether it fits your problem. RepoLens answers the question you have: should I use this, and what am I signing up for?
 
 ---
 
@@ -41,7 +41,7 @@ A scan opens to a **verdict landing** and fans out into focused tabs:
 
 Plus **SKTPG** (a one-tap State / Known-pitfalls / Trajectory / Proof / Growth read), framework lenses, and capability re-tagging.
 
-**First run:** Vee walks new users through a seeded demo repo (Library → Verdict → Blueprint) via a coachmark tour. After roughly five real scans a second "power tour" introduces the cross-library tools: Ask, Corkboard analysis, multi-select compare, Radar, and Discover.
+**First run:** Vee, the lens mascot, walks you through a seeded demo repo (Library, then Verdict, then Blueprint) with a short coachmark tour. After about five real scans, a second power tour shows you the cross-library tools: Ask, Corkboard, multi-select compare, Radar, and Discover.
 
 ---
 
@@ -61,7 +61,7 @@ A correctness, security, and tooling pass from a full code audit — fixes only,
 ### v1.7.0 — Boards, Vee & a motion pass
 
 - 🗂️ **Collections ("Boards").** Group the repos you're evaluating together and filter the Library by board — with live counts, per-card membership dots, and a one-click assignment popover. Boards travel in your library export/import.
-- 🔭 **Meet "Vee", an optional lens mascot** that reacts to your scans (scanning, wide-open on a strong fit, eyes-narrowed on a risky one, resting on an empty library). One theme-aware SVG, reduced-motion-safe; turn it off in **Options → Interface**.
+- **Meet Vee, an optional lens mascot** that reacts to your scans: scanning, wide-open on a strong fit, narrowed on a risky one, resting on an empty library. One theme-aware SVG, reduced-motion safe. Turn it off in **Options → Interface**.
 - ✨ **Subtle motion, everywhere it helps** — tactile press states, a staged tab reveal, a verdict health-bar fill, a smoother toast and modal — all respecting reduced-motion.
 - 🧭 **Errors that tell you what to do** — a failed scan now offers **Open Settings** (bad key / wrong model) or **Retry** (transient), and the loading copy names the provider it's actually using.
 
@@ -119,15 +119,15 @@ No accounts. No backend. Your keys, your machine.
 
 ## Models — your keys, your call
 
-Bring your own provider. Five are **first-class** (one-click sign-in where the vendor allows it — **Grok**, **OpenRouter**, and **OpenAI/ChatGPT** — otherwise an API key; **Claude** is API-key only) and fan out across a **smart fallback chain**: RepoLens tries them in order and drops to the next if one errors, so a single key is enough to start.
+Bring your own provider. Five are **first-class** (one-click sign-in where the vendor allows it: **Grok**, **OpenRouter**, and **OpenAI/ChatGPT**; otherwise an API key; **Claude** is API-key only) and fan out across a **smart fallback chain**: RepoLens tries them in order and drops to the next if one errors, so a single key is enough to start.
 
 **Nous** (Nous Research) **→ Gemini → OpenRouter → Grok → Anthropic**
 
-On top of those, RepoLens works with **almost any other AI service** through one registry — **OpenAI, DeepSeek, Groq, NVIDIA NIM, Kimi (Moonshot), Zhipu GLM, Qwen (Aliyun), Xiaomi MiMo, Volcengine Ark, Ollama Cloud, MiniMax, Azure OpenAI**, local **Ollama** (no key needed), and a universal **Custom** endpoint. Each keeps its **own key** (switching never loses data), has a model picker, an optional **endpoint override**, and built-in **connection / function self-tests**. Connect just one and it works — it joins the fallback chain automatically.
+On top of those, RepoLens works with **almost any other AI service** through one registry: **OpenAI, DeepSeek, Groq, NVIDIA NIM, Kimi (Moonshot), Zhipu GLM, Qwen (Aliyun), Xiaomi MiMo, Volcengine Ark, Ollama Cloud, MiniMax, Azure OpenAI**, local **Ollama** (no key needed), and a universal **Custom** endpoint. Each keeps its **own key** (switching never loses data), has a model picker, an optional **endpoint override**, and built-in **connection / function self-tests**. Connect just one and it works. It joins the fallback chain automatically.
 
-> **Sign in with ChatGPT.** The OpenAI card also offers a one-click **ChatGPT login** — the same OAuth the **Codex CLI** uses — so you can connect without pasting a key (it needs API access on your ChatGPT plan; otherwise paste a key).
+> **Sign in with ChatGPT.** The OpenAI card also offers a one-click **ChatGPT login**, the same OAuth the **Codex CLI** uses, so you can connect without pasting a key (it needs API access on your ChatGPT plan; otherwise paste a key).
 
-> Local-only? Point at **Ollama** on `localhost` — no key, no cloud. (Spawning a local *CLI* binary like `claude`/`codex` still isn't possible — a browser extension is sandboxed and can't launch a program — but it can do those CLIs' **OAuth logins**, and talk to a local HTTP model server like Ollama.)
+> Local-only? Point at **Ollama** on `localhost`. No key, no cloud. (Spawning a local *CLI* binary like `claude`/`codex` still isn't possible: a browser extension is sandboxed and can't launch a program. But it can do those CLIs' **OAuth logins**, and talk to a local HTTP model server like Ollama.)
 
 Each provider has a model dropdown (★ marks the recommended pick), and you can **route each part of a scan to a different model**:
 
@@ -139,9 +139,9 @@ Any per-part pick still falls back to the full chain if that provider errors or
 
 ## Storage — nothing to install
 
-Your whole library lives **in the browser** (IndexedDB). No database, no daemon, no setup — it works the moment you load the extension, and it's Web-Store-ready.
+Your whole library lives **in the browser** (IndexedDB). No database, no daemon, no setup. It works the moment you load the extension, and it's Web-Store-ready.
 
-Because it's *your* data, you can take it with you: **Library → Export** writes your whole library — analyzed repos, the semantic graph, and the local scan cache — to one portable JSON file, and **Import** restores it (merge or replace) on any machine. Backups are validated and bounded on import, so a bad file fails safe. Your settings travel too: **Options → Back up your settings** exports your theme, voice, model picks and per-part routing — never your API keys.
+Because it's *your* data, you can take it with you: **Library → Export** writes your whole library (analyzed repos, the semantic graph, and the local scan cache) to one portable JSON file, and **Import** restores it (merge or replace) on any machine. Backups are validated and bounded on import, so a bad file fails safe. Your settings travel too: **Options → Back up your settings** exports your theme, voice, model picks and per-part routing, but never your API keys.
 
 Migrating from an old VelesDB server? **Options → Import from VelesDB** pulls your library across in one click.
 

assets/wordmark.svg

@@ -64,6 +64,7 @@ import { buildFitsStackPrompt, parseFitsStack } from './fits-stack.js';
 import { buildStackPrompt, parseStack } from './stack-prompt.js';
 import { buildAskRepoPrompt, parseAskRepoAnswer } from './ask-repo.js';
 import { buildComparePrompt, parseCompareResult } from './compare-repos.js';
+import { startScanAnim, stopScanAnim } from './icon-anim.js';
 
 // Notify when a scan completes — clicking the notification focuses the result tab.
 chrome.notifications.onClicked.addListener(async (notifId) => {
@@ -199,7 +200,7 @@ chrome.runtime.onMessage.addListener((msg, sender, sendResponse) => {
       .set({ [msg.sessionKey]: { loading: true, status: 'fetching', ...detected } })
       .then(() => {
         sendResponse({ ok: true });
-        runAnalysis(msg.sessionKey, detected); // fire and forget; tab polls the session
+        runAnalysis(msg.sessionKey, detected, sender.tab?.id); // fire and forget; tab polls the session
       })
       .catch((err) => sendResponse({ ok: false, error: err?.message || 'Could not start the scan' }));
     return true; // keep the message channel open for the async sendResponse
@@ -555,7 +556,7 @@ chrome.action.onClicked.addListener(async (tab) => {
   // Open the output tab immediately with a loading state, then run the analysis.
   await chrome.storage.session.set({ [sessionKey]: { loading: true, status: 'fetching', ...detected } });
   await chrome.tabs.create({ url: `output-tab.html?key=${sessionKey}` });
-  runAnalysis(sessionKey, detected);
+  runAnalysis(sessionKey, detected, tab.id);
 });
 
 // Every provider credential + model-selector key, read together wherever an AI
@@ -645,14 +646,15 @@ async function runBatchScan(batchKey, urls) {
 }
 
 // Fetch → AI → parse → store. Used by the initial click and by RERUN (retry).
-async function runAnalysis(sessionKey, detected) {
+async function runAnalysis(sessionKey, detected, tabId) {
   // Load every provider credential + model + routing in one read; pass the whole
   // object to callAI so registry (compat) providers are reachable too — not just
   // the five first-class ones. Extra keys (autoSave/tone) are ignored downstream.
   const settings = await chrome.storage.local.get([...PROVIDER_KEYS, 'autoSave', 'tone']);
   const { autoSave = true, tone } = settings;
 
   try {
+    startScanAnim(tabId); // fire-and-forget; no-ops without a tabId / when disabled / reduced motion
     // Snapshot the previous cached analysis for diff comparison (before it's overwritten).
     const prevCached = await getCached(detected.platform, detected.repoId).catch(() => null);
 
@@ -749,7 +751,9 @@ async function runAnalysis(sessionKey, detected) {
       });
     } catch { /* notifications are best-effort */ }
 
+    stopScanAnim(tabId); // success: reset to the static icon
   } catch (err) {
+    stopScanAnim(tabId); // error: reset to the static icon
     // AI failures already carry a humanized message + kind; other failures (fetch,
     // parse) get classified here so the tab can still route the error CTA.
     const errorKind = err.kind || categorizeError(err).kind;

background.js

@@ -0,0 +1,11 @@
+# Writing standard
+
+RepoLens copy follows **stop-slop** (Hardik Pandya's de-slop ruleset), vendored in
+[`stop-slop/`](stop-slop/SKILL.md). It is the standard for product copy and docs:
+Vee's onboarding lines, the README, the CHANGELOG, and any future store-listing or
+website copy.
+
+The short version: cut filler openers and adverbs, write active voice with a human
+subject, name the specific thing, vary sentence rhythm, no em dashes, no emoji on
+product surfaces. Score a draft against the rubric in
+[`stop-slop/SKILL.md`](stop-slop/SKILL.md); below 35/50, revise.

docs/style/README.md

@@ -0,0 +1,68 @@
+---
+name: stop-slop
+description: Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
+metadata:
+  trigger: Writing prose, editing drafts, reviewing content for AI patterns
+  author: Hardik Pandya (https://hvpandya.com)
+---
+
+# Stop Slop
+
+Eliminate predictable AI writing patterns from prose.
+
+## Core Rules
+
+1. **Cut filler phrases.** Remove throat-clearing openers, emphasis crutches, and all adverbs. See [references/phrases.md](references/phrases.md).
+
+2. **Break formulaic structures.** Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See [references/structures.md](references/structures.md).
+
+3. **Use active voice.** Every sentence needs a human subject doing something. No passive constructions. No inanimate objects performing human actions ("the complaint becomes a fix").
+
+4. **Be specific.** No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
+
+5. **Put the reader in the room.** No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
+
+6. **Vary rhythm.** Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
+
+7. **Trust readers.** State facts directly. Skip softening, justification, hand-holding.
+
+8. **Cut quotables.** If it sounds like a pull-quote, rewrite it.
+
+## Quick Checks
+
+Before delivering prose:
+
+- Any adverbs? Kill them.
+- Any passive voice? Find the actor, make them the subject.
+- Inanimate thing doing a human verb ("the decision emerges")? Name the person.
+- Sentence starts with a Wh- word? Restructure it.
+- Any "here's what/this/that" throat-clearing? Cut to the point.
+- Any "not X, it's Y" contrasts? State Y directly.
+- Three consecutive sentences match length? Break one.
+- Paragraph ends with punchy one-liner? Vary it.
+- Em-dash anywhere? Remove it.
+- Vague declarative ("The implications are significant")? Name the specific implication.
+- Narrator-from-a-distance ("Nobody designed this")? Put the reader in the scene.
+- Meta-joiners ("The rest of this essay...")? Delete. Let the essay move.
+
+## Scoring
+
+Rate 1-10 on each dimension:
+
+| Dimension | Question |
+|-----------|----------|
+| Directness | Statements or announcements? |
+| Rhythm | Varied or metronomic? |
+| Trust | Respects reader intelligence? |
+| Authenticity | Sounds human? |
+| Density | Anything cuttable? |
+
+Below 35/50: revise.
+
+## Examples
+
+See [references/examples.md](references/examples.md) for before/after transformations.
+
+## License
+
+MIT