사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/kaizen2026/universal-agent-skills --skill implement시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Implement the work described by the user in the spec or tickets.
Before changing anything, record the current HEAD as the review fixed point.
Classify frontend work before changing it:
- If the issue/spec references an approved
docs/design/<feature>/DESIGN.md, or an approved contract clearly governs the feature, invoke/frontend-buildand treat that contract as the visual source of truth. - If the work introduces or changes a visual direction and no approved contract resolves it, stop only that frontend slice and route the unresolved decision to
/frontend-design. - If the task is a prescribed maintenance change that introduces no visual decision — for example a copy correction, bug fix, or specified reuse of an existing component — implement it through the existing design system. A new contract is not required.
Never infer that every frontend diff needs a design contract, and never invent an unresolved direction during implementation.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, invoke /code-review with the recorded fixed point. It must review committed, staged, unstaged, and untracked work from this run. Frontend changes receive its independent /frontend-review lane in addition to Standards and Spec. Resolve blocking findings and rerun affected checks before committing; preserve genuinely unavailable checks as explicit Unverified items.
Commit your work to the current branch.
