Codex Separate Page, Pagination, and API Responsibilities
Map orchestration, transport, domain rules, and rendering to modules with clear reasons to change.
中文Install in Codex
Use a local front-end project with the page, API call sites, and existing tests.
- Copy the pinned `.codex/skills/module-boundary-guard/` directory into `.agents/skills/module-boundary-guard/` in the project.
- Point Codex at the current page and ask it to map each responsibility to its file and function first.
Example task
Review a local `OrdersPage` that builds requests, owns pagination, and renders rows. Propose boundaries and list behavior to preserve.What to check
The plan places page wiring, requests, paging state, and presentation clearly, with tests for loading and error feedback.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does separation always require a new abstraction layer?
Use the existing architecture and reasons to change. Keep the current composition when boundaries are already clear and the code is small.