@damiangilgonzalez/harness 1.3.11 → 1.3.13

package/scripts/lib/versions.js

@@ -0,0 +1,31 @@
+import { readFileSync } from 'node:fs';
+import { join, dirname } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+// Which rsc is running, and which rsc this project was last built with. Two different numbers, and
+// the gap between them is where a published fix fails to arrive: hooks are materialized as copies
+// under `.rsc/`, so a release changes nothing in a project until someone syncs it. Nobody could see
+// that gap before — there was no `--version`, and bug reports arrived without one.
+
+const ROOT = join(dirname(fileURLToPath(import.meta.url)), '..', '..');
+export const CLI_VERSION = JSON.parse(readFileSync(join(ROOT, 'package.json'), 'utf8')).version;
+
+/** `.rsc/.version` is written at install and at every sync — the version this project's hooks came from. */
+export function installedVersion(root) {
+  try { return readFileSync(join(root, '.rsc', '.version'), 'utf8').trim() || null; } catch { return null; }
+}
+
+export function isNewer(a, b) {
+  const pa = String(a).split('.').map(Number);
+  const pb = String(b).split('.').map(Number);
+  for (let i = 0; i < 3; i++) {
+    if ((pa[i] || 0) > (pb[i] || 0)) return true;
+    if ((pa[i] || 0) < (pb[i] || 0)) return false;
+  }
+  return false;
+}
+
+export function versionReport(root) {
+  const installed = installedVersion(root);
+  return { cli: CLI_VERSION, installed, behind: Boolean(installed && isNewer(CLI_VERSION, installed)) };
+}

package/scripts/rsc.js

@@ -16,6 +16,7 @@ import { runUpgrade } from './lib/upgrade.js';
 import { diagnose, repair } from './lib/repair.js';
 import { DEFAULT_SKILL_FLOOR, withDefaultSkillFloor } from './lib/default-skill-floor.js';
 import { readManifest, writeManifest } from './lib/manifest-file.js';
