# Laravel Blade UI Fix Prompt

Public URL: https://amo.ng/prompts/laravel-blade-ui-fix-prompt

Summary: Use this prompt to fix Blade layout, styling, responsiveness, and frontend behavior without breaking existing Laravel logic.

Use this for: Designing and improving automation workflows with clear inputs, checks, handoffs, and next actions.

Category: Codex & Coding
Tool: Codex
Difficulty: Expert
Prompt type: coding

## Best Use Cases

1. Laravel Change Review
2. Database Migration Planning
3. Zero-Downtime Deployment Review
4. Rollback Planning
5. Regression Testing
6. Production Readiness Checks

## Prompt Body

Act as a senior Codex & Coding specialist using Codex. Your task is: [Goal or task].

Context:
- Current situation: [Current context]
- Constraints: [Constraints]
- Available materials: [Files, data, examples, URLs, logs, notes]
- Success criteria: [Definition of done]

Workflow:
1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
2. Make reasonable assumptions only when they are low risk, and label them clearly.
3. Produce the main deliverable for "Laravel Blade UI Fix Prompt" with enough detail that a skilled operator can execute it immediately.
4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
6. End with the smallest safe next action.

Output format:
- Executive summary
- Detailed plan or implementation
- Risks and mitigations
- Verification checklist
- Next action

Do not give generic advice. Optimize for a production-quality coding outcome.

## Variables to Replace

1. Goal or task
2. Current context
3. Constraints
4. Files, data, or examples
5. Definition of done

## How to Use

Replace every bracketed placeholder before running. Give the model enough context to inspect assumptions, ask only blocking questions, and produce a concrete deliverable. For code prompts, include relevant files, errors, logs, and test commands.

## Example Use Case

Use this when you need a production-ready coding result in Codex & Coding, not a generic brainstorm. The expected output should include findings, implementation steps, risks, and verification checks.

## Tags

1. laravel
2. codex
3. Codex & Coding
4. blade
5. frontend

## Dates

Published: 2026-05-31
Updated: 2026-06-11