No description
  • Go Template 93.7%
  • Smarty 6.3%
Find a file
Daniel McGeever 3b4c4eb2c9 docs(tandoor): 0.8.0 — prep is a step, and a recipe is not a changelog
Two corrections from cooking off the converted library.

Knife work was ending up in ingredient notes, because "attach each line to
the step that uses it" puts preparation wherever the ingredient is consumed
— so "diced into 1 cm pieces" is discovered when the wok is already hot.
Nobody heats a pan and then starts jointing chicken. The note keeps the
specification, since that is what scaling and shopping need; the action goes
on the timeline in plain words with no quantities, because the master
ingredient list is on screen the whole time.

Where prep goes is the critical-path question again, asked about a step that
was never counted. No usable window (wok, stir-fry, risotto) means all knife
work before any heat. A real unattended window — a 20-minute simmer, a
25-minute roast — means prep belongs inside it, said out loud. Blanket
"prep everything first" is the taco preheat error pointing the other way:
it front-loads chopping onto a recipe with a roast you could have chopped
during, and leaves you at a cold hob.

The provenance section is deleted rather than edited. It instructed exactly
the wrong thing: record in the description that amounts were converted and
servings inferred. That produced recipes carrying "1 lb in the source",
"a mangled conversion", "title de-shouted" — a record of editing work, which
to anyone the recipe is shared with is noise about a document they never saw.
The test is now: would this line make sense to someone you shared it with?
Conversions happen silently, because the converted amount IS the recipe now.

An italic aside survives only if it changes how you cook — "cold stock
stalls the rice" earns its place, "the source only mentions this in its
ingredient list" does not. One exception is kept: where the source's own
quantity is unsafe as written, such as US "chili powder" measured in
tablespoons against the pure ground chilli sold here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-16 15:10:53 +00:00
.claude-plugin docs(tandoor): 0.8.0 — prep is a step, and a recipe is not a changelog 2026-08-16 15:10:53 +00:00
plugins docs(tandoor): 0.8.0 — prep is a step, and a recipe is not a changelog 2026-08-16 15:10:53 +00:00
skills feat(project-scaffold): enrich CLAUDE.md, graphify defaults, promote-skill; drop dev-hub (#1) 2026-06-28 11:29:55 +00:00
.gitignore chore: gitignore .env (tooling secrets must never be committed) 2026-05-31 07:53:13 +00:00
README.md chore: remove dev-hub plugin (project retired) 2026-07-12 10:50:28 +00:00

claude-resources

Central Claude Code marketplace for the homelab. Holds the marketplace index (.claude-plugin/marketplace.json), the per-project plugins under plugins/, and (later) shared cross-project skills under shared/.

Install (one-time, per VM, user scope)

claude plugin marketplace add https://forgejo.towneygorm.cc/daniel/claude-resources.git --scope user
claude plugin install project-scaffold@claude-resources --scope user

Restart Claude Code (or start a new session) to load the plugin.

Development loop

Edit a plugin in place, then test it privately without affecting consumers:

# one-time, on the dev machine, scoped to this repo
claude plugin marketplace add ~/projects/claude-resources --scope local

Skill edits are picked up live; for command/hook/MCP/plugin.json changes run /reload-plugins. Consumers stay pinned to the git-URL install and see nothing until you merge to main and they run claude plugin update.