+import { versionReport } from './lib/versions.js';
 import {
   normalizeOnboarding, missingOnboardingFields, scanProject,
   buildOnboardingPlan, decodeGoal, encodeGoal, identifyPlan, recommendDeferredComponents,
@@ -23,6 +24,20 @@ import {
 import { applyAcceptedOnboarding, verifyOnboarding, ensureHarnessSkeleton, harnessReadiness } from './lib/onboarding-apply.js';
 
 const rawArgv = process.argv.slice(2);
+
+// `rsc --version` — answered before anything else runs, offline, and in a shape a bug report can
+// paste. Two numbers because there are two things: the CLI you just ran, and the harness this
+// project was built with. When they differ the project is running old hooks, and a fix that was
+// published may simply not be here yet.
+if (['--version', '-v', 'version'].includes(rawArgv[0])) {
+  const v = versionReport(process.cwd());
+  const lines = [`rsc ${v.cli}`];
+  if (v.installed) lines.push(`installed in this project: ${v.installed}${v.behind ? ' (behind)' : ''}`);
+  else lines.push('installed in this project: none');
+  if (v.behind) lines.push('This project runs older hooks than this CLI. To catch up, run here:', '  npx @damiangilgonzalez/harness@latest');
+  process.stdout.write(`${lines.join('\n')}\n`);
+  process.exit(0);
+}
 const GLOBAL_VALUE_FLAGS = new Set([
   '--target', '--technical-level', '--accompaniment', '--project-kind', '--goal', '--goal-base64', '--software-scope', '--accept-plan',
 ]);
@@ -486,7 +501,18 @@ function printContextBudget(b) {
   say('════════════════════════════════════════════════\n');
 }
 
-async function wizard(flagTargets) {
+async function syncDeclared(targets, dry = false) {
+  for (const t of targets) {
+    const result = await syncInstalled({ target: t, dryRun: dry });
+    const verb = dry ? 'Would sync' : 'Synced';
+    say(`${verb} ${t}: ${result.synced.length ? result.synced.join(', ') : '(nothing to sync)'}`);
+    if (dry && result.paths?.length) {
+      for (const p of result.paths) say(`  ${p}`);
+    }
+  }
+}
+
+async function wizard(flagTargets, declaredTargets = []) {
   const m = loadManifest();
   await banner(m.counts.skills);
   say('  the skill catalog for your assistant (Claude Code · Codex · Cursor · Gemini · Antigravity)\n');
@@ -496,12 +522,16 @@ async function wizard(flagTargets) {
   const baseIds = skillsForProfile(m, 'minimal');
   // Navigable loop: esc / "← Back" / "no" all return here instead of quitting.
   for (;;) {
+    const declared = readManifest();
     const choice = await select('What do you want to do?', [
+      // First, because it is what someone who already has a harness came here for nine times in ten.
+      ...(declared ? [{ key: 'update', label: `Update this project — keeps its ${declared.skills.length} skills, refreshes hooks and content` }] : []),
       { key: 'base', label: `Base install — the essentials (${baseIds.length} skills)` },
       { key: 'workflow', label: 'Base + tu flujo de trabajo — grill-with-docs → to-spec → plan o tickets' },
       { key: 'manual', label: 'Pick skills by hand, by area' },
     ]);
     if (choice === null) { say('\nOK — nothing installed. Anytime: npx @damiangilgonzalez/harness'); return; }
+    if (choice === 'update') return syncDeclared(declaredTargets);
 
     let ids;
     if (choice === 'base') ids = baseIds;
@@ -560,6 +590,27 @@ async function guardCollisions(targets, ids) {
   return confirm('Replace them anyway?');
 }
 
+// The governed list that `sync` reads lives INSIDE the onboarding receipt, not in `manifest.skills`.
+// Updating one without the other is what deleted users' skills: `add` installed a skill and recorded
+// it in `manifest.skills`, `sync` then read a governed list that predated the install, and pruned
+// everything absent from it — recursively. Reported by a user, reproduced 2026-09-17: nine declared
+// skills against eight governed, visible in the manifest before sync was even run.
+//
+// So the two travel together, always. Any command that changes what is installed carries both, and
+// `applyInstall` persists the receipt rather than conserving the stale one.
+function governedBy(receipt, skills) {
+  // The receipt is hash-checked against the plan the user accepted, so its policy is NOT a place to
+  // record what happened afterwards: rewriting `plan.policy.skills` made every install report "the
+  // receipt does not match its accepted plan id", which is the integrity check doing its job.
+  //
+  // An earlier fix for the reported data loss did exactly that, and it was wrong — the right place
+  // was never `add`, it was `sync`, which treated the accepted plan as the only declaration and
+  // pruned everything absent from it. The policy still travels for hooks and agents; what must not
+  // travel is a rewritten receipt.
+  if (!receipt) return { policy: undefined, onboarding: undefined };
+  return { policy: { ...receipt.plan.policy, skills }, onboarding: undefined };
+}
+
 async function main() {
   // One resolution for every command, doctor included: `doctor` used to resolve on its
   // own and could report a different assistant than the one just installed into.
@@ -589,7 +640,16 @@ async function main() {
   const target = targets[0];
   switch (cmd) {
     case undefined:
-      return hasDeclaredHarness() ? wizard(f ? targets : null) : runOnboarding(f ? targets : []);
+      if (!hasDeclaredHarness()) return runOnboarding(f ? targets : []);
+      // A project that already has a harness: the bare command means "bring it up to date". It is
+      // what every update notice, the README and our own replies to users tell people to run, with
+      // the promise "that reinstalls and refreshes". It used to open the install wizard instead, and
+      // with no terminal — which is how an agent runs it when it obeys the notice — it did nothing.
+      // Restoring what the project already declared is not a decision, so there is nothing to ask.
+      // RSC_FORCE_WIZARD opens the wizard anyway, answering from piped stdin: that is how its
+      // choices are tested end to end, since a test has no terminal to offer.
+      if (!isInteractive() && !process.env.RSC_FORCE_WIZARD) return syncDeclared(targets);
+      return wizard(f ? targets : null, targets);
     case 'onboard':
       return runOnboarding(f ? targets : []);
     case 'reassess':
@@ -604,8 +664,8 @@ async function main() {
       const currentManifest = readManifest();
       const receipt = currentManifest?.onboarding;
       const maintainedIds = receipt ? [...new Set([...(currentManifest.skills || []), ...(receipt.plan.policy.skills || []), ...ids])].sort() : ids;
-      const policy = receipt ? { ...receipt.plan.policy, skills: maintainedIds } : undefined;
-      for (const t of targets) await applyInstall({ skillIds: maintainedIds, agentIds: selected.agents, target: t, policy });
+      const { policy, onboarding } = governedBy(receipt, maintainedIds);
+      for (const t of targets) await applyInstall({ skillIds: maintainedIds, agentIds: selected.agents, target: t, policy, onboarding });
       markMaintenanceDrift(`add ${requested.join(',')}`);
       say(`✅ Installed for ${targets.join(', ')}: ${requested.join(', ')}`);
       return void say('   ↻ Reload/restart your assistant so the new skill activates.');
@@ -727,18 +787,8 @@ async function main() {
       process.exitCode = 1;
       return;
     }
-    case 'sync': {
-      const dry = argv.includes('--dry-run');
-      for (const t of targets) {
-        const result = await syncInstalled({ target: t, dryRun: dry });
-        const verb = dry ? 'Would sync' : 'Synced';
-        say(`${verb} ${t}: ${result.synced.length ? result.synced.join(', ') : '(nothing to sync)'}`);
-        if (dry && result.paths?.length) {
-          for (const p of result.paths) say(`  ${p}`);
-        }
-      }
-      return;
-    }
+    case 'sync':
+      return syncDeclared(targets, argv.includes('--dry-run'));
     case 'backups': {
       const backups = listBackups();
       if (!backups.length) return void say('(no backups)');

package/skills/animar/SKILL.md

@@ -3,6 +3,7 @@ name: animar
 description: "Use when asked to animate something, add motion, make a component feel alive, or build a transition. Builds the animation from scratch, making the decisions in the order that determines whether it feels right — whether it should animate at all, for what purpose, with which tool, which properties, which curve and duration, how it is interrupted, and how it exits. Writes the implementation. For critiquing existing motion use revisar-animaciones."
 tags: ["animation", "motion", "transitions"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Construir animaciones

package/skills/claude-project-setup/SKILL.md

@@ -3,6 +3,7 @@ name: claude-project-setup
 description: "Use when starting a new project, initializing a repository for Claude Code, or when the user asks to configure CLAUDE.md, rules, commands, skills, or agents for a project."
 tags: ["setup", "claude-code", "project-init"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 # Claude Project Setup

package/skills/code-review/SKILL.md

@@ -3,6 +3,7 @@ name: code-review
 description: "Reviews changes from a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow the repo's documented coding standards?) and Spec (does the code match what the source issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work in progress, or asks to \\"review from X\\"."
 tags: ["code-review", "standards", "spec-compliance"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Revisión en dos ejes del diff entre `HEAD` y un punto fijo que proporciona el usuario:

package/skills/diseno-apple/SKILL.md

@@ -3,6 +3,7 @@ name: diseno-apple
 description: "Apple's approach to interface design and fluid, physical motion, translated to the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, inertia and interruptible transitions, translucent materials and depth, typography (optical size, tracking, line height), reduced motion, or the design fundamentals (feedback, spatial consistency, containment) behind Apple-style interfaces."
 tags: ["design", "apple", "motion", "interface"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Diseno Apple

package/skills/diseno-landing/SKILL.md

@@ -3,6 +3,7 @@ name: diseno-landing
 description: "Complete system for building high-conversion landing pages: intake questions, page structure, layout choice, conversion copy, SEO, plus strict visual rules for typography, spacing, radii, backgrounds, hero, icons, and motion. Use whenever building, editing, styling, reviewing, or writing copy for ANY landing page, marketing site, web UI, page section, component, or prototype, even if the user does not mention design, conversion, tokens, or a design system. Always consult it before choosing sections, headlines, CTAs, fonts, text sizes, spacing values, radii, background colors, icons, or transitions."
 tags: ["landing-page", "conversion", "design-system", "copywriting"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Diseno de landing page

package/skills/domain-modeling/SKILL.md

@@ -3,6 +3,7 @@ name: domain-modeling
 description: "Build and refine the project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to keep the domain model up to date."
 tags: ["domain-modeling", "glossary", "architecture"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 # Modelado de Dominio

package/skills/flujo-interfaz/SKILL.md

@@ -4,6 +4,7 @@ description: "Use when work touches a screen — building or reshaping a landing
 tags: ["ui-design", "routing", "workflow"]
 profiles: [ui, full]
 recommends: [ingeniero-diseno-web, diseno-landing, revision-interfaz]
+origin: damiangil
 ---
 
 # Flujo de interfaz — quien manda en cada paso

package/skills/grill-me/SKILL.md

@@ -4,6 +4,7 @@ description: "A relentless interrogation to sharpen a plan or design."
 tags: ["planning", "questioning", "decision-making"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Llama a la herramienta Skill con "grilling".

package/skills/grill-with-docs/SKILL.md

@@ -4,6 +4,7 @@ description: "A relentless interrogation to sharpen a plan or design, which also
 tags: ["planning", "questioning", "documentation", "adr"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Lanza una sesión de `/grilling`, usando la skill `/domain-modeling`.

package/skills/grilling/SKILL.md

@@ -3,6 +3,7 @@ name: grilling
 description: "Interrogates the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their reasoning, or when they use any trigger phrase like \\"grill\\" / \\"interrogate me\\" / \\"put me to the test\\"."
 tags: ["planning", "questioning", "decision-making"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Interroga al usuario sin tregua hasta llegar a un entendimiento compartido. Represéntalo como un **árbol de decisión**: cada decisión se ramifica en las decisiones que cuelgan de ella.

package/skills/handoff/SKILL.md

@@ -3,6 +3,7 @@ name: handoff
 description: "Compacts the current conversation into a handoff document so another agent can continue the work."
 tags: ["handoff", "documentation", "continuity"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Redacta un documento de traspaso que resuma la conversación actual para que un agente nuevo pueda continuar con el trabajo. 

package/skills/implement/SKILL.md

@@ -4,6 +4,7 @@ description: "Implements a piece of work from a spec or a set of tickets."
 tags: ["implementation", "spec", "tickets"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 

package/skills/ingeniero-diseno-web/SKILL.md

@@ -3,6 +3,7 @@ name: ingeniero-diseno-web
 description: "Build or redesign polished visual artifacts that render in a browser with HTML/CSS/JavaScript/React — pages, dashboards, prototypes, presentations, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser-based acceptance/QA. Not for back-end, CLI, non-visual code, or converting sources into long-form articles."
 tags: ["frontend", "web-design", "prototyping", "qa"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Ingeniero de diseno web

package/skills/leyes-de-percepcion/SKILL.md

@@ -3,6 +3,7 @@ name: leyes-de-percepcion
 description: "Use when composing or reviewing a screen and you need to decide what the eye sees first and how things are grouped — proximity, similarity, common region, closure, continuity, figure-ground, the Von Restorff effect, and visual hierarchy. This is the package of Gestalt laws applied to interface design."
 tags: ["gestalt", "visual-perception", "ui-design"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Leyes de percepcion

package/skills/leyes-de-retencion/SKILL.md

@@ -3,6 +3,7 @@ name: leyes-de-retencion
 description: "Use when diagnosing why people abandon a flow halfway through, or when designing decisions, forms, steps, response times, and closing moments — Hick's law, Fitts's law, Miller's law, Jakob's law, the Doherty threshold, the Zeigarnik effect, the serial position effect, the peak-end rule, and Tesler's law."
 tags: ["retention", "ux-laws", "behavioral-design"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Leyes de retencion

package/skills/mejor-accesibilidad/SKILL.md

@@ -3,6 +3,7 @@ name: mejor-accesibilidad
 description: "Use to bring the project up to accessibility standards and best practices — native elements vs. ARIA, focus rings, full keyboard support, focus trapping, tap target sizes, form labels, announced errors, accessible names, reduced motion, live regions, alt text, heading structure, and zoom."
 tags: ["accessibility", "a11y", "aria", "keyboard-navigation"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Accesibilidad

package/skills/mejor-colores/SKILL.md

@@ -3,6 +3,7 @@ name: mejor-colores
 description: "Use to build a color system or answer anything about color in the project — generating palettes, using semantic tokens, converting between formats, measuring contrast, choosing a gradient's interpolation space, and setting up dark mode."
 tags: ["color", "design-tokens", "contrast", "dark-mode"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Colores

package/skills/mejor-layout/SKILL.md

@@ -3,6 +3,7 @@ name: mejor-layout
 description: "Use when building or reviewing a screen's layout — grouping, alignment, reading order, progressive disclosure, spacing, breakpoints, translated-text growth, and RTL."
 tags: ["layout", "responsive-design", "ui-design"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Layout

package/skills/mejor-redaccion/SKILL.md

@@ -3,6 +3,7 @@ name: mejor-redaccion
 description: "Use when writing or reviewing a product's copy — voice and tone, button labels, a flow's vocabulary, link text, capitalization, settings, error messages, empty states, and placeholders."
 tags: ["ux-writing", "microcopy", "content-design"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Redaccion de interfaz

package/skills/mejor-tipografia/SKILL.md

@@ -3,6 +3,7 @@ name: mejor-tipografia
 description: "Use when building or reviewing typography — size scale, spacing, line height, variable fonts, OpenType features, wrapping, truncation, tabular numbers, punctuation, and all the details that make text read well across a product."
 tags: ["typography", "design-system", "readability"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Tipografia

package/skills/mejor-ui/SKILL.md

@@ -3,6 +3,7 @@ name: mejor-ui
 description: "Use to polish and improve a project's UI — concentric border radii, optical alignment, surface depth, shadows vs. borders, interruptible animations, staggered entrances, icon transitions, press scaling, theme-switch transition suppression, and motion containment."
 tags: ["ui-polish", "visual-design", "motion"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Acabado de UI

package/skills/muscle-memory/SKILL.md

@@ -3,6 +3,7 @@ name: muscle-memory
 description: "Python practice gym — generates short katas from the user's recent code, tracks progress, and reviews solutions. Use when the user wants to practice/keep their coding sharp, review a kata solution, or check practice progress."
 tags: ["practice", "python", "katas"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 # Muscle Memory

package/skills/prototype/SKILL.md

@@ -3,6 +3,7 @@ name: prototype
 description: "Builds a throwaway prototype to answer a design question. Use when the user wants to check whether a state model or logic \\"feels right\\", or explore what a UI should look like."
 tags: ["prototyping", "design", "exploration"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 # Prototipo

package/skills/research/SKILL.md

@@ -3,6 +3,7 @@ name: research
 description: "Researches a question against high-confidence primary sources and captures the findings as a Markdown file in the repo. Use when the person wants to research a topic, gather facts from documentation or an API, or delegate the reading work to a background agent."
 tags: ["research", "documentation", "background-agent"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Levanta un **agente en segundo plano** para hacer la investigación, así sigues trabajando mientras él lee.

package/skills/revision-de-cambios/SKILL.md

@@ -4,6 +4,7 @@ description: "Reviews a CHANGE (uncommitted work, a branch, a commit range, or a
 tags: ["code-review", "diff-review", "regression"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 # Revision de cambios

package/skills/revision-interfaz/SKILL.md

@@ -3,6 +3,7 @@ name: revision-interfaz
 description: "Combines all the `mejor-*` skills into a single interface review covering accessibility, layout, copy, typography, color, and visual polish, and consolidates a verdict ordered by impact."
 tags: ["ui-review", "accessibility", "design-audit"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Revision de interfaz

package/skills/sitios-calidad-premio/SKILL.md

@@ -3,6 +3,7 @@ name: sitios-calidad-premio
 description: "Art-direct and implement marketing, editorial, portfolio, and landing sites that are distinctive and motion-rich, with original imagery inspired by references, standout heroes, GSAP choreography, a single smooth-scroll engine, optional Three.js shaders, honest icon and logo sourcing, photographic avatars, accessibility, and performance safeguards. Use when asked for an award-quality, premium, cinematic, interactive, high-concept, or motion-driven website."
 tags: ["award-site", "gsap", "webgl", "art-direction"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Construir sitios de calidad de premio

package/skills/suggest/SKILL.md

@@ -25,9 +25,8 @@ owns it; this is the pointer, not the manual.
 The moment someone wants something to **exist or behave differently** — build, add, change,
 integrate, "it should also…", "¿y si…?", in any language — the request earns a clear *what* and
 the user's go-ahead before any line of code lands. No skill outranks this, stack and builder
-skills included (`nextjs`, `react`, `fastapi`, `flutter`, `go`, `postgresdb`, `building-agents`,
-`design`, `chatbot`, `course-builder`, `marketing`…): they run **inside** the chain, once the plan
-is approved — matching strongly is not a reason to skip ahead.
+skills included (`nextjs`, `fastapi`, `flutter`, `building-agents`, `design`, `marketing`…): they
+run **inside** the chain, once the plan is approved — matching strongly is not a reason to skip ahead.
 
 The shape of the chain:
 
@@ -47,8 +46,8 @@ Two exceptions, and say out loud when you take one:
 
 When you cannot tell, take the clarifying step. A skipped one is where drift hides.
 
-Judge the **meaning**, not the wording: the trigger is semantic, so it holds in any language,
-including ones with no example here. A URL plus a description of desired behaviour is a feature
+Judge the **meaning**, not the wording: the trigger is semantic, so it holds in any language.
+A URL plus a description of desired behaviour is a feature
 request. If the user already engaged an autopilot over this chain, that one consent covers the
 whole run — advance through the phases without re-asking.
 
@@ -73,7 +72,7 @@ name it and offer it. This runs mid-conversation, not only at project start.
    `id  available  short description`.
 2. Pick the single best fit **by meaning**, the way you would match a request to a teammate's
    expertise — "mandar emails de bienvenida" → an email/outreach skill, though not one keyword
-   overlaps; "login con Google" → an auth skill, not `flutter`. If nothing genuinely fits, say so
+   overlaps. If nothing genuinely fits, say so
    and move on: a tangential suggestion is worse than none.
 3. Ask once, plainly: "Para esto instalaría `<id>`, que aún no tienes. ¿La instalo? (sí/no)".
 4. On yes, run `npx @damiangilgonzalez/harness add <id>`, then continue the original task.
@@ -100,7 +99,6 @@ You are injected into every session, so you are the only thing that can notice a
 harness before its owner does — and its owner usually cannot, because the symptoms name
 nothing they recognise. When any of these is true, act on it **once** in the session:
 
-- the assistant sees no skills in a project that clearly has a harness;
 - `.rsc.json` exists and what it declares is not what is installed;
 - the same hook seems to run several times;
 - the harness is wired for an assistant that is not the one running.
@@ -108,6 +106,10 @@ nothing they recognise. When any of these is true, act on it **once** in the ses
 Run `npx @damiangilgonzalez/harness doctor`, and say in one line what is wrong **as a symptom**, not as
 a cause. Then:
 
+- **Nothing built** — `.rsc.json` without `.rsc/`: a clone. Name
+  `npx @damiangilgonzalez/harness@<catalogVersion in .rsc.json> sync`, that exact version, **never** `@latest`
+  — a release nobody here adopted is drift. Ask in one line, **keep working either way**; silence
+  is not a no, `.rsc/.no-harness` is.
 - Anything that only puts the harness back to what was already declared — dangling links, a
   repeated hook, a layout no version uses — say you are fixing it and run
   `npx @damiangilgonzalez/harness repair`. Restoring is not deciding, and a recoverable copy is kept.
@@ -115,8 +117,7 @@ a cause. Then:
   teammate added, disarming a gate — **ask first**. A `git pull` never rewrites someone's
   machine.
 
-Offer once. A "no" holds for the session; a new session may look again, because the problem
-has not gone away. Never mention it when the harness is healthy.
+Offer once per session. Never mention any of it when the harness is healthy.
 
 ## 4. First contact
 

package/skills/tastemaker/SKILL.md

@@ -3,6 +3,7 @@ name: tastemaker
 description: "Generates genuinely beautiful, on-brand UI instead of generic AI slop. Use whenever asked to build, design, style, or improve a UI, landing page, dashboard, app screen, or component; when a PRD needs a design pass before implementation; when the user pastes reference images or links and wants the app to look like them; or when they complain the generated UI looks generic, boring, templated, or like every other AI app. Also triggers without the word \\"design\\", with phrases like \\"make this look good\\", \\"build me the frontend for X\\", \\"this looks like just another SaaS site\\", or \\"pick up the look of this\\". Also with the verbs study or extract the look from a screenshot or URL, and audit or review why something looks AI-made."
 tags: ["ui-design", "branding", "visual-design"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Tastemaker

package/skills/teach/SKILL.md

@@ -4,6 +4,7 @@ description: "Teaches the user a new skill or concept within this workspace. Use
 tags: ["teaching", "learning", "mentoring"]
 disable-model-invocation: true
 profiles: [minimal, core, ui, full]
+origin: damiangil
 ---
 
 El usuario te ha pedido que le enseñes algo. Es una petición con estado: pretende aprender el tema a lo largo de varias sesiones.

package/skills/to-questionnaire/SKILL.md

@@ -4,6 +4,7 @@ description: "Turns a decision you cannot answer alone into a questionnaire for
 tags: ["planning", "questionnaire", "decision-making"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Convierte algo que el usuario no puede responder solo en un **cuestionario**: un documento Markdown que entrega a una persona para rellenarlo de forma asíncrona, o para completarlo juntos en una reunión. El destinatario tiene un conocimiento que al usuario le falta; el cuestionario se lo extrae.

package/skills/to-spec/SKILL.md

@@ -4,6 +4,7 @@ description: "Turns the current conversation into a spec (PRD) and publishes it
 tags: ["spec", "prd", "issue-tracker"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 

package/skills/to-tickets/SKILL.md

@@ -4,6 +4,7 @@ description: "Breaks down a plan, a spec, or the current conversation into a set
 tags: ["tickets", "planning", "issue-tracker"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 

package/skills/video-a-superprompt/SKILL.md

@@ -3,6 +3,7 @@ name: video-a-superprompt
 description: "Turns a reference video into a highly detailed recreation or inspiration prompt. Use when the user provides, mentions, uploads, links, or points to a video and asks to analyze the design, UI, animations, transitions, scroll interactions, typography, colors, assets, WebGL/Three.js, narrative, or section-by-section behavior, or to create a prompt or article that recreates the page, app, interaction, or motion system."
 tags: ["video-analysis", "prompt-engineering", "design"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # De video a superprompt

package/skills/vocabulario-animacion/SKILL.md

@@ -3,6 +3,7 @@ name: vocabulario-animacion
 description: "Use when someone describes a web motion effect without knowing its name (\\"that bouncy thing when a popover opens\\", \\"the iOS rubber-band scroll\\") and asks \\"what's it called when...\\". Returns the exact term so it can be requested from an AI or a designer. This is for NAMING an effect, not designing or building one."
 tags: ["animation", "vocabulary", "reference"]
 profiles: [ui, full]
+origin: damiangil
 ---
 
 # Vocabulario de animacion

package/skills/wait-what/SKILL.md

@@ -4,6 +4,7 @@ description: "Stop. That last message didn't land: rephrase it."
 tags: ["clarification", "communication"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Espera, no entiendo a dónde has llegado con esto. Vuelve a plantearlo: dame algo de contexto, habla en Inglés Técnico Simplificado ASD-STE100 (aplícalo igual en español: frases cortas, una idea por frase, vocabulario consistente), y usa el lenguaje ubicuo de `CONTEXT.md` (sigue `CONTEXT-MAP.md` hasta el correcto si el repo tiene más de uno).

package/skills/wayfinder/SKILL.md

@@ -4,6 +4,7 @@ description: "Plans a huge chunk of work — more than fits in a single agent se
 tags: ["planning", "issue-tracker", "large-scale-work"]
 disable-model-invocation: true
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Ha llegado una idea difusa — demasiado grande para una sola sesión de agente, y envuelta en niebla: todavía no se ve el camino de aquí al **destino**. El wayfinding trata de encontrar ese camino, no de embestir contra el destino. Esta skill traza el camino como un **mapa compartido** en el issue tracker del repo, y luego trabaja sus **tickets de decisión** — preguntas cuya resolución es una decisión, no porciones de una construcción a ejecutar — de uno en uno hasta que la ruta está clara.

package/skills/write-adr/SKILL.md

@@ -3,6 +3,7 @@ name: write-adr
 description: "Use when you need to record an architecture decision, open an ADR, amend or replace an existing one, or when a change is hard to revert and someone will ask in six months why it's done this way (structural refactor, major dependency, API contract, data partitioning, module boundaries)."
 tags: ["adr", "architecture", "documentation"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 # Write an ADR

package/skills/writing-for-agents/SKILL.md

@@ -3,6 +3,7 @@ name: writing-for-agents
 description: "Write documents that an agent will consume. Use when creating or editing skills, or when modifying AGENTS.md or CLAUDE.md."
 tags: ["writing", "documentation", "agents"]
 profiles: [core, ui, full]
+origin: damiangil
 ---
 
 Referencia para escribir cualquier documento que consume un agente: una skill, un `AGENTS.md` / `CLAUDE.md`, un documento al que se llega por un puntero. El empaquetado cambia; la escritura no: las mismas palancas hacen predecible cada uno, porque el agente sigue el mismo *proceso* en cada ejecución en lugar de producir el mismo resultado.

package/targets/_md-block.js

@@ -1,6 +1,7 @@
 import { readFileSync, writeFileSync, existsSync, mkdirSync } from 'node:fs';
 import { dirname } from 'node:path';
 import { linkOrCopy } from './index.js';
+import { ensureShadowClaudeMd } from './agents-md-shadow.js';
 
 // Shared adapter for every assistant whose "always-on" surface is a plain
 // markdown instructions/rules file (AGENTS.md, copilot-instructions.md, a
@@ -33,7 +34,13 @@ export function wireHook(paths, sourceMd, policy = {}) {
   }
   mkdirSync(dirname(paths.hookTarget), { recursive: true });
   writeFileSync(paths.hookTarget, doc);
-  return [paths.hookTarget];
+
+  // This file may BE the root AGENTS.md, which Claude Code 2.1.277+ reads as project instructions
+  // when no CLAUDE.md exists — doubling an always-on body the SessionStart hook already prints.
+  // No-op unless the Claude Code target is also wired here. Called from both adapters so the fix
+  // holds whichever assistant the user installs second. See targets/agents-md-shadow.js.
+  const shadow = ensureShadowClaudeMd(paths.projectRoot);
+  return shadow ? [paths.hookTarget, shadow] : [paths.hookTarget];
 }
 
 // Inverse of wireHook: remove the marked rsc-suggest block from the shared