100 Advanced Codex Prompts

#001 Repo Recon

Map the product surface

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 1: Map the product surface.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#002 Repo Recon

Trace a user workflow end to end

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 2: Trace a user workflow end to end.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#003 Repo Recon

Find the likely owner files for a bug

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 3: Find the likely owner files for a bug.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#004 Repo Recon

Build a dependency and risk map

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 4: Build a dependency and risk map.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#005 Repo Recon

Compare intended behavior to implementation

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 5: Compare intended behavior to implementation.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#006 Repo Recon

Locate hidden configuration assumptions

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 6: Locate hidden configuration assumptions.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#007 Repo Recon

Summarize the test and build system

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 7: Summarize the test and build system.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#008 Repo Recon

Identify dead code and unused paths

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 8: Identify dead code and unused paths.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#009 Repo Recon

Find feature flags and rollout gates

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 9: Find feature flags and rollout gates.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#010 Repo Recon

Create a first-hour onboarding brief

Act as my senior Codex pair for understanding an unfamiliar codebase before changing it.

Task 10: Create a first-hour onboarding brief.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#011 Planning

Convert a vague request into acceptance criteria

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 11: Convert a vague request into acceptance criteria.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#012 Planning

Design a minimal change plan

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 12: Design a minimal change plan.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#013 Planning

Split a large feature into reviewable phases

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 13: Split a large feature into reviewable phases.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#014 Planning

Write a technical spec from product notes

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 14: Write a technical spec from product notes.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#015 Planning

Choose between three implementation approaches

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 15: Choose between three implementation approaches.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#016 Planning

Define done-when checks for a risky task

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 16: Define done-when checks for a risky task.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#017 Planning

Create a migration plan with rollback

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 17: Create a migration plan with rollback.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#018 Planning

Plan data model changes safely

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 18: Plan data model changes safely.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#019 Planning

Turn screenshots into build requirements

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 19: Turn screenshots into build requirements.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#020 Planning

Write a nontechnical implementation summary

Act as my senior Codex pair for turning an ambiguous request into a precise implementation plan.

Task 20: Write a nontechnical implementation summary.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#021 Architecture

Reduce duplication in a shared module

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 21: Reduce duplication in a shared module.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#022 Architecture

Extract a service boundary carefully

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 22: Extract a service boundary carefully.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#023 Architecture

Refactor a component without changing behavior

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 23: Refactor a component without changing behavior.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#024 Architecture

Simplify state management

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 24: Simplify state management.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#025 Architecture

Replace brittle glue code

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 25: Replace brittle glue code.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#026 Architecture

Design a plugin or extension point

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 26: Design a plugin or extension point.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#027 Architecture

Improve API boundaries

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 27: Improve API boundaries.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#028 Architecture

Untangle circular dependencies

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 28: Untangle circular dependencies.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#029 Architecture

Create a compatibility layer

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 29: Create a compatibility layer.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#030 Architecture

Review architecture for future maintenance

Act as my senior Codex pair for improving structure without creating unnecessary rewrites.

Task 30: Review architecture for future maintenance.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#031 Testing

Add focused unit tests

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 31: Add focused unit tests.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#032 Testing

Add integration tests for a workflow

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 32: Add integration tests for a workflow.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#033 Testing

Build a regression test from a bug report

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 33: Build a regression test from a bug report.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#034 Testing

Design a browser smoke test

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 34: Design a browser smoke test.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#035 Testing

Create fixture data for edge cases

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 35: Create fixture data for edge cases.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#036 Testing

Review flaky tests

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 36: Review flaky tests.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#037 Testing

Improve test names and coverage

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 37: Improve test names and coverage.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#038 Testing

Test failure and empty states

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 38: Test failure and empty states.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#039 Testing

Verify accessibility behavior

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 39: Verify accessibility behavior.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#040 Testing

Write a release verification checklist

Act as my senior Codex pair for proving that changes work and regressions are caught.

Task 40: Write a release verification checklist.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#041 Debugging

Reproduce a production-only bug

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 41: Reproduce a production-only bug.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#042 Debugging

Trace an exception through logs and code

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 42: Trace an exception through logs and code.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#043 Debugging

Find why a button or link does nothing

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 43: Find why a button or link does nothing.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#044 Debugging

Diagnose a slow page or API

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 44: Diagnose a slow page or API.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#045 Debugging

Debug a broken build

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 45: Debug a broken build.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#046 Debugging

Find why styles are being overridden

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 46: Find why styles are being overridden.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#047 Debugging

Investigate missing data

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 47: Investigate missing data.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#048 Debugging

Fix a timezone or date bug

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 48: Fix a timezone or date bug.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#049 Debugging

Debug a permissions problem

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 49: Debug a permissions problem.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#050 Debugging

Create a root-cause report

Act as my senior Codex pair for finding root cause with evidence before applying a fix.

Task 50: Create a root-cause report.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#051 WordPress

Audit a WordPress page before editing

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 51: Audit a WordPress page before editing.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#052 WordPress

