Guide
Codex prompt pack examples for coding agents
A Codex prompt pack should be short enough to paste, but specific enough to change agent behavior. The goal is not a long system prompt. The goal is a focused operating mode for one task.
Frontend pack
Use frontend design, accessibility pass, component audit, and mobile UI QA. Ask the agent to inspect the existing design system, make scoped UI changes, check text fit on mobile, and verify the result with screenshots when possible.
This pack is useful for landing pages, dashboards, settings pages, and catalog interfaces where a generic component layout would look cheap.
Testing pack
Use webapp testing, Playwright tests, bug reproduction, and form validation QA. Ask the agent to identify critical user flows, create or run browser checks, capture failures, and report what is still untested.
This is the pack to use before launch or after a UI refactor. It catches the obvious product bugs that unit tests often miss.
Security pack
Use security best practices, secrets check, auth flow review, dependency review, and prompt injection lab. Ask for findings first, concrete fixes second, and no unrelated rewrites.
Security prompts should be direct. They should not ask for broad theory. They should ask for code paths, trust boundaries, validation, permissions, secrets, external calls, and rollback notes.