Prompt berguna untuk Codex, siap saat Anda berbicara.

Target application: Codex
Target input: task composer

Task: Fix the bug described in my dictation.

Problem:
- Summarize the observed behavior precisely.

Expected behavior:
- State what should happen instead.

Reproduction:
- Extract the steps and relevant environment details I mention.

Constraints:
- Preserve existing behavior outside the fix.
- Do not invent missing requirements.

Before editing, inspect the relevant code and identify the likely root cause. Implement the smallest complete fix, add or update meaningful regression coverage, run the relevant checks, and report the cause, change, and verification.

Application-specific guidance:
- Let Codex inspect the workspace and reproduce the issue before editing; preserve unrelated working-tree changes.

Target application: Codex
Target input: task composer

Goal:
- Turn my description into one clear product outcome.

User flow:
- Capture the trigger, expected behavior, empty/loading/error states, and completion state.

Constraints:
- Preserve the current design system and established architecture.
- Reuse existing components and services where appropriate.
- Do not invent scope I did not request.

Inspect the current implementation first. Then implement the complete user-facing flow, verify it with the most relevant checks, and explain any material tradeoffs.

Application-specific guidance:
- Complete the whole user flow in the current project and use its established components, services and conventions.

Target application: Codex
Target input: task composer

Refactor target:
- Identify the code and problem described in my dictation.

Invariants:
- Preserve observable behavior, public interfaces, analytics names, and persisted data unless I explicitly request a change.

Desired result:
- State the simpler structure or responsibility boundary I want.

Inspect callers and tests before editing. Make the refactor in reviewable steps, remove obsolete code, run focused regression checks, and call out any behavior that could not be proven equivalent.

Application-specific guidance:
- Check every affected caller and persisted contract, then remove obsolete code only after equivalence is verified.

Target application: Codex
Target input: task composer

Behavior under test:
- Extract the contract and failure modes from my dictation.

Test cases:
- Cover the main success path, the stated edge cases, and the regression that motivated this task.

Requirements:
- Test observable behavior rather than implementation details.
- Reuse the repository's existing test style and fixtures.
- Avoid tests that merely repeat the production code.

Inspect the implementation and nearby tests, add the smallest meaningful test set, run it, and report what the tests prove.

Application-specific guidance:
- Add focused regression coverage that proves the changed behavior and run the repository's required checks.

Target application: Codex
Target input: task composer

Review the changes I describe or provide.

Focus on:
- User-visible regressions and incorrect behavior.
- Data loss, security, privacy, concurrency, and migration risks.
- Missing validation for behavior that materially changed.

Check the surrounding code and established project conventions before judging the diff. Report only actionable findings, ordered by severity, with a concrete trigger and consequence for each. If there are no findings, say so and state the remaining verification limits.

Application-specific guidance:
- Review the concrete diff and runtime consequences, prioritizing data loss, security, privacy and user-facing regressions.

Target application: Codex
Target input: task composer

Performance problem:
- Capture where the slowdown occurs, how often, and what the user experiences.

Evidence:
- Record the measurements, logs, device details, and reproduction conditions I mention.

Investigate before optimizing. Identify the dominant cost, distinguish measured facts from hypotheses, and avoid broad rewrites. Implement the highest-impact safe improvement, compare before and after with the same workload, and report the measured result and remaining bottlenecks.

Application-specific guidance:
- Collect measurements in the actual environment, fix the dominant cost and compare the same workload afterward.

Target application: Codex
Target input: task composer

Objective:
- Restate the outcome from my dictation.

Current context:
- Capture the relevant system, constraints, and decisions already made.

Produce a concrete implementation plan based on the actual codebase. Name the components that need to change, dependencies between steps, migration or rollout concerns, and the checks that prove completion. Resolve routine choices from repository evidence and list only uncertainties that truly block execution.

Application-specific guidance:
- Base the plan on repository evidence, resolve routine choices and surface only uncertainties that truly block execution.

Target application: Codex
Target input: task composer

Screen or flow:
- Identify the interface and user goal from my dictation.

Problems noticed:
- Capture the visual, interaction, responsive, and accessibility issues I mention.

Preserve the product's existing visual language. Inspect the screen at its real desktop and mobile sizes, fix hierarchy, spacing, typography, states, and interaction details, then compare the result in the running product. Avoid decorative changes that do not improve comprehension or use.

Application-specific guidance:
- Use a running preview at desktop and mobile sizes and preserve the product's existing visual language.