claude-agent-skills 1.3.7 → 1.4.0

package/lib/banner.js

@@ -23,20 +23,21 @@ const SKILLS_LINES = [
 const ART = [...CLAUDE_LINES, ...SKILLS_LINES];
 const MAX_WIDTH = Math.max(...ART.map(l => l.length));
 
-// One pride stripe per art line (12 lines → 2 lines per colour)
+// Colour palette per art line — crimson gradient top → deep red bottom.
+// To restore pride rainbow: replace each entry with the pride colours.
 const PRIDE = [
-  [220,  30,  30], // red
-  [220,  30,  30],
-  [255, 140,   0], // orange
-  [255, 140,   0],
-  [255, 210,   0], // yellow
-  [255, 210,   0],
-  [ 30, 185,  30], // green
-  [ 30, 185,  30],
-  [ 30, 100, 255], // blue
-  [ 30, 100, 255],
-  [150,  30, 230], // purple
-  [150,  30, 230],
+  [240,  65,  65],
+  [230,  55,  55],
+  [215,  42,  42],
+  [200,  32,  32],
+  [185,  25,  25],
+  [170,  18,  18],
+  [155,  13,  13],
+  [140,  10,  10],
+  [125,   8,   8],
+  [110,   6,   6],
+  [ 95,   4,   4],
+  [ 80,   3,   3],
 ];
 
 const sleep = ms => new Promise(r => setTimeout(r, ms));

package/lib/picker.js

@@ -38,12 +38,11 @@ export async function skillPicker({ message, options }) {
   const numCols = Math.max(1, Math.floor((termW - 2) / colW));
   const numRows = Math.ceil(options.length / numCols);
 
-  // Fixed layout heights
-  const HEADER   = 2;
-  const GRID_H   = numRows;
-  const SEP      = 1;
-  const DESC_H   = Math.max(5, Math.min(8, termH - HEADER - GRID_H - SEP - 3));
-  const FOOTER   = 1;
+  // Layout heights — DESC_H is computed dynamically per render from wrapped lines
+  const HEADER = 2;
+  const GRID_H = numRows;
+  const SEP    = 1;
+  const FOOTER = 1;
 
   let cursor = 0;
   const sel  = new Set();
@@ -84,16 +83,14 @@ export async function skillPicker({ message, options }) {
       lines.push(row);
     }
 
-    // Separator + description
-    lines.push(muted('├' + '─'.repeat(Math.min(termW - 2, 78)) + '┤'));
-
+    // Separator + full description — all lines, no cap
     const focused = options[cursor];
     const desc    = focused?.description ?? '';
-    // Cap wrap at 72 chars so descriptions always break into multiple lines
     const wrapW   = Math.min(termW - 6, 72);
-    const wrapped = desc ? wordWrap(desc, wrapW) : [];
-    for (let i = 0; i < DESC_H; i++) {
-      const line = wrapped[i] ?? '';
+    const wrapped = desc ? wordWrap(desc, wrapW) : [''];
+
+    lines.push(muted('├' + '─'.repeat(Math.min(termW - 2, 78)) + '┤'));
+    for (const line of wrapped) {
       lines.push(muted('│ ') + white(line));
     }
 
@@ -109,13 +106,12 @@ export async function skillPicker({ message, options }) {
 
   function draw() {
     const lines = renderGrid();
-    // Go up by however many lines we drew last time
-    if (lastLines > 0) {
-      process.stdout.write(`\x1b[${lastLines}A`);
-    }
+    if (lastLines > 0) process.stdout.write(`\x1b[${lastLines}A`);
     for (const line of lines) {
       process.stdout.write('\x1b[2K' + line + '\n');
     }
+    // Erase any leftover content from a previously taller render
+    process.stdout.write('\x1b[0J');
     lastLines = lines.length;
   }
 

package/lib/theme.js

@@ -1,6 +1,10 @@
 import ansis from 'ansis';
 
-export const BRAND_HEX = '#FF69B4'; // hot pink
+// ── Colour mode ─────────────────────────────────────────────────────────────
+// Flip PRIDE_MODE to true for pride month to restore rainbow palette.
+export const PRIDE_MODE = false;
+
+export const BRAND_HEX = '#B91919'; // metallic crimson
 
 const ok = () => !process.env.NO_COLOR && ansis.isSupported();
 
@@ -11,25 +15,30 @@ export const muted   = t => ok() ? ansis.dim(t) : t;
 export const white   = t => ok() ? ansis.white(t) : t;
 export const strip   = t => ansis.strip(t);
 
-// ── Pride mode ─────────────────────────────────────────────────────────────
-// Set to false after June to revert skill names to brand pink.
-export const PRIDE_MODE = true;
+// Metallic crimson — bright at index 0, steps down, then back up (cycling shimmer)
+const CRIMSON = [
+  [235,  60,  60],
+  [210,  38,  38],
+  [185,  25,  25],
+  [160,  15,  15],
+  [185,  25,  25],
+  [210,  38,  38],
+];
 
+// Pride rainbow — restore for pride month
 const PRIDE_PALETTE = [
-  [220,  30,  30],   // red
-  [255, 140,   0],   // orange
-  [220, 200,   0],   // yellow
-  [ 30, 185,  30],   // green
-  [ 30, 100, 255],   // blue
-  [150,  30, 230],   // purple
+  [220,  30,  30],
+  [255, 140,   0],
+  [220, 200,   0],
+  [ 30, 185,  30],
+  [ 30, 100, 255],
+  [150,  30, 230],
 ];
 
-// Returns a color function for the nth skill. Cycles through pride palette in
-// PRIDE_MODE, falls back to brand pink otherwise.
 export function skillColor(index) {
   if (!ok()) return t => t;
-  if (!PRIDE_MODE) return brand;
-  const [r, g, b] = PRIDE_PALETTE[index % PRIDE_PALETTE.length];
+  const palette = PRIDE_MODE ? PRIDE_PALETTE : CRIMSON;
+  const [r, g, b] = palette[index % palette.length];
   return t => ansis.rgb(r, g, b)(t);
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-agent-skills",
-  "version": "1.3.7",
+  "version": "1.4.0",
   "description": "Install and manage Pavi's Claude Code agent skills",
   "license": "MIT",
   "type": "module",

package/skills.json

@@ -1,7 +1,7 @@
 {
   "schema_version": 1,
   "name": "claude-agent-skills",
-  "version": "1.3.7",
+  "version": "1.4.0",
   "skills": [
     "ask-matt",
     "brainstorming",
@@ -108,25 +108,25 @@
   "descriptions": {
     "ask-matt": "You don't remember every skill, so ask.",
     "brainstorming": "Help turn ideas into fully formed designs and specs through natural collaborative dialogue.",
-    "cavecrew": "Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main c…",
+    "cavecrew": "Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation.",
     "caveman": "Respond terse like smart caveman. All technical substance stay. Only fluff die.",
     "caveman-commit": "Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.",
-    "caveman-compress": "Compress natural language files (CLAUDE.md, todos, preferences) into caveman-speak to reduce input tokens. Compressed version overwrites original. Human-readable backup saved as `<filename>.original.…",
+    "caveman-compress": "Compress natural language files (CLAUDE.md, todos, preferences) into caveman-speak to reduce input tokens. Compressed version overwrites original. Human-readable backup saved as `<filename>.original.md`.",
     "caveman-help": "Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything. Output in caveman style.",
     "caveman-review": "Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.",
-    "caveman-stats": "This skill is delivered by `hooks/caveman-stats.js` (read by `hooks/caveman-mode-tracker.js` on `/caveman-stats`). The model does not need to do anything when this skill fires — the hook returns `dec…",
-    "codebase-design": "Design **deep modules**: a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface. Use this language and these principles wherever code is being designed o…",
+    "caveman-stats": "This skill is delivered by `hooks/caveman-stats.js` (read by `hooks/caveman-mode-tracker.js` on `/caveman-stats`). The model does not need to do anything when this skill fires — the hook returns `decision: \"block\"` with the formatted stats as the reason. The user sees the numbers immediately.",
+    "codebase-design": "Design **deep modules**: a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface. Use this language and these principles wherever code is being designed or restructured. The aim is leverage for callers, locality for maintainers, and testability for everyone.",
     "council": "You are the orchestrator. Dispatch three Haiku subagents in parallel — each a council member giving an independent perspective — then synthesize their responses into a unified recommendation.",
     "diagnosing-bugs": "A discipline for hard bugs. Skip phases only when explicitly justified.",
-    "dispatching-parallel-agents": "You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit…",
-    "domain-modeling": "Actively build and sharpen the project's domain model as you design. This is the *active* discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down th…",
+    "dispatching-parallel-agents": "You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.",
+    "domain-modeling": "Actively build and sharpen the project's domain model as you design. This is the *active* discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `CONTEXT.md` for vocabulary is not this skill — that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)",
     "edit-article": "1. First, divide the article into sections based on its headings. Think about the main points you want to make during those sections.",
     "executing-plans": "Load plan, review critically, execute all tasks, report when complete.",
     "finishing-a-development-branch": "Guide completion of development work by presenting clear options and handling chosen workflow.",
     "git-guardrails-claude-code": "Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them.",
     "grill-me": "Run a `/grilling` session.",
     "grill-with-docs": "Run a `/grilling` session, using the `/domain-modeling` skill.",
-    "grilling": "Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For eac…",
+    "grilling": "Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.",
     "handoff": "Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.",
     "i-am-dumb": "The user wants something explained in extreme detail. They are not actually dumb — they just want the full picture without assumptions about what they already know.",
     "implement": "Implement the work described by the user in the PRD or issues.",
@@ -141,7 +141,7 @@
     "ponytail-review": "Review the diff or codebase for over-engineering only. Goal: make the code shorter. Report findings as one line each. Apply no fixes unless explicitly asked.",
     "prototype": "A prototype is **throwaway code that answers a question**. The question decides the shape.",
     "receiving-code-review": "Code review requires technical evaluation, not emotional performance.",
-    "requesting-code-review": "Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on th…",
+    "requesting-code-review": "Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.",
     "resolving-merge-conflicts": "1. **See the current state** of the merge/rebase. Check git history, and the conflicting files.",
     "scaffold-exercises": "Create exercise directory structures that pass `pnpm ai-hero-cli internal lint`, then commit with `git commit`.",
     "setup-matt-pocock-skills": "Scaffold the per-repo configuration that the engineering skills assume:",
@@ -157,8 +157,8 @@
     "using-git-worktrees": "Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available.",
     "using-superpowers": "<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP>",
     "verification-before-completion": "Claiming work is complete without verification is dishonesty, not efficiency.",
-    "writing-great-skills": "A skill exists to wrangle determinism out of a stochastic system. **Predictability** — the agent taking the same _process_ every run, not producing the same output — is the root virtue; every lever b…",
-    "writing-plans": "Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, cod…",
+    "writing-great-skills": "A skill exists to wrangle determinism out of a stochastic system. **Predictability** — the agent taking the same _process_ every run, not producing the same output — is the root virtue; every lever below serves it.",
+    "writing-plans": "Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.",
     "writing-skills": "**Writing skills IS Test-Driven Development applied to process documentation.**"
   }
 }