Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/drewbarontini/equilio-coding --skill equilio-frameAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Frame
Turn an initial signal into an issue-ready account of the problem. Establish what already exists: a request, issue, local file, prototype, or code. Match the depth to the work's impact and uncertainty.
Investigate who is affected, what is happening, evidence, desired outcome, constraints, proposed solutions, and open questions. Test whether a proposed solution addresses the underlying problem before treating it as settled. Distinguish observations from assumptions and decisions.
Write a local Markdown draft the user can inspect. Keep it readable as an emerging issue, not a questionnaire with empty sections. If the project already has an issue, revise the draft against that issue and preserve its useful history and links. When framing is ready, use the project's chosen GitHub, Linear, or local Markdown issue; establish the destination before creating or changing a remote issue. Bring consequential framing to the user for review when appropriate, without making every small edit a gate.
Leave a clear problem, desired outcome, known evidence, current direction if any, and the questions that could alter it. Carry accepted conclusions into the shared issue in prose rather than copying the whole draft. If work stays local, the Markdown issue itself can be the shared account. Never imply a solution or shipment is validated before it is.
