Minimum Scopes for Third-Party Access
Added 2026-10
Minimum Scopes for Third-Party Access — Chinese original prompt
我们的开放平台目前只有 [权限粒度]，接入方一授权就拿走全部数据。请按功能把权限拆成更细的范围，规定每个接口需要哪个范围，并处理用户拒绝部分授权的情况。输出：范围划分表、接口与范围的对应关系、拒绝授权时的接口行为、以及已上线接入方的迁移安排。
Site original
Chinese original
Example
Sample input
开放平台现在只有读写一档权限，接入方一授权就拿走全部数据，帮我拆成更细的范围。
The output should include
- 按功能拆细范围并给划分表
- 接口与范围的对应关系列清
- 用户拒绝部分授权时的接口行为
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[权限粒度]
How to use
拆分范围会让老接入方报错，先统计它们实际调用的接口再分批收紧。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.