api-and-interface-desi…
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints,…
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
$ npx -y skills add kevinnft/ai-agent-skills --skill scaffold-exercises --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/scaffold-exercisesContext preview
The summary Claude sees to decide when to auto-load this skill.
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
name: scaffold-exercises description: Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section. source_repo: "mattpocock/skills" source_url: "https://github.com/mattpocock/skills" source_license: "MIT" origin: aggregated language: en
Create exercise directory structures that pass `pnpm ai-hero-cli internal lint`, then commit with `git commit`.
Each exercise needs at least one of these subfolders:
When stubbing, default to `explainer/` unless the plan specifies otherwise.
Each subfolder (`problem/`, `solution/`, `explainer/`) needs a `readme.md` that:
When stubbing, create a minimal readme with a title and a description:
# Exercise Title Description here
If the subfolder has code, it also needs a `main.ts` (>1 line). But for stubs, a readme-only exercise is fine.
1. **Parse the plan** - extract section names, exercise names, and variant types 2. **Create directories** - `mkdir -p` for each path 3. **Create stub readmes** - one `readme.md` per variant folder with a title 4. **Run lint** - `pnpm ai-hero-cli internal lint` to validate 5. **Fix any errors** - iterate until lint passes
The linter (`pnpm ai-hero-cli internal lint`) checks:
When renumbering or moving exercises:
1. Use `git mv` (not `mv`) to rename directories - preserves git history 2. Update the numeric prefix to maintain order 3. Re-run lint after moves
Example:
git mv exercises/01-retrieval/01.03-embeddings exercises/01-retrieval/01.04-embeddings
Given a plan like:
Section 05: Memory Skill Building - 05.01 Introduction to Memory - 05.02 Short-term Memory (explainer + problem + solution) - 05.03 Long-term Memory
Create:
mkdir -p exercises/05-memory-skill-building/05.01-introduction-to-memory/explainer
mkdir -p exercises/05-memory-skill-building/05.02-short-term-memory/{explainer,problem,solution}
mkdir -p exercises/05-memory-skill-building/05.03-long-term-memory/explainerThen create readme stubs:
exercises/05-memory-skill-building/05.01-introduction-to-memory/explainer/readme.md -> "# Introduction to Memory" exercises/05-memory-skill-building/05.02-short-term-memory/explainer/readme.md -> "# Short-term Memory" exercises/05-memory-skill-building/05.02-short-term-memory/problem/readme.md -> "# Short-term Memory" exercises/05-memory-skill-building/05.02-short-term-memory/solution/readme.md -> "# Short-term Memory" exercises/05-memory-skill-building/05.03-long-term-memory/explainer/readme.md -> "# Long-term Memory"
191 attribution-first agent skills for Hermes Agent, Claude Code, Cursor — one installer, 28 categories, searchable catalog. See NOTICE for upstream attribution.
Repo: kevinnft/ai-agent-skills
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints,…
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze…
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test…
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to…
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend…
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure…