Refactor: add agent training and repository conventions#318
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
AGENTS.mdto define the repository's training workflow and contribution conventions.Problem
There was no repository-level guide describing how this project should be used as a backend training ground and portfolio project, or how the agent should coach, review, and structure iterative learning cycles.
Solution
Introduce an
AGENTS.mddocument that defines the agent role, coaching approach, training cycle, cycle completion criteria, transition criteria, output expectations, and Git/GitHub conventions.Changes
Example
A future session can now start with the phrase
새로운 학습 시작하자, and the agent will treat it as the trigger for a new guided learning cycle.Related Issues
N/A