Repository navigation
Conversation
|
@alexsoyes mes retours et ke me questionne sur la responsabilité de Project Memory: il commence à faire peut-être trop de choses. Son rôle, c'est le contexte à la base et on commence à faire des vérifications techniques (tester l'accès à des services). Qu'est-ce que verify apporte en plus de l'étape 3 de la recette, qui donne déjà le prompt pour le faire ? Et tu dis dans la description que l'accès n'a pas été testé en live, on ne sait pas encore ce que ça apporte avec l'execution en contexte réel. |
|
|
||
| ## Process | ||
|
|
||
| 1. **Map**: Resolve `connect-services.md` from the local recipe catalogue, then read it by its relative path and read the relevant project memory to identify required services, accounts and targets. |
There was a problem hiding this comment.
Besoin de la notion de relative path, il sait pas le faire seul ?
|
|
||
| > This gives the assistant the right repository, workspace and conventions for its work. | ||
|
|
||
| ## CLI, MCP, API or SDK? |
There was a problem hiding this comment.
Le titre annonce 4 options, mais les tables par service plus bas n'en montrent que 2 (CLI et MCP), API et SDK n'apparaissent qu'ici on a pas d'exemple ?
|
|
||
| Add any other services your team uses to the relevant table. `—` means no option is listed here. | ||
|
|
||
| ### 2) 🔌 Install and sign in |
There was a problem hiding this comment.
On ne parle que de Claude Code (/mcp, claude plugin install). L'ancienne recipe couvrait Codex, Cursor et Copilot. Tu veux prendre le parti de Claude only en exemple ?
|
|
||
| Start a new session, run `/mcp`, select Figma, then **Authenticate**; other clients use [Figma's setup guide](https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/). | ||
|
|
||
| - **API / GitHub**: Wrap reusable API access in a skill with `/aidd-context:04-skill-generate` ([Generate Skill](https://github.com/ai-driven-dev/framework/blob/next/plugins/aidd-context/skills/04-skill-generate/SKILL.md)). With a token configured as described in the [REST API quickstart](https://docs.github.com/en/rest/quickstart), read the account: |
There was a problem hiding this comment.
L'exemple API est sur GitHub, alors que gh couvre déjà tout, donc il contredit la règle plus haut où API pour ce que les outils existants comme CLI ne permettent pas.
|
|
||
| Start a new session, run `/mcp`, select Figma, then **Authenticate**; other clients use [Figma's setup guide](https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/). | ||
|
|
||
| - **API / GitHub**: Wrap reusable API access in a skill with `/aidd-context:04-skill-generate` ([Generate Skill](https://github.com/ai-driven-dev/framework/blob/next/plugins/aidd-context/skills/04-skill-generate/SKILL.md)). With a token configured as described in the [REST API quickstart](https://docs.github.com/en/rest/quickstart), read the account: |
There was a problem hiding this comment.
L'appel à Skill generate c'est pour encourager à créer un skill qui norme ce genre d'appel à une API ?
|
|
||
| For each service your project uses, choose an option that covers your task. Add another only for a need the first cannot cover. | ||
|
|
||
| Memory links open the AIDD templates for the corresponding files in your project's `aidd_docs/memory/`. |
There was a problem hiding this comment.
On devrait peut être faire un lien explicite vers le skill project memory ?
| - Mark missing context as unverified, never as not needed. | ||
| 2. **Check**: Inspect available CLI, MCP, native or API access and perform one read against each required account and target. | ||
| - Continue checking the other services when one fails. | ||
| 3. **Report**: Fill `connection-report.md` from observed results, with one row per category. |
There was a problem hiding this comment.
En cas d'erreur ou blocage on fait quoi je ne vois pas ce cas de figure
| name: 02-project-memory | ||
| description: Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file. | ||
| argument-hint: setup | refresh | rewire | ||
| description: Build project memory and wire it into AI tools. Use when the user wants to set up or refresh memory, rewire it, or verify the assistant's service connections. Not for editing one existing memory file. |
There was a problem hiding this comment.
Est-ce que la description perd un peu son sens avec ça , on veut gérer la memoire AI du projet et on lie avec des vérifications techniques
| | write | write the memory | | ||
| | check | show what drifted, change nothing | | ||
| | sync | pick the tools, wire it in | | ||
| | verify-connection | verify the assistant's service access | |
There was a problem hiding this comment.
Check et verify a côté c'est bizarre ça rejoint mon sentiment qu'on fait faire des choses au skill qui n'est peut être pas sa responsabilité
| - Never invent unreadable content; setup, refresh and rewire stop when a referenced file cannot be read. | ||
| - Ask before anything ambiguous. Never default silently. | ||
| - A bank that already exists changes only through what the user approved, file by file and line by line. | ||
| - End with a short report of what changed. |
There was a problem hiding this comment.
Ici ça marche plus pour ta nouvelel action y'a pas de changement en soit ?
Replace
mcp-installationwithconnect-services: tool choices by service, setup examples and links to project memory.Add
/aidd-context:02-project-memory verifyto check access and report connection status. Allow H4 categories in recipes.Validation: 681 framework tests and 71 recipe tests pass; links and recipes validate. Live service access not tested.