hoard

Étoiles0

Forks0

Mis à jour24 juillet 2026 à 11:16

Save a newly-figured-out trick as a minimal working example in hoard/, so future sessions can reuse or recombine it. Use after solving something non-obvious for the first time.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

moritalous

moritalous/agentic-engineering-patterns

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	hoard
description	Save a newly-figured-out trick as a minimal working example in hoard/, so future sessions can reuse or recombine it. Use after solving something non-obvious for the first time.

Hoard things you know how to do

We only ever need to figure out a trick once. If it's documented with a working code example, any future session can consult it and apply it to any similarly-shaped problem — or recombine two hoard entries into something new.

Recording an entry

The argument to this skill is the trick that was just figured out.

Create hoard/<slug>/README.md with:
- What it does — one or two sentences, phrased as the question it answers ("Can a web page run OCR in JavaScript alone?").
- The working example — the minimal complete code, in the README or as runnable files alongside it. It must be running code that was actually executed, not a theoretical sketch — knowing something is possible is not the same as having seen it work.
- How to run it — the exact command(s).
- Gotchas — anything that cost time to discover.
Keep it minimal: strip the example down to just the trick itself.

Using the hoard

Before building something new, search hoard/ for existing examples to adapt.
Recombine: the strongest prompting pattern is feeding two or more working examples into one prompt — "example A shows X, example B shows Y, combine them to build Z".
External examples work too: fetch raw sources with curl (WebFetch summarizes; you usually want the raw HTML/code), or clone reference repos to /tmp and search them there.

Plus depuis ce dépôt

même dépôt

compound

moritalous/agentic-engineering-patterns

Run the compound engineering step — a short retrospective after a piece of work that folds what was learned back into CLAUDE.md, the skills, or the hoard. Use at the end of every significant task.

2026-07-240

git-rescue

moritalous/agentic-engineering-patterns

Sort out git messes and perform history surgery — undo/rewrite commits, resolve conflicted merges and rebases, recover lost code via reflog, find regressions with git bisect.

2026-07-240

interactive-explanation

moritalous/agentic-engineering-patterns

Build a self-contained interactive or animated HTML page that explains how an algorithm or piece of code works. Use to pay down cognitive debt when a written explanation isn't enough.

2026-07-240

manual-test

moritalous/agentic-engineering-patterns

Manually exercise code beyond the automated tests — python -c for libraries, curl for APIs, browser automation with screenshots for web UIs — and document the results. Use after tests pass, before declaring work done.

2026-07-240

pr-ready

moritalous/agentic-engineering-patterns

Pre-pull-request checklist — verify the code works, the diff is reviewable, and the PR carries context and evidence of testing. Run before opening any pull request.

2026-07-240

proofread

moritalous/agentic-engineering-patterns

Proofread a document before publication — spelling, grammar, repetition, logical and factual errors, weak arguments, placeholder links. Reports issues; never rewrites the author's voice.

2026-07-240

name	hoard
description	Save a newly-figured-out trick as a minimal working example in hoard/, so future sessions can reuse or recombine it. Use after solving something non-obvious for the first time.

Hoard things you know how to do

Recording an entry

The argument to this skill is the trick that was just figured out.

Create hoard/<slug>/README.md with:
- What it does — one or two sentences, phrased as the question it answers ("Can a web page run OCR in JavaScript alone?").
- The working example — the minimal complete code, in the README or as runnable files alongside it. It must be running code that was actually executed, not a theoretical sketch — knowing something is possible is not the same as having seen it work.
- How to run it — the exact command(s).
- Gotchas — anything that cost time to discover.
Keep it minimal: strip the example down to just the trick itself.

Using the hoard

Before building something new, search hoard/ for existing examples to adapt.
Recombine: the strongest prompting pattern is feeding two or more working examples into one prompt — "example A shows X, example B shows Y, combine them to build Z".
External examples work too: fetch raw sources with curl (WebFetch summarizes; you usually want the raw HTML/code), or clone reference repos to /tmp and search them there.