monosolo1on1

@hwdq0012
是呀，理论上是这样，但是光看前端的状态管理框架层出不穷的架势，就知道实际上是啥情况了~

为啥我一个后端起步的 9 年经验程序员，觉得前端也很复杂？尤其是 UI 交互下各数据/状态同步，搞麻了。
相反后端模块化更容易，各模块职责明确，业务逻辑也是单向的，不会有前端那种互相影响的情况。
当然，也有可能是我前端还没入门。

我一开始也是用 rules 文件，但他经常忽略我的 rules 。有另外一位兄弟建议可以 @ rules 文件来强调，或许可以试一试。但这样的话和输入一次快捷键的操作成本差不多了～

@name1991

确实，写到文件里面然后聊天框里面引用，也是一个方法～

但我还有些定制聊天规则的 prompt ，用在 chatgpt 聊天框的。所以定制为快捷键可能更便捷一点。

我还有一些 in-zh ，in-en ，in-short ，的快捷键，指定回复语言和风格的。各种快捷键可以很方便组合～

@maladaxia

## 1. 启动阶段让 AI 多想想再开始写：
You are about to work with me in an interactive coding process.
Your role is to propose solutions, ask clarifying questions, and discuss ideas collaboratively.

You may proceed to write code only after receiving explicit approval⚠️.
Act with caution and deliberation — do not rush into implementation or shift direction without strong justification.

Follow the steps below in order:
1. Understand the task: Describe your understanding of the task, highlight areas that require extra care, and consider both best practices and the specific context of this project.
2. Understand the codebase: Describe your understanding of the project by using any available methods to gather information (file structure, key configs, code, etc.).
3. Outline your approach: Present your proposed solution and implementation steps. Include key code snippets (each no more than 50 lines). Avoid diving into full implementation details.
4. Evaluate dependencies: If your approach involves new packages, explain their necessity and compare them to alternative options.
5. Request approval: If anything is unclear, ask. Do not start coding until the plan is fully confirmed.

## 2. 追问过程中让 ai 继续保持思考，让我确认再写代码：
This is the **drafting stage**. Focus on analyzing the problem, evaluating options, and outlining a clear plan.
Avoid all implementation for now. Do **not** begin coding, editing, or executing any part of the solution.

Use short code fragments (≤ 50 lines) only if necessary to support discussion or clarify ideas.
Keep the conversation at the planning level until implementation is explicitly requested.

## 3. 告诉 AI 之前的讨论方案 OK ，现在可以开始写代码了：
You are now authorized to implement the confirmed solution(s).
Write code strictly based on the previously discussed and approved solution.
Do not introduce new ideas, restructure the logic, or make assumptions beyond the agreed scope⚠️.
If you encounter uncertainties, pause and ask questions before proceeding.

## 4. 告诉 AI 我修改了代码，先读取最新的代码再开始写：
I’ve made substantial changes to the codebase.
**Before continuing any work, carefully re-read all affected code files** to fully understand the latest logic and structure.
Ensure your upcoming work is based on this updated version—failure to do so may result in conflicts, overwritten work, or critical bugs.

## 5. 让 AI 重构代码文件，模块化，不要改其它的东西
Refactor this file by breaking it down into smaller, decoupled internal modules to improve readability and maintainability.

Requirements:
1. Do not alter any existing functionality, styles, or behaviors.
2. Update documentation and comments as needed to reflect the new structure.
3. You may only edit this file. Creating or modifying any other files is strictly prohibited.

以上是我每天在用的，设置了快捷键一键输入(可以用 raycast)，不然我也不可能一个一个敲出来回复你。

我觉得 AI 写代码最大的瓶颈在于“沟通”，只要把话说清楚背景捋清楚，它总能写得比我自己又快又好。
我并不觉得我得沟通能力差，只是很多时候我懒得说/懒得打那么多字。
所以我做了两个尝试：
1. 把经常要说的提示词用快捷键输入。虽然有 cursorrules 等文件，但是它经常忽略。而我明确在聊天框说的字，它是不会忽略的；
2. 让它尽可能和我交互，多问我问题，我再简单回答。比我自己上来要铺垫很多信息要更轻松，也更精准。

好！

哈哈哈，恭喜恭喜

@radishzz
看了这位老哥的视频，挺有意思的。
而且看时间和我遇到这问题基本差不多，估计是今年 Apple 突然加紧了这方面的审查。

@LOGOSJ
海外上架简单很多，不需要备案啥的，也不会遇到这种情况。
不过欧洲那边好像对隐私条款啥的比较严格，具体没仔细研究，我直接就没上欧洲国家。
我觉得 Apple 还算好的，最难的是国内 Android 市场，还需要软著，这东西流程贼慢，两个月起步。