Fix shortcode output showing as text

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 52: Fix shortcode output showing as text.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#053 WordPress

Create a page-scoped style fix

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 53: Create a page-scoped style fix.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#054 WordPress

Update content through the REST API

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 54: Update content through the REST API.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#055 WordPress

Verify internal links and PDFs

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 55: Verify internal links and PDFs.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#056 WordPress

Preserve existing live pages during an import

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 56: Preserve existing live pages during an import.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#057 WordPress

Create reusable HTML content blocks

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 57: Create reusable HTML content blocks.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#058 WordPress

Debug theme CSS conflicts

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 58: Debug theme CSS conflicts.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#059 WordPress

Prepare a safe publish checklist

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 59: Prepare a safe publish checklist.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#060 WordPress

Write a rollback note for a page update

Act as my senior Codex pair for editing and validating WordPress content safely.

Task 60: Write a rollback note for a page update.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#061 Frontend

Convert a screenshot into UI fixes

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 61: Convert a screenshot into UI fixes.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#062 Frontend

Improve color contrast

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 62: Improve color contrast.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#063 Frontend

Make a list or library easier to scan

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 63: Make a list or library easier to scan.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#064 Frontend

Add copy-to-clipboard behavior

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 64: Add copy-to-clipboard behavior.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#065 Frontend

Design mobile responsive controls

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 65: Design mobile responsive controls.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#066 Frontend

Fix layout shift and text overflow

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 66: Fix layout shift and text overflow.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#067 Frontend

Improve empty and loading states

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 67: Improve empty and loading states.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#068 Frontend

Create accessible buttons and labels

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 68: Create accessible buttons and labels.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#069 Frontend

Review typography scale

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 69: Review typography scale.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#070 Frontend

Verify visual quality after deployment

Act as my senior Codex pair for shipping usable, polished interface changes.

Task 70: Verify visual quality after deployment.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#071 Release

Prepare a release branch

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 71: Prepare a release branch.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#072 Release

Write a high-signal PR description

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 72: Write a high-signal PR description.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#073 Release

Review changed files for accidental edits

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 73: Review changed files for accidental edits.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#074 Release

Create deployment evidence

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 74: Create deployment evidence.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#075 Release

Verify cache and CDN behavior

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 75: Verify cache and CDN behavior.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#076 Release

Plan a rollback

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 76: Plan a rollback.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#077 Release

Check production links after publish

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 77: Check production links after publish.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#078 Release

Write release notes for nontechnical stakeholders

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 78: Write release notes for nontechnical stakeholders.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#079 Release

Triage post-release issues

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 79: Triage post-release issues.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#080 Release

Close the loop with a completion report

Act as my senior Codex pair for moving work from local change to live site with proof.

Task 80: Close the loop with a completion report.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#081 Automation

Create a one-off migration script

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 81: Create a one-off migration script.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#082 Automation

Turn a manual checklist into a script

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 82: Turn a manual checklist into a script.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#083 Automation

Validate CSV or JSON input before import

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 83: Validate CSV or JSON input before import.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#084 Automation

Generate content from structured data

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 84: Generate content from structured data.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#085 Automation

Add idempotency to an updater

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 85: Add idempotency to an updater.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#086 Automation

Write a cleanup script with dry-run mode

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 86: Write a cleanup script with dry-run mode.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#087 Automation

Create evidence files after automation

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 87: Create evidence files after automation.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#088 Automation

Automate link checking

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 88: Automate link checking.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#089 Automation

Build a local QA command

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 89: Build a local QA command.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#090 Automation

Document an operator workflow

Act as my senior Codex pair for building scripts and repeatable workflows.

Task 90: Document an operator workflow.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#091 Security Review

Review a change for secret exposure

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 91: Review a change for secret exposure.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#092 Security Review

Check input validation and output escaping

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 92: Check input validation and output escaping.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#093 Security Review

Review auth and permissions behavior

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 93: Review auth and permissions behavior.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#094 Security Review

Assess third-party dependency risk

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 94: Assess third-party dependency risk.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#095 Security Review

Harden file upload handling

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 95: Harden file upload handling.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#096 Security Review

Review admin-only workflows

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 96: Review admin-only workflows.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#097 Security Review

Create a safe logging plan

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 97: Create a safe logging plan.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#098 Security Review

Check clipboard and browser APIs

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 98: Check clipboard and browser APIs.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#099 Security Review

Audit public pages for accidental private data

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 99: Audit public pages for accidental private data.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.

#100 Security Review

Write a security-minded code review

Act as my senior Codex pair for making changes safely without exposing data or creating risk.

Task 100: Write a security-minded code review.

Start by inspecting the repository, page, or files that matter most. Do not guess when you can verify. Then give me:
1. What you found, in plain English.
2. The smallest safe implementation plan.
3. The exact files, pages, or commands you expect to touch.
4. The risks or edge cases I should know about.
5. The verification steps you will run before calling it done.

If the request is ambiguous, make one reasonable assumption, state it clearly, and continue. Keep the final result practical, reversible, and easy for a nontechnical owner to review.