- AI 하네스 참조 문서·스킬 추가 및 AGENTS.md, .agent/project.md 갱신 - 사업정보: 수정 권한(내부·재단) 계정에 배정 캘린더 버튼 추가 - 사업정보: 모니터링 계정은 본인 배정 슬롯만 표시, 툴팁에 모니터링/컨설팅 구분 표시 - 공연 상세: 모니터링 계정에는 관계자 정보 숨김 - 신청자 수·평가위원 조회 hook에 enabled 옵션 추가
38 lines
2.0 KiB
Markdown
38 lines
2.0 KiB
Markdown
---
|
|
name: karpathy-guidelines
|
|
description: Keep implementation, refactoring, and code review assumption-aware, simple, surgical, and tied to verifiable success criteria.
|
|
---
|
|
|
|
<!--
|
|
GENERATED BY KRI AGENT HARNESS. DO NOT EDIT DIRECTLY.
|
|
Source: skills/karpathy-guidelines/SKILL.md
|
|
-->
|
|
# Karpathy Guidelines
|
|
|
|
Use these guidelines while implementing, refactoring, or reviewing code. They refine execution quality but do not expand the approved task scope.
|
|
|
|
## Think Before Coding
|
|
|
|
- Inspect the relevant code and repository conventions before choosing a solution.
|
|
- Surface an assumption when different choices would materially change behavior, compatibility, data, or scope.
|
|
- Ask only when the decision cannot be discovered safely and a reasonable assumption would be risky. Otherwise proceed with the smallest reasonable assumption and report it.
|
|
|
|
## Simplicity First
|
|
|
|
- Implement the smallest complete solution that satisfies the observable requirement.
|
|
- Do not add speculative abstractions, extension points, configuration, fallback paths, or dependencies for hypothetical future use.
|
|
- Prefer an existing repository pattern or standard-library capability over a new local framework.
|
|
|
|
## Surgical Changes
|
|
|
|
- Every changed line must trace to the approved objective, required validation, or a necessary compatibility adjustment.
|
|
- Preserve existing naming, structure, public behavior, and formatting outside that boundary.
|
|
- Do not mix the task with unrelated cleanup. Remove dead code, duplication, or ceremony introduced by the current change before finishing.
|
|
|
|
## Goal-Driven Execution
|
|
|
|
- Translate the request into observable success criteria before implementation.
|
|
- Choose the narrowest check that can fail for the behavior being changed, then run broader repository checks when appropriate.
|
|
- Iterate only within the approved scope until the criteria pass or a concrete blocker is established.
|
|
- Before reporting completion, inspect the final diff for unnecessary code and use `verification-before-completion` for fresh evidence.
|