Lesson Content

Real product work combines code, data, interfaces, and operational constraints. For WordPress, Codex may inspect PHP, JavaScript, CSS, templates, hooks, capabilities, nonces, database tables, REST endpoints, and packaging rules. It should preserve WordPress conventions, sanitize input, escape output, check permissions, and avoid direct edits to core or third-party packages.

Break work into increments: inspect current architecture; document baseline behavior; implement one feature; add automated and manual tests; perform security and accessibility checks; then package only when explicitly requested. Maintain version numbers and migration paths deliberately.

For mobile or desktop apps, identify platform tooling, signing boundaries, dependency management, tests, and build artifacts. Codex may create or edit source code, but access to local GUI tools, certificates, devices, or app-store accounts depends on the environment. Never claim an install or release succeeded without observable evidence.

The best product task ends with a release dossier: changed behavior, files, tests, known limitations, upgrade notes, rollback, and QA checklist.