Imported from honeychest/lab (AGENTS.md). Install upstream with npx skills add honeychest/lab. Copyright stays with the author.

Apply Always : /chs/chs-rules.md

인수인계 (모든 AI 에이전트)

• docs/HANDOFF.md 가 비어 있지 않으면 먼저 읽고 이어서 작업한다 (일회성 작업의 세션 간 인계).

폴더별 코드 규칙 (모든 AI 에이전트)

• frontend/AGENTS.md, springboot/AGENTS.md — 해당 폴더의 파일을 수정하기 전에 읽는다. (공용 훅·순수 모듈 등 "가져다 쓸 것" 모범 패턴과 금지 사항이 정리돼 있음)

GitNexus — Code Intelligence

This project is indexed by GitNexus as lab (13040 symbols, 27720 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

• MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
• MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
• MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
• When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
• When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

Never Do

• NEVER edit a function, class, or method without first running gitnexus_impact on it.
• NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
• NEVER rename symbols with find-and-replace — use gitnexus_rename which understands the call graph.
• NEVER commit changes without running gitnexus_detect_changes() to check affected scope.

Resources

CLI