infinity-harness 2.0.0 → 2.0.2

package/src/core/skills.ts

@@ -0,0 +1,386 @@
+/**
+ * infinity-harness — the craft skills that ship with the package.
+ *
+ * 29 short documents on how to do the work well: how to write a test worth
+ * keeping, how to debug something intermittent, how to design a module
+ * boundary. pi loads them as skills so the model can invoke any of them by
+ * name — but a model with 29 skills available and no idea which one applies
+ * reads none of them.
+ *
+ * So the brief names the one or two that match what is being worked on right
+ * now. That matching is what this module does. Each skill declares the phases
+ * it belongs to and the vocabulary it covers:
+ *
+ *     ---
+ *     name: concurrency-async
+ *     description: Concurrency and async correctness — races, idempotency, …
+ *     tags: [concurrency, async, race, lock, mutex, deadlock, atomic]
+ *     when: task involves parallel work, background jobs, or shared state
+ *     phases: [plan, build, verify]
+ *     ---
+ *
+ * and a task called "serialise plan writes so two workers can't clobber each
+ * other" hits `lock` and `race` in BUILD, so the brief says to read it.
+ *
+ * The skills live in the package, not the user's project: they travel with the
+ * install, and no project needs to vendor them.
+ */
+
+import { readFileSync, readdirSync, statSync, existsSync } from "node:fs";
+import { basename, dirname, join, resolve } from "node:path";
+import { fileURLToPath } from "node:url";
+import { PHASE_ORDER, type Phase } from "./types.ts";
+
+/**
+ * What a skill is for, which decides how it earns a place in a brief.
+ *
+ *   - `process` — how to work in a phase. Belonging to the phase is enough:
+ *     TDD is the right answer for a BUILD task whatever the task says.
+ *   - `domain` — a subject area. Must share vocabulary with the task; nobody
+ *     needs the database skill because they happen to be in BUILD.
+ *   - `meta` — growing the toolkit. Vocabulary only, never a phase.
+ */
+export type SkillKind = "process" | "domain" | "meta";
+
+export type SkillMeta = {
+  /** As pi knows it — `/skill:<name>`. */
+  name: string;
+  description: string;
+  kind: SkillKind;
+  /** Vocabulary that should pull this skill in. */
+  tags: string[];
+  /** Phases it belongs to. Empty means "any phase" — the meta skills. */
+  phases: string[];
+  /** Prose condition from the header, shown when nothing better is available. */
+  when: string;
+  file: string;
+};
+
+export type SkillMatch = {
+  skill: SkillMeta;
+  score: number;
+  /** Why it surfaced, in words: `build phase · matches "lock", "race"`. */
+  why: string;
+};
+
+/**
+ * Where the shipped skills live.
+ *
+ * Resolved from this module's own location, so it is right in a checkout
+ * (`<repo>/src/core` → `<repo>/harness/skills`) and right inside an install
+ * (`node_modules/infinity-harness/src/core` → `…/harness/skills`).
+ *
+ * pi loads extensions through jiti, which provides `import.meta.url` but not
+ * `import.meta.dirname` — hence the long way round.
+ */
+export function packagedSkillsDir(): string {
+  try {
+    return resolve(dirname(fileURLToPath(import.meta.url)), "..", "..", "harness", "skills");
+  } catch {
+    return "";
+  }
+}
+
+/**
+ * pi's discovery rules, reproduced:
+ *   - a directory containing `SKILL.md` is a skill root; that file is the
+ *     skill and nothing below it is scanned
+ *   - otherwise direct `.md` children of the root are skills
+ *   - subdirectories are recursed into, but only to find `SKILL.md`
+ *   - dotfiles and `node_modules` are skipped
+ */
+export function discoverSkillFiles(dir: string, includeRootFiles = true): string[] {
+  let entries: string[];
+  try {
+    entries = readdirSync(dir);
+  } catch {
+    return [];
+  }
+
+  if (entries.includes("SKILL.md") && isFile(join(dir, "SKILL.md"))) {
+    return [join(dir, "SKILL.md")];
+  }
+
+  const found: string[] = [];
+  for (const entry of entries.sort()) {
+    if (entry.startsWith(".") || entry === "node_modules") continue;
+    const full = join(dir, entry);
+    if (isDir(full)) {
+      found.push(...discoverSkillFiles(full, false));
+      continue;
+    }
+    if (!includeRootFiles || !entry.endsWith(".md") || !isFile(full)) continue;
+    found.push(full);
+  }
+  return found;
+}
+
+function isDir(path: string): boolean {
+  try {
+    return statSync(path).isDirectory();
+  } catch {
+    return false;
+  }
+}
+
+function isFile(path: string): boolean {
+  try {
+    return statSync(path).isFile();
+  } catch {
+    return false;
+  }
+}
+
+// ── Frontmatter ─────────────────────────────────────────────────────────────
+
+export type Frontmatter =
+  | {
+      kind: "ok";
+      /** Plain single-line values. */
+      scalars: Map<string, string>;
+      /** Flow lists: `tags: [a, b]`. */
+      lists: Map<string, string[]>;
+      /** Keys whose value is a map, a block scalar, or otherwise not plain. */
+      structured: Set<string>;
+    }
+  | { kind: "error"; message: string };
+
+const SCALAR_KEYS = new Set(["name", "description", "when", "kind"]);
+const LIST_KEYS = new Set(["tags", "phases"]);
+
+/**
+ * Read a skill header without a YAML dependency.
+ *
+ * pi uses a real YAML parser; this reads the subset a skill header is allowed
+ * to use, and records anything else as `structured` rather than guessing at
+ * it. The audit turns that into a failure, so the two readers can never
+ * silently disagree about what a skill is called or what it does.
+ *
+ * The `startsWith("---")` test is pi's, and it is why a UTF-8 BOM hides an
+ * entire header: three invisible bytes and the file has no frontmatter at all.
+ */
+export function parseSkillFrontmatter(raw: string): Frontmatter {
+  const text = raw.replace(/\r\n/g, "\n").replace(/\r/g, "\n");
+  if (!text.startsWith("---")) {
+    return {
+      kind: "error",
+      message: "no frontmatter block (pi requires `---` on the very first line)",
+    };
+  }
+  const end = text.indexOf("\n---", 3);
+  if (end === -1) {
+    return { kind: "error", message: "frontmatter block is never closed with `---`" };
+  }
+
+  const scalars = new Map<string, string>();
+  const lists = new Map<string, string[]>();
+  const structured = new Set<string>();
+
+  for (const line of text.slice(4, end).split("\n")) {
+    if (!line.trim() || line.startsWith("#")) continue;
+    // An indented line belongs to whatever structured value came before it.
+    if (/^\s/.test(line)) continue;
+    const match = /^([A-Za-z0-9_-]+)\s*:\s*(.*)$/.exec(line);
+    if (!match) continue;
+    const key = match[1]!;
+    const value = match[2]!.trim();
+
+    if (LIST_KEYS.has(key)) {
+      if (value.startsWith("[") && value.endsWith("]")) {
+        lists.set(key, splitFlowList(value.slice(1, -1)));
+      } else if (value === "") {
+        // A block list (`tags:` then `  - a`) is legal YAML but not the house
+        // style; record it as structured rather than reading half of it.
+        structured.add(key);
+      } else {
+        lists.set(key, splitFlowList(value));
+      }
+      continue;
+    }
+
+    if (!SCALAR_KEYS.has(key)) continue;
+
+    if (value === "" || value === "|" || value === ">" || value.startsWith("[") || value.startsWith("{")) {
+      structured.add(key);
+      continue;
+    }
+    scalars.set(key, unquote(value));
+  }
+
+  return { kind: "ok", scalars, lists, structured };
+}
+
+function splitFlowList(inner: string): string[] {
+  return inner
+    .split(",")
+    .map((s) => unquote(s.trim()))
+    .filter((s) => s.length > 0);
+}
+
+function unquote(value: string): string {
+  if (value.length >= 2) {
+    const first = value[0];
+    const last = value[value.length - 1];
+    if ((first === '"' && last === '"') || (first === "'" && last === "'")) {
+      return value.slice(1, -1);
+    }
+  }
+  // A YAML plain scalar ends at an unquoted ` #`.
+  const comment = value.indexOf(" #");
+  return (comment === -1 ? value : value.slice(0, comment)).trim();
+}
+
+// ── Loading ─────────────────────────────────────────────────────────────────
+
+/**
+ * Load every skill in a directory. Malformed files are skipped rather than
+ * thrown on — a broken skill must never stop a brief from being issued. The
+ * audit (`skillsAudit.ts`) is what refuses to let one ship.
+ *
+ * Deliberately uncached: 29 small files read once per brief costs nothing, and
+ * a cache would serve a stale header to anyone editing a skill mid-run.
+ */
+export function loadSkills(dir: string = packagedSkillsDir()): SkillMeta[] {
+  if (!dir || !existsSync(dir)) return [];
+  const out: SkillMeta[] = [];
+  for (const file of discoverSkillFiles(dir)) {
+    let raw: string;
+    try {
+      raw = readFileSync(file, "utf-8");
+    } catch {
+      continue;
+    }
+    const parsed = parseSkillFrontmatter(raw);
+    if (parsed.kind !== "ok") continue;
+    const description = parsed.scalars.get("description") ?? "";
+    if (!description.trim()) continue;
+    const stem = basename(file).replace(/\.md$/, "");
+    const name = parsed.scalars.get("name") || (stem === "SKILL" ? basename(dirname(file)) : stem);
+    const kind = parsed.scalars.get("kind");
+    out.push({
+      name,
+      description,
+      kind: kind === "process" || kind === "domain" || kind === "meta" ? kind : "domain",
+      tags: parsed.lists.get("tags") ?? [],
+      phases: parsed.lists.get("phases") ?? [],
+      when: parsed.scalars.get("when") ?? "",
+      file,
+    });
+  }
+  return out;
+}
+
+// ── Matching ────────────────────────────────────────────────────────────────
+
+const PHASE_WEIGHT = 4;
+const TAG_WEIGHT = 2;
+const NAME_WEIGHT = 3;
+/** Three tag hits already means "yes, this one"; more shouldn't drown a phase. */
+const MAX_TAG_HITS = 3;
+/**
+ * A single incidental tag hit is not a recommendation. "package-lock.json"
+ * contains `json`, which is on the HTTP skill's tag list, and nobody resolving
+ * a merge conflict needs to read about REST.
+ */
+const MIN_SCORE = 3;
+
+export type MatchOptions = {
+  phase?: Phase | null;
+  /** Everything known about the current work: task, feature, goal, criteria. */
+  text?: string;
+  limit?: number;
+};
+
+/**
+ * Rank skills against the work in hand.
+ *
+ * A skill earns its place by belonging to this phase, by sharing vocabulary
+ * with the task, or both — but only `process` skills can qualify on the phase
+ * alone. That distinction is the whole difference between a useful section and
+ * a section people learn to skip: without it, every BUILD task in the world
+ * gets told to read about authentication, because `auth-security` lists BUILD
+ * among its phases and sorts early in the alphabet.
+ *
+ * Where a phase appears in a skill's list matters too. `diagnosing-bugs`
+ * declares `[verify, build]` — it is a VERIFY skill that is also useful in
+ * BUILD — so it should not outrank `tdd`, which leads with BUILD, on a BUILD
+ * task that says nothing about bugs.
+ *
+ * Skills that score nothing are left out entirely. An empty section is honest;
+ * a padded one is noise.
+ */
+export function matchSkills(skills: SkillMeta[], options: MatchOptions = {}): SkillMatch[] {
+  const { phase = null, text = "", limit = 3 } = options;
+  const haystack = text.toLowerCase();
+  const tokens = new Set(haystack.split(/[^a-z0-9]+/).filter(Boolean));
+
+  const matches: SkillMatch[] = [];
+  for (const skill of skills) {
+    let score = 0;
+    const reasons: string[] = [];
+
+    const hits: string[] = [];
+    for (const tag of skill.tags) {
+      const t = tag.toLowerCase();
+      // Hyphenated tags don't survive tokenisation, so look for them whole.
+      // Everything else matches its own plural: a task about "two workers"
+      // is about the `worker` tag, and pretending otherwise loses the match
+      // that mattered.
+      const hit = t.includes("-") ? haystack.includes(t) : hasWord(tokens, t);
+      if (hit && !hits.includes(t)) hits.push(t);
+    }
+
+    const position = phase ? skill.phases.indexOf(phase) : -1;
+    const phaseCounts = position >= 0 && (skill.kind === "process" || hits.length > 0);
+    if (phaseCounts) {
+      score += Math.max(1, PHASE_WEIGHT - position);
+      reasons.push(`${phase} phase`);
+    }
+
+    if (hits.length && skill.kind !== "meta") {
+      score += TAG_WEIGHT * Math.min(hits.length, MAX_TAG_HITS);
+    } else if (hits.length) {
+      // A meta skill has to be asked for: `meta` is on all of their tag lists,
+      // so counting it like any other hit would surface all four constantly.
+      const real = hits.filter((h) => h !== "meta");
+      if (real.length === 0) continue;
+      score += TAG_WEIGHT * Math.min(real.length, MAX_TAG_HITS);
+    }
+    if (hits.length) {
+      const shown = hits.filter((h) => h !== "meta" || skill.kind !== "meta").slice(0, MAX_TAG_HITS);
+      if (shown.length) reasons.push(`matches ${shown.map((h) => `"${h}"`).join(", ")}`);
+    }
+
+    // Naming the skill in the task means it, and outranks any guess.
+    if (skill.name && haystack.includes(skill.name.toLowerCase())) {
+      score += NAME_WEIGHT;
+    }
+
+    if (score < MIN_SCORE) continue;
+    matches.push({ skill, score, why: reasons.join(" · ") });
+  }
+
+  // Ties break by phase specificity then name, so the same state always
+  // produces the same brief — one that reshuffles between turns reads as new
+  // information when nothing has changed.
+  matches.sort(
+    (a, b) =>
+      b.score - a.score ||
+      a.skill.phases.length - b.skill.phases.length ||
+      a.skill.name.localeCompare(b.skill.name),
+  );
+  return matches.slice(0, Math.max(0, limit));
+}
+
+/** Token match, tolerant of a trailing plural on either side. */
+function hasWord(tokens: Set<string>, tag: string): boolean {
+  if (tokens.has(tag)) return true;
+  if (tokens.has(`${tag}s`)) return true;
+  return tag.endsWith("s") && tokens.has(tag.slice(0, -1));
+}
+
+/** Every kind a skill header may legally declare. */
+export const SKILL_KINDS: readonly string[] = ["process", "domain", "meta"];
+
+/** Every phase name a skill header may legally declare. */
+export const KNOWN_PHASES: readonly string[] = PHASE_ORDER;

