AI 工具指南
Codex/Deep guide

Codex Css Spacing Responsive

新手搜索“Codex 修 CSS 间距和响应式问题怎么做”时，通常不是缺一个概念解释，而是不知道准备哪些材料、按什么顺序验证、哪些风险不能碰。读完后可以按清单完成初步判断，知道下一步该问什么、测什么、记录什么，以及什么时候应该暂缓或找人复核。

What is the problem?

新手搜索“Codex 修 CSS 间距和响应式问题怎么做”时，通常不是缺一个概念解释，而是不知道准备哪些材料、按什么顺序验证、哪些风险不能碰。读完后可以按清单完成初步判断，知道下一步该问什么、测什么、记录什么，以及什么时候应该暂缓或找人复核。

Quick solution

Treat this as a Codex tutorial issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.

Read the deep guide

Detailed steps

  1. 保存原始需求、报错或客户消息，不要只保留自己理解后的版本。
  2. 标出项目平台、技术栈、预算、截止时间、权限范围和交付标准。
  3. 用本站的 Proposal 生成器或报错解释器做第一轮拆解，但不要直接复制输出。
  4. 检查是否出现平台外私下交易、免费测试、极低预算加急、敏感权限、生产数据库等风险信号。
  5. 写出 3-5 个必须向客户确认的问题。
  6. 用本地测试、截图或最小 demo 验证自己是否真的能做。

Commands or code

Thanks for sharing the details. Before I confirm the final scope, I would like to check a few points:
1. Could you share the current link, screenshots, or repository?
2. What result should be considered finished?
3. Is this a test environment or a live production project?
4. Are there any deadline or platform requirements I should know?

I will only confirm the quote after reviewing these details, so I do not promise something I cannot deliver.

Risk notes

Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.