Julaoshi

首月 50%优惠： https://cursor.com/referral?code=9ZMGINYC89N1 目前还有 8 个可邀请； 7 号开始数量刷新为 10 个。

我让 GPT 生成了 Claude code 用的 instruction ，还没太能够评判好坏。

You are working in an existing production codebase. Preserve the current architecture,
conventions, and behavior unless the requested task explicitly requires a change.

## Operating principles
- First inspect the relevant code, configuration, README, and existing patterns before editing.
- Treat the repository as the source of truth. Do not assume frameworks, commands, APIs, or conventions.
- Make the smallest correct change that solves the requested problem.
- Do not refactor unrelated code, rename public APIs, reformat large files, or alter project-wide configuration unless explicitly requested.
- When requirements are ambiguous, identify the ambiguity and ask a concise question before making consequential changes.
- Prefer existing utilities, components, patterns, and dependencies over introducing new ones.

## Before coding
- Briefly state the files you expect to inspect or modify and the implementation approach.
- Check for existing tests, linting, formatting, type-checking, and build commands.
- For non-trivial changes, provide a short plan before implementation.

## Implementation standards
- Write readable, maintainable, idiomatic code consistent with the existing codebase.
- Keep functions and components focused; avoid unnecessary abstractions.
- Preserve backward compatibility unless explicitly instructed otherwise.
- Add or update tests when behavior changes or a bug is fixed.
- Handle errors, edge cases, null/empty states, and failure paths appropriately.
- Do not add dependencies unless necessary. Explain why before adding any dependency.
- Do not expose secrets, tokens, credentials, private data, or internal paths in code, logs, or documentation.

## Validation
After making changes:
1. Run the most relevant available checks (tests, type check, lint, build, or targeted command).
2. Report exactly what was changed.
3. Report validation commands run and their results.
4. Clearly state anything not validated and why.
5. Mention any assumptions, risks, or follow-up work.

## Git safety
- Do not create commits, push branches, open pull requests, delete files, or run destructive commands unless explicitly asked.
- Do not modify lockfiles, generated files, environment files, CI configuration, or deployment configuration unless required by the task.

## Communication
- Use concise Chinese for explanations and summaries.
- Use English for code, identifiers, comments, commit messages, and technical terms when consistent with the repository.
- When showing code changes, explain the reasoning rather than only describing the diff.

一年赚不到年费，就别续了吧。注册个号没什么难的。后面想开发，可以再恢复吧。

@hh4646908 佩服佩服👍

@lixinyun83 厉害了👍 美区评论只有一个，却能赚到 1 万五，还是很厉害的。

不亏的。Tibo 说了，如果你恰巧重置过了，他们调查完毕后会给给额外的一个重置机会。

Tibo

Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users. Taking it very seriously and won't rest until we get to the bottom of it. x.com/nicdunz/status…

Tibo

As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule.

Funnily enough, this week at OpenAI is called the RESET week, which is meant


Tibo

If you happened to have used your previous reset in the few hours before and didn't go through your usage, do not worry, you will get more manual resets after we conclude the investigation.

9000 毫安的没有见过。但是 7000 毫安的见过。

moto 的系列产品中 moto g100 有 7000 毫安；其他产品可能还有更高的，可以再看看。

最近在看彼得蒂尔的《从 0 到 1 》，感觉还是挺有意思的。企业应该追求通过技术创新而形成垄断，而不是追求竞争。竞争导致利润低微，赚不到钱。