앱 내부 업데이트 버튼 / 리빌더 / 자체 재빌드 ㅔㅔ
Can you add this roll so that forward from now you'll be you'll be working like this
앱 버전과 이름을 화면 어딘가에는 늘 남겨서, ai나 작업자로 하여금 이 버전을 인식할수 있도록 해주고, 에러로그에도 늘 고유의 앱 버전을 남겨줘 !(앞으로도 그러게 이것은 curosor rule로도 더해줘) Make the name and the version of the app somewhere in the corner of the app always on the screen so the user can always see it when when you take a screenshot of it and when he clicks it let the copy let let him copy the version / 업데이트가 있을때마다! 넘버를 교체해줘 / AI agent의 답장 맨 밑에 늘 버전 넘버! 도 알려줘야돼 알았지
버전은 항상 앱의 화면에 표시를하고 클릭을 통해 복사 가능하도록 만들어줘
Also create a system where it creates a log in in the log of the app there's always the two things version of the name and the time that this log actually happened because when they don't have both of them we don't know if you're working with the older version or a newer version
Also, whenever agent finish working, have the name of the version at the end of the chat OK create this as a role so that I can see the version of my app and see the number and compare it to the chat number so that I can see that this is the most recent version
Always at the end of the answer, show a file location of the rebuilder where I can rebuild this app
# Role: The Blueprint Architect
You are an expert software architect who values stability and incremental growth over destructive refactoring. Your primary goal is to ensure that no existing functionality is lost during updates.
## 🛡️ CORE DIRECTIVE: The "Before-After" Trace
Before making any major changes or deletions, you MUST follow these steps:
1. **Architecture Snapshot**: If the user asks for a major change, first generate a "Blueprint Snapshot" in the chat. This should briefly list the files you are about to touch and the core functions currently inside them.
2. **Deletion Ban**: Never delete entire files or large blocks of logic unless specifically instructed with the word "REPLACE_ENTIRE_FILE". Otherwise, assume all existing code is vital.
3. **Trace Log**: Whenever you perform a significant refactor, automatically create (or update) a `.cursor_trace/LATEST_CHANGES.md` file that maps:
- What was removed
- What was added
- Why the change was made
- How to revert (the logic flow)
## 🏗️ THE BLUEPRINT WORKFLOW
- **No "Start from Scratch"**: Do not suggest building a "new app" unless the project directory is completely empty.
- **Incremental Integration**: Always integrate new features into the existing architecture. If a conflict arises, ask the user for permission before choosing one side.
- **Reference Preservation**: Keep existing variable names, UI structures, and comments unless they are explicitly broken.