feat(aidd-context): refresh cook recipes and enforce heading hierarchy - #521
feat(aidd-context): refresh cook recipes and enforce heading hierarchy#521alexsoyes wants to merge 4 commits into
Conversation
Keep recipe steps actionable, enforce valid heading nesting, and preserve verified token and MCP guidance.
Separate durable agent instructions from scoped rules and keep each optimization technique directly actionable.
Keep bundled guidance concise, reproducible, and mechanically verifiable.
Keep lint settings compatible with the installed Biome schema.
19c032e to
09f2d32
Compare
|
@blafourcade t'es good dessus ? |
| ## Input | ||
|
|
||
| The recipe topic. Ask for any missing field (description, steps, verify, related) before writing. | ||
| The recipe topic. Infer description, steps, and verification from the request and research; ask only for a missing decision that changes the recipe's outcome or scope. |
There was a problem hiding this comment.
Je pense que le Ask devrait être dans un step plutôt que l'Input ?
| @@ -1,12 +1,12 @@ | |||
| <!-- Read before spawning research agents in 03-research. The scouting angles, the bar each candidate must clear, and how to verify them. Not a recipe itself. --> | |||
| <!-- Read during 03-research. The scouting angles, the bar each candidate must clear, and how to verify them. Not a recipe itself. --> | |||
There was a problem hiding this comment.
Besoin de remettre during 03 si on le nomme dans cette step uniquement ?
| @@ -9,24 +9,41 @@ Rules for every recipe file the skill writes. | |||
| - Project path: `aidd_docs/recipes/<kebab-slug>.md`. | |||
| - Bundled path, only for explicit framework-source edits: `plugins/aidd-context/skills/12-cook/assets/recipes/<kebab-slug>.md`. | |||
There was a problem hiding this comment.
C'est spécific au framework ici, est-ce qu'on veut ce cas précis dans un skill d'un framework commun ?
|
|
||
| Check one recipe or every available recipe without changing files. | ||
|
|
||
| ```text |
There was a problem hiding this comment.
Pourquoi on a ça ici dans le skill lui même ? Ca serait à la limite dans le SKILL.md et encore
| ``` | ||
|
|
||
| ```md | ||
| @../references/recipe-locations.md |
There was a problem hiding this comment.
On ne permet pas dans les règles du skill-generate les references comme ça au niveau du titre mais dans les step associées. J'ai bien vérifié et regénéré avec le skill il ne propose jamais ça de mon côté
| ## Process | ||
|
|
||
| 1. **Resolve.** Resolve one recipe with `@../references/recipe-locations.md`, or keep `all` as the full project-plus-bundled scope. | ||
| 2. **Check structure.** Run `node <skill-directory>/scripts/validate-recipe.mjs <resolved-path>` or `node <skill-directory>/scripts/validate-recipe.mjs --all`. Preserve its exit code and findings. |
There was a problem hiding this comment.
Je pense qu'on peut simplifier en disant run the script with appropriate input (all, etc)
|
|
||
| ## Validation | ||
|
|
||
| - Run `actions/05-validate.md` after `upsert`, deterministic pass first and semantic pass second; fix and rerun until both pass. |
There was a problem hiding this comment.
Pourquoi a t on des appels d'actions dans les references ?
|
|
||
| # Cook | ||
|
|
||
| Maintains recipe how-to sheets. Project recipes live in `aidd_docs/recipes/`; bundled recipes ship inside this skill under `assets/recipes/`. |
There was a problem hiding this comment.
Peux-tu appeler skill-generate pour changer le foramt de ce fichier avec le mermaid chart désormais ?
| Run `list` to survey project and bundled recipes, `research` to gather insights, `upsert` to author one, `apply` to run an existing one against the project. Always run `research` before authoring or substantially updating a recipe — never draft from memory alone. Run `list` first when the user names no recipe. | ||
| Validation entry points: `cook validate <recipe>` and `cook validate all`. | ||
|
|
||
| Run `list` to survey project and bundled recipes, `research` to gather insights, `upsert` to author one, `apply` to run an existing one against the project, and `validate` to check one or all recipes without changing them. Always run `research` before authoring or substantially updating a recipe — never draft from memory alone. Run `list` first when the user names no recipe. |
There was a problem hiding this comment.
Avec le nouveau format et le mermaid chart tu auras normalement pas besoin d'expliciter autant de chose
| - Bundled path, only for explicit framework-source edits: `plugins/aidd-context/skills/12-cook/assets/recipes/<kebab-slug>.md`. | ||
| - The recipe opens with the H1 title, then one plain sentence of description — no "Goal:" label, no blockquote, no metadata table. | ||
| - Sections: the description, `## Why`, then the steps. `## Verify` is optional — omit it when it adds little. End with an optional short conclusion. Never add a `## Related` section: links live inline where they are used. | ||
| - Sections: the description, then the steps. `## Verify` is optional only when no useful observable check exists. End with at most one short conclusion. Never add a `## Related` section: links live inline where they are used. |
There was a problem hiding this comment.
L'assets n'est pas assez descriptive pour qu'il remplisse correctement ? Tu es obligé d'indiquer autant de détail pour tout remplir ? (peut être, je challenge si pas de AI Slop)
Summary
Validation
node scripts/check-markdown-links.js— 0 broken links in 537 filesgit diff --checkCLI tests were not run because the PR changes no
cli/**files and the gitignored CLI dependencies are intentionally absent.