사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/drewbarontini/equilio-coding --skill equilio-frame시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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.