package/src/core/skillsAudit.ts

@@ -0,0 +1,223 @@
+/**
+ * infinity-harness — skill file audit.
+ *
+ * pi loads **every** `.md` file in a declared skills directory as a skill and
+ * validates it. A file that fails validation is not quietly ignored: pi prints
+ * a `[Skill conflicts]` block on every single start, naming the file and the
+ * problem. A stray `README.md` beside the skills is enough to do it — that is
+ * exactly how this module came to exist.
+ *
+ * The point is to turn a warning the user sees at runtime into a failure we
+ * see at test time. This re-implements pi's validation rules (`core/skills.js`
+ * in the agent) closely enough that a clean audit means a clean start, over
+ * the discovery and header parsing in `skills.ts`.
+ *
+ * Two deliberate differences, both in the stricter direction — this must never
+ * pass something pi would reject:
+ *
+ *   - pi honours `.gitignore` / `.ignore` / `.fdignore` inside the skills tree
+ *     and skips what they exclude. We audit everything we find.
+ *   - pi parses frontmatter with a real YAML parser. We accept only plain
+ *     scalars and flow lists, and report anything else rather than guessing.
+ *     Frontmatter clever enough to need a YAML parser is frontmatter nobody
+ *     should be writing in a skill header.
+ */
+
+import { readFileSync } from "node:fs";
+import { basename, dirname } from "node:path";
+import { KNOWN_PHASES, SKILL_KINDS, discoverSkillFiles, parseSkillFrontmatter } from "./skills.ts";
+
+/** pi: MAX_NAME_LENGTH. */
+export const MAX_NAME_LENGTH = 64;
+/** pi: MAX_DESCRIPTION_LENGTH. */
+export const MAX_DESCRIPTION_LENGTH = 1024;
+/** pi: validateName. */
+export const NAME_RE = /^[a-z0-9-]+$/;
+
+export type SkillProblem = {
+  /** Absolute path of the offending file. */
+  file: string;
+  /** Phrased the way pi phrases it, where pi has a phrasing. */
+  message: string;
+};
+
+export type SkillEntry = {
+  file: string;
+  name: string;
+  description: string;
+};
+
+export type SkillAudit = {
+  /** Files that would load as skills. */
+  skills: SkillEntry[];
+  /** Everything wrong, in discovery order. */
+  problems: SkillProblem[];
+};
+
+/**
+ * Walk a skills directory the way pi does and report what it would say.
+ *
+ * A missing directory is not a problem — pi treats it as "no skills here", and
+ * so do we; a package may legitimately declare a directory it does not ship.
+ */
+export function auditSkillsDir(dir: string): SkillAudit {
+  const audit: SkillAudit = { skills: [], problems: [] };
+
+  for (const file of discoverSkillFiles(dir)) {
+    inspect(file, audit);
+  }
+
+  // pi keys skills by name, so two files claiming one name means one of them
+  // simply does not exist — and nothing warns about that, which makes it worse
+  // than the errors that do.
+  const byName = new Map<string, string[]>();
+  for (const skill of audit.skills) {
+    const seen = byName.get(skill.name);
+    if (seen) seen.push(skill.file);
+    else byName.set(skill.name, [skill.file]);
+  }
+  for (const [name, files] of byName) {
+    if (files.length < 2) continue;
+    for (const file of files.slice(1)) {
+      audit.problems.push({
+        file,
+        message: `duplicate skill name "${name}" (also declared by ${files[0]})`,
+      });
+    }
+  }
+
+  return audit;
+}
+
+/** Validate one file, appending to the audit. */
+function inspect(file: string, audit: SkillAudit): void {
+  let raw: string;
+  try {
+    raw = readFileSync(file, "utf-8");
+  } catch (e) {
+    audit.problems.push({ file, message: e instanceof Error ? e.message : "unreadable" });
+    return;
+  }
+
+  // pi tests `content.startsWith("---")` against the raw string, so a UTF-8
+  // BOM hides the frontmatter completely and the file reads as a skill with no
+  // description at all — a confusing way to learn your editor added three
+  // invisible bytes.
+  if (raw.charCodeAt(0) === 0xfeff) {
+    audit.problems.push({
+      file,
+      message: "starts with a UTF-8 BOM, which hides the frontmatter from pi",
+    });
+    return;
+  }
+
+  const parsed = parseSkillFrontmatter(raw);
+  if (parsed.kind === "error") {
+    audit.problems.push({ file, message: parsed.message });
+    return;
+  }
+
+  for (const key of ["name", "description"]) {
+    if (parsed.structured.has(key)) {
+      audit.problems.push({ file, message: `\`${key}\` must be a plain single-line value` });
+    }
+  }
+  if (parsed.structured.has("name") || parsed.structured.has("description")) return;
+
+  const declaredName = parsed.scalars.get("name") ?? "";
+  const description = parsed.scalars.get("description") ?? "";
+  const stem = basename(file).replace(/\.md$/, "");
+  const isSkillRoot = stem === "SKILL";
+  // pi's fallback when frontmatter omits a name: the parent directory name.
+  const name = declaredName || basename(dirname(file));
+  let usable = true;
+
+  if (description.trim() === "") {
+    // pi's exact wording, so a search for the message people actually see
+    // lands here.
+    audit.problems.push({ file, message: "description is required" });
+    usable = false;
+  } else if (description.length > MAX_DESCRIPTION_LENGTH) {
+    audit.problems.push({
+      file,
+      message: `description exceeds ${MAX_DESCRIPTION_LENGTH} characters (${description.length})`,
+    });
+  }
+
+  for (const message of nameProblems(name)) {
+    audit.problems.push({ file, message });
+  }
+
+  // House rules pi does not enforce, both of which produce a skill that loads
+  // and then never does anything.
+  if (!declaredName) {
+    audit.problems.push({
+      file,
+      message: "name is required (pi would fall back to the directory name)",
+    });
+  } else if (!isSkillRoot && declaredName !== stem) {
+    audit.problems.push({
+      file,
+      message: `name "${declaredName}" does not match filename "${stem}.md"`,
+    });
+  }
+
+  // The brief routes on `kind`, and a skill with no kind is silently filed as
+  // `domain` — which means a process skill without one stops being offered for
+  // its phase and nobody finds out.
+  const kind = parsed.scalars.get("kind") ?? "";
+  if (!kind) {
+    audit.problems.push({ file, message: `kind is required (one of ${SKILL_KINDS.join(", ")})` });
+  } else if (!SKILL_KINDS.includes(kind)) {
+    audit.problems.push({
+      file,
+      message: `unknown kind "${kind}" (expected one of ${SKILL_KINDS.join(", ")})`,
+    });
+  }
+
+  // A typo in `phases:` is invisible: the skill loads, and the brief never
+  // offers it, because no phase is ever called `verfiy`.
+  for (const phase of parsed.lists.get("phases") ?? []) {
+    if (!KNOWN_PHASES.includes(phase)) {
+      audit.problems.push({
+        file,
+        message: `unknown phase "${phase}" (expected one of ${KNOWN_PHASES.join(", ")})`,
+      });
+    }
+  }
+  if (parsed.structured.has("phases") || parsed.structured.has("tags")) {
+    audit.problems.push({
+      file,
+      message: "`tags` and `phases` must be inline lists, e.g. `tags: [a, b]`",
+    });
+  }
+
+  if (usable) audit.skills.push({ file, name: declaredName || name, description });
+}
+
+/** pi: validateName. */
+export function nameProblems(name: string): string[] {
+  const problems: string[] = [];
+  if (name.length > MAX_NAME_LENGTH) {
+    problems.push(`name exceeds ${MAX_NAME_LENGTH} characters (${name.length})`);
+  }
+  if (!NAME_RE.test(name)) {
+    problems.push("name contains invalid characters (must be lowercase a-z, 0-9, hyphens only)");
+  }
+  if (name.startsWith("-") || name.endsWith("-")) {
+    problems.push("name must not start or end with a hyphen");
+  }
+  if (name.includes("--")) {
+    problems.push("name must not contain consecutive hyphens");
+  }
+  return problems;
+}
+
+/** One line per problem, for a test failure message or a CLI. */
+export function formatAudit(audit: SkillAudit, root?: string): string {
+  if (audit.problems.length === 0) {
+    return `${audit.skills.length} skills, no problems`;
+  }
+  const rel = (file: string) => (root && file.startsWith(root) ? file.slice(root.length + 1) : file);
+  return audit.problems.map((p) => `${rel(p.file)}: ${p.message}`).join("\n");
+}

package/src/core/types.ts

@@ -223,6 +223,8 @@ export type Brief = {
   gate: GateResult | null;
   progress: { tasksDone: number; tasksTotal: number; featuresDone: number; featuresTotal: number };
   retries: { task: number; feature: number; phase: number; max: number };
+  /** Craft skills worth reading before starting this task, best match first. */
+  skills: { name: string; description: string; why: string }[];
   notes: string[];
 };
 

package/harness/skills/README.md

@@ -1,60 +0,0 @@
-# Craft Skills
-
-How to do the work WELL — the engineering discipline behind each pipeline
-phase. The phase docs (`harness/docs/phases/`) say *what* to produce; these
-skills say *how* an expert produces it.
-
-`the infinity_brief tool` matches skills to your current task and points you at
-the right ones. Read the referenced skill BEFORE working — it is short and
-it will change what you do. Find skills yourself:
-`infinity-harness capability match "<your task>"`.
-
-## Process skills (phase-mapped)
-
-| Skill | Use during | One-liner |
-|-------|-----------|-----------|
-| `grilling.md` | DEFINE | Stress-test the spec with relentless questions |
-| `domain-modeling.md` | DEFINE | Pin down domain terms before writing code |
-| `research.md` | DEFINE, anytime | Answer questions from primary sources only |
-| `planning-tasks.md` | PLAN | Break specs into tracer-bullet vertical slices |
-| `codebase-design.md` | PLAN, SIMPLIFY | Design deep modules behind small interfaces |
-| `tdd.md` | BUILD | Red → green loop; tests worth keeping |
-| `prototype.md` | BUILD | Throwaway code that answers a design question |
-| `diagnosing-bugs.md` | VERIFY, anytime | Build a feedback loop before hypothesizing |
-| `code-review.md` | REVIEW | Two-axis review: standards + spec |
-| `resolving-merge-conflicts.md` | anytime | Resolve conflicts by original intent |
-
-## Domain skills (task-matched by tags)
-
-`databases` · `http-apis` · `auth-security` · `frontend-ui` ·
-`testing-infra` · `concurrency-async` · `performance` ·
-`error-handling-logging` · `config-and-secrets` · `cli-design`
-
-## Frontier playbook (how a strong model operates)
-
-| Skill | Delivery surface |
-|-------|-----------------|
-| `self-review.md` | Its pass runs before EVERY validate (briefs remind you) |
-| `stuck-protocol.md` | Referenced when retries fail — stop thrashing, escalate cleanly |
-| `context-hygiene.md` | Externalize discoveries the moment they happen |
-| `scope-discipline.md` | The contract is the boundary; park everything else |
-
-## The capability ladder (meta-skills)
-
-| Skill | Purpose |
-|-------|---------|
-| `capability-acquisition.md` | HAVE → ACQUIRE → CREATE → KEEP, for skills/MCP/tools |
-| `writing-skills.md` | How to author a skill worth keeping |
-| `building-mcp-servers.md` | Scaffold, fill handlers, self-test, register |
-| `building-tools.md` | Project tool standards + registration |
-
-Growing the library IS part of the job: acquired and created capabilities
-are registered (`infinity-harness capability add ...`) so the next task starts
-ahead. Export your accumulated skills across projects:
-`infinity-harness capability export`.
-
-## Attribution
-
-Skills marked "Adapted from mattpocock/skills" derive from
-[Matt Pocock's skills repository](https://github.com/mattpocock/skills)
-(MIT License, © 2026 Matt Pocock), adapted for the infinity-harness pipeline.