Coding & Development prompts

Act as a senior frontend engineer and visual designer. Build a responsive landing page for [product] serving [audience], using [preferred stack]. The primary action is [conversion goal]. Start by identifying the smallest useful page structure: navigation, a clear hero, concrete benefits, a product demonstration, credible evidence where supplied, frequently asked questions and a final call to action. Create a coherent visual system with semantic color tokens, a clear typography scale and deliberate spacing. Implement real interactions for navigation, forms and expandable content. Use semantic HTML, visible keyboard focus, accessible labels and reduced-motion support. Do not invent testimonials, customer counts or awards. Include friendly loading, empty, success and error states wherever needed. Return a file structure, complete working code and exact setup commands. Finish with a short verification checklist covering mobile layout, keyboard navigation, form behavior and console errors, and state any assumptions that need product input.

Act as a careful senior software engineer.

THE TASK
Investigate a supplied bug by reconstructing expected behavior, actual behavior, relevant state, and a minimal reproduction. Rank explanations before recommending a patch.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A reproduction recipe, hypothesis table, minimal patch proposal, regression test, and explanation of the failure mechanism. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Investigate a reproducible bug by narrowing hypotheses, asking for logs, and testing likely fixes.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Investigate a reproducible bug by narrowing hypotheses, asking for logs, and testing likely fixes.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Investigate a reproducible bug by narrowing hypotheses, asking for logs, and testing likely fixes.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Investigate a reproducible bug by narrowing hypotheses, asking for logs, and testing likely fixes.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Investigate a reproducible bug by narrowing hypotheses, asking for logs, and testing likely fixes.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Review a code snippet for correctness, clarity, performance, security, and maintainability.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Review a code snippet for correctness, clarity, performance, security, and maintainability.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Review a code snippet for correctness, clarity, performance, security, and maintainability.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Review a code snippet for correctness, clarity, performance, security, and maintainability.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Review a code snippet for correctness, clarity, performance, security, and maintainability.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Recommend a simple system architecture that fits a product, user base, and developer skill level.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Recommend a simple system architecture that fits a product, user base, and developer skill level.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Recommend a simple system architecture that fits a product, user base, and developer skill level.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Recommend a simple system architecture that fits a product, user base, and developer skill level.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Recommend a simple system architecture that fits a product, user base, and developer skill level.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Design unit, integration, and edge-case tests for an existing function or feature.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Design unit, integration, and edge-case tests for an existing function or feature.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Design unit, integration, and edge-case tests for an existing function or feature.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Design unit, integration, and edge-case tests for an existing function or feature.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Design unit, integration, and edge-case tests for an existing function or feature.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Explain an API flow and produce a small client example with authentication and error handling.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Explain an API flow and produce a small client example with authentication and error handling.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Explain an API flow and produce a small client example with authentication and error handling.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Explain an API flow and produce a small client example with authentication and error handling.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Explain an API flow and produce a small client example with authentication and error handling.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Improve tangled code in manageable steps while preserving observable behavior.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Improve tangled code in manageable steps while preserving observable behavior.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Improve tangled code in manageable steps while preserving observable behavior.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Improve tangled code in manageable steps while preserving observable behavior.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Improve tangled code in manageable steps while preserving observable behavior.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Model a product domain with tables, relations, indexes, and validation considerations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Model a product domain with tables, relations, indexes, and validation considerations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Model a product domain with tables, relations, indexes, and validation considerations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Model a product domain with tables, relations, indexes, and validation considerations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Model a product domain with tables, relations, indexes, and validation considerations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Audit a user interface for keyboard use, semantics, contrast, states, and screen readers.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Audit a user interface for keyboard use, semantics, contrast, states, and screen readers.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Audit a user interface for keyboard use, semantics, contrast, states, and screen readers.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Audit a user interface for keyboard use, semantics, contrast, states, and screen readers.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Audit a user interface for keyboard use, semantics, contrast, states, and screen readers.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Diagnose slow application behavior using profiling evidence and incremental optimizations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Diagnose slow application behavior using profiling evidence and incremental optimizations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Diagnose slow application behavior using profiling evidence and incremental optimizations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Diagnose slow application behavior using profiling evidence and incremental optimizations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Diagnose slow application behavior using profiling evidence and incremental optimizations.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Create a guided map of a project explaining entry points, data flow, dependencies, and risky areas.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — STEP-BY-STEP BLUEPRINT
Start by restating the goal in one sentence and identifying the three most important constraints. Develop a step-by-step approach ordered by impact and effort. Include a concrete example tailored to the supplied inputs, a practical checklist, and the first small action to take today.

DELIVERABLE
A clear plan with numbered phases, a worked example, and a short ready-to-use checklist.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Create a guided map of a project explaining entry points, data flow, dependencies, and risky areas.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — CREATIVE IDEA LAB
Explore several genuinely different creative directions, including a conservative option, a surprising angle, and a lean low-cost alternative. Explain who each approach fits and what makes it different. Select the strongest direction and refine it with a memorable example.

DELIVERABLE
Seven distinct ideas, a comparison of the top three, one refined concept, and two experiments to validate it.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Create a guided map of a project explaining entry points, data flow, dependencies, and risky areas.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — EXPERT CRITIQUE & UPGRADE
Approach this like a candid expert reviewer. Diagnose common weak points and hidden assumptions. Prioritize problems by likely impact and ease of fixing them. Suggest precise improvements, show a before-and-after example, and note which missing facts would change your recommendation.

DELIVERABLE
An audit table, the three highest-impact fixes, an improved example, and verification questions.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Create a guided map of a project explaining entry points, data flow, dependencies, and risky areas.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — DONE-FOR-YOU TOOLKIT
Produce practical, reusable materials that someone can adapt immediately. Include a fill-in template with [placeholders], a polished filled example based only on known details, and two versions for different situations. Make each item self-contained and easy to copy.

DELIVERABLE
A copy-ready template, one fully written example, two variations, and concise customization notes.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer and pragmatic technical mentor.

MY PROJECT
I want to: Create a guided map of a project explaining entry points, data flow, dependencies, and risky areas.

CONTEXT TO USE
[Describe your specific situation here.] Include what you know about: language, framework, environment, code or error, requirements, and constraints. If essential details are missing, ask up to three targeted questions; otherwise state reasonable assumptions and move forward.

YOUR APPROACH — 7-DAY ACTION SPRINT
Turn the objective into a realistic seven-day sprint, with daily outcomes, a time-boxed task, and a definition of done. Include a lightweight tracking method, a likely obstacle for each phase, and a recovery path if one day is missed. Prefer momentum over perfection.

DELIVERABLE
A day-by-day plan, measurable milestones, a risk-and-response table, and a final review rubric.

QUALITY STANDARD
Prioritize correctness, security, maintainability, and testable examples. Be specific rather than generic. Use plain language, concrete examples, and a format I can put into practice without additional explanation.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a polished responsive landing page with a clear component structure and real interactions.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver file structure, complete working code, setup steps and focused verification instructions. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design the core entities, relationships and invariants before implementation.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver schema, example records, validation rules, migration considerations and tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a reusable accessible [component] appropriate to this application.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver component code, keyboard behavior, ARIA only where needed and usage examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design a small API that makes common actions clear and handles errors consistently.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver endpoint definitions, request/response examples, validation rules and authorization boundaries. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a disciplined debugging plan for [observed bug] in this application.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver minimal reproduction steps, likely causes, targeted instrumentation and a verified-fix checklist. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Identify probable performance bottlenecks and propose measurement-led improvements.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a profiling plan, prioritized hypotheses, implementation options and before/after metrics. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement a user-friendly form with client feedback and authoritative server validation.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver working form code, validation schema, error states and meaningful boundary cases. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement composable search, filtering and sorting for the application’s primary records.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver data-flow explanation, working code, URL-state strategy and behavior examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Choose a simple state model that separates persistent, server and transient interface state.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver state inventory, ownership decisions, example code and recovery behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Review the proposed application design for concrete security risks.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver threat model, prioritized findings, remediation examples and assumptions requiring confirmation. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Build a resilient import pipeline with useful feedback and no silent data loss.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver parser code, validation approach, duplicate handling and an import summary. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design tests around important user behavior and failure conditions.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a risk-based test matrix, representative test code and clear fixture data. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Refactor [existing code] to reduce accidental complexity while preserving observable behavior.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver a short diagnosis, revised code, migration notes and focused regression checks. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design an offline-capable workflow with explicit synchronization and conflict behavior.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver architecture sketch in prose, state transitions, storage choices and recovery scenarios. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Create a small design system with reusable tokens and semantic components.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver CSS tokens, foundational components, responsive rules and accessible interaction states. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design application error handling that helps users understand and recover.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver error taxonomy, boundary strategy, example UI copy, logging rules and retry behavior. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Implement pagination or incremental loading for a growing record collection.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver API/data strategy, working UI code, navigation behavior and performance tradeoffs. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Design authentication and authorization around clear resource ownership.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver access matrix, server checks, session behavior and failure-state examples; do not invent credentials. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Write developer documentation for setting up and changing the application safely.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver README outline, installation instructions, architecture notes and troubleshooting examples. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a recipe-planning web app with reusable ingredients, dietary tags and a weekly shopping list. Adapt the work for [audience] and [intended use]. Use these specific constraints: support keyboard navigation, clear empty states and editable quantities. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a booking dashboard for a small workshop business. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle time zones explicitly, prevent overlapping appointments and explain validation errors. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a searchable prompt library with categories, saved items and copy actions. Adapt the work for [audience] and [intended use]. Use these specific constraints: support a large local dataset, fast filtering and persistent user preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a private habit tracker with daily check-ins and weekly summaries. Adapt the work for [audience] and [intended use]. Use these specific constraints: avoid manipulative streak mechanics, preserve local dates and allow correction. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: an inventory tool for a small independent shop. Adapt the work for [audience] and [intended use]. Use these specific constraints: validate stock changes, distinguish reserved from available items and maintain a clear audit trail. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a learning platform with lessons, progress tracking and accessible quizzes. Adapt the work for [audience] and [intended use]. Use these specific constraints: save progress safely, explain feedback and support reduced-motion preferences. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a client portal for sharing project milestones and feedback. Adapt the work for [audience] and [intended use]. Use these specific constraints: treat authorization as server-side, avoid exposing private data and show clear loading states. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a portfolio builder with editable project cards and image captions. Adapt the work for [audience] and [intended use]. Use these specific constraints: maintain semantic HTML, responsive layouts and meaningful alt text. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: an expense organizer that imports and categorizes CSV records. Adapt the work for [audience] and [intended use]. Use these specific constraints: handle malformed input, preserve source data and explain duplicate detection. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a senior software engineer who favors clear architecture and maintainable code. Break a proposed feature into small reviewable implementation steps.

Creative brief: a community directory with searchable local organizations and submission review. Adapt the work for [audience] and [intended use]. Use these specific constraints: sanitize user input, define moderation status and support accessible filters. Additional requirements: [requirements].

Before producing the result, identify the main objective, the most important creative or practical choice, and any essential information missing from the brief. Ask no more than three focused questions only if you cannot make a useful result without the answers; otherwise state reasonable assumptions and continue. Make concrete choices connected to this particular brief rather than offering a generic list of tips.

Deliver acceptance criteria, dependency order, edge cases, rollout strategy and verification plan. Explain the reasoning behind the most consequential choices in a short practical note. Include one alternative direction that changes a meaningful aspect of the approach while keeping the core goal. Adapt the level of detail to [available time or budget]. Use [preferred stack] and state version assumptions. Provide runnable examples rather than pseudocode when code is requested. Cover relevant loading, empty, error and success states. Validate inputs, preserve accessibility and explain how to verify the behavior with meaningful checks. Never invent credentials or pretend code was executed.

Act as a careful senior software engineer.

THE TASK
Investigate a supplied bug by reconstructing expected behavior, actual behavior, relevant state, and a minimal reproduction. Rank explanations before recommending a patch.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A reproduction recipe, hypothesis table, minimal patch proposal, regression test, and explanation of the failure mechanism. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Investigate a supplied bug by reconstructing expected behavior, actual behavior, relevant state, and a minimal reproduction. Rank explanations before recommending a patch.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A reproduction recipe, hypothesis table, minimal patch proposal, regression test, and explanation of the failure mechanism. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Investigate a supplied bug by reconstructing expected behavior, actual behavior, relevant state, and a minimal reproduction. Rank explanations before recommending a patch.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A reproduction recipe, hypothesis table, minimal patch proposal, regression test, and explanation of the failure mechanism. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Investigate a supplied bug by reconstructing expected behavior, actual behavior, relevant state, and a minimal reproduction. Rank explanations before recommending a patch.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A reproduction recipe, hypothesis table, minimal patch proposal, regression test, and explanation of the failure mechanism. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Investigate a supplied bug by reconstructing expected behavior, actual behavior, relevant state, and a minimal reproduction. Rank explanations before recommending a patch.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A reproduction recipe, hypothesis table, minimal patch proposal, regression test, and explanation of the failure mechanism. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Identify important boundaries in a function or service: empty inputs, type conversion, authorization, limits, retries, and failure states. Select tests by risk rather than mirroring implementation.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A risk-based test plan, representative tests in the supplied framework, and a note on assumptions or missing setup. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Identify important boundaries in a function or service: empty inputs, type conversion, authorization, limits, retries, and failure states. Select tests by risk rather than mirroring implementation.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A risk-based test plan, representative tests in the supplied framework, and a note on assumptions or missing setup. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Identify important boundaries in a function or service: empty inputs, type conversion, authorization, limits, retries, and failure states. Select tests by risk rather than mirroring implementation.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A risk-based test plan, representative tests in the supplied framework, and a note on assumptions or missing setup. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Identify important boundaries in a function or service: empty inputs, type conversion, authorization, limits, retries, and failure states. Select tests by risk rather than mirroring implementation.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A risk-based test plan, representative tests in the supplied framework, and a note on assumptions or missing setup. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Identify important boundaries in a function or service: empty inputs, type conversion, authorization, limits, retries, and failure states. Select tests by risk rather than mirroring implementation.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A risk-based test plan, representative tests in the supplied framework, and a note on assumptions or missing setup. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Identify important boundaries in a function or service: empty inputs, type conversion, authorization, limits, retries, and failure states. Select tests by risk rather than mirroring implementation.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A risk-based test plan, representative tests in the supplied framework, and a note on assumptions or missing setup. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Improve a supplied module by identifying mixed responsibilities and hidden dependencies. Preserve observable behavior and explain a sequence of small changes that remains easy to review.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A responsibility map, staged refactor, updated code, and tests that protect behavior during each stage. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Improve a supplied module by identifying mixed responsibilities and hidden dependencies. Preserve observable behavior and explain a sequence of small changes that remains easy to review.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A responsibility map, staged refactor, updated code, and tests that protect behavior during each stage. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Improve a supplied module by identifying mixed responsibilities and hidden dependencies. Preserve observable behavior and explain a sequence of small changes that remains easy to review.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A responsibility map, staged refactor, updated code, and tests that protect behavior during each stage. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Improve a supplied module by identifying mixed responsibilities and hidden dependencies. Preserve observable behavior and explain a sequence of small changes that remains easy to review.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A responsibility map, staged refactor, updated code, and tests that protect behavior during each stage. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Improve a supplied module by identifying mixed responsibilities and hidden dependencies. Preserve observable behavior and explain a sequence of small changes that remains easy to review.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A responsibility map, staged refactor, updated code, and tests that protect behavior during each stage. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Improve a supplied module by identifying mixed responsibilities and hidden dependencies. Preserve observable behavior and explain a sequence of small changes that remains easy to review.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A responsibility map, staged refactor, updated code, and tests that protect behavior during each stage. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design an API around the actual consumer workflow, including inputs, outputs, validation, permissions, errors, and retry behavior. Avoid adding endpoints without a demonstrated use case.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
An endpoint contract, example requests and responses, error catalog, and compatibility notes for future changes. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design an API around the actual consumer workflow, including inputs, outputs, validation, permissions, errors, and retry behavior. Avoid adding endpoints without a demonstrated use case.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
An endpoint contract, example requests and responses, error catalog, and compatibility notes for future changes. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design an API around the actual consumer workflow, including inputs, outputs, validation, permissions, errors, and retry behavior. Avoid adding endpoints without a demonstrated use case.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
An endpoint contract, example requests and responses, error catalog, and compatibility notes for future changes. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design an API around the actual consumer workflow, including inputs, outputs, validation, permissions, errors, and retry behavior. Avoid adding endpoints without a demonstrated use case.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
An endpoint contract, example requests and responses, error catalog, and compatibility notes for future changes. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design an API around the actual consumer workflow, including inputs, outputs, validation, permissions, errors, and retry behavior. Avoid adding endpoints without a demonstrated use case.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
An endpoint contract, example requests and responses, error catalog, and compatibility notes for future changes. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design an API around the actual consumer workflow, including inputs, outputs, validation, permissions, errors, and retry behavior. Avoid adding endpoints without a demonstrated use case.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
An endpoint contract, example requests and responses, error catalog, and compatibility notes for future changes. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Analyze a slow request or operation using the supplied measurements. Separate network, database, CPU, serialization, and waiting time before recommending an optimization.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A latency breakdown, measurement plan, prioritized changes, and a benchmark procedure with representative data and limits. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Analyze a slow request or operation using the supplied measurements. Separate network, database, CPU, serialization, and waiting time before recommending an optimization.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A latency breakdown, measurement plan, prioritized changes, and a benchmark procedure with representative data and limits. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Analyze a slow request or operation using the supplied measurements. Separate network, database, CPU, serialization, and waiting time before recommending an optimization.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A latency breakdown, measurement plan, prioritized changes, and a benchmark procedure with representative data and limits. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Analyze a slow request or operation using the supplied measurements. Separate network, database, CPU, serialization, and waiting time before recommending an optimization.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A latency breakdown, measurement plan, prioritized changes, and a benchmark procedure with representative data and limits. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Analyze a slow request or operation using the supplied measurements. Separate network, database, CPU, serialization, and waiting time before recommending an optimization.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A latency breakdown, measurement plan, prioritized changes, and a benchmark procedure with representative data and limits. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Analyze a slow request or operation using the supplied measurements. Separate network, database, CPU, serialization, and waiting time before recommending an optimization.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A latency breakdown, measurement plan, prioritized changes, and a benchmark procedure with representative data and limits. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Plan a data or schema migration that accounts for existing users, partial completion, rollback, and verification. Distinguish steps safe to repeat from irreversible transformations.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A migration sequence, idempotency notes, verification queries, rollback criteria, and operational checkpoints. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Plan a data or schema migration that accounts for existing users, partial completion, rollback, and verification. Distinguish steps safe to repeat from irreversible transformations.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A migration sequence, idempotency notes, verification queries, rollback criteria, and operational checkpoints. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Plan a data or schema migration that accounts for existing users, partial completion, rollback, and verification. Distinguish steps safe to repeat from irreversible transformations.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A migration sequence, idempotency notes, verification queries, rollback criteria, and operational checkpoints. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Plan a data or schema migration that accounts for existing users, partial completion, rollback, and verification. Distinguish steps safe to repeat from irreversible transformations.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A migration sequence, idempotency notes, verification queries, rollback criteria, and operational checkpoints. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Plan a data or schema migration that accounts for existing users, partial completion, rollback, and verification. Distinguish steps safe to repeat from irreversible transformations.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A migration sequence, idempotency notes, verification queries, rollback criteria, and operational checkpoints. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Plan a data or schema migration that accounts for existing users, partial completion, rollback, and verification. Distinguish steps safe to repeat from irreversible transformations.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A migration sequence, idempotency notes, verification queries, rollback criteria, and operational checkpoints. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Implement an interactive component with clear semantics, keyboard behavior, focus handling, and useful errors. Account for loading and empty states rather than only the successful interaction.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
Component code, interaction-state table, accessibility notes, and a focused manual and automated verification checklist. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Implement an interactive component with clear semantics, keyboard behavior, focus handling, and useful errors. Account for loading and empty states rather than only the successful interaction.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
Component code, interaction-state table, accessibility notes, and a focused manual and automated verification checklist. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Implement an interactive component with clear semantics, keyboard behavior, focus handling, and useful errors. Account for loading and empty states rather than only the successful interaction.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
Component code, interaction-state table, accessibility notes, and a focused manual and automated verification checklist. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Implement an interactive component with clear semantics, keyboard behavior, focus handling, and useful errors. Account for loading and empty states rather than only the successful interaction.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
Component code, interaction-state table, accessibility notes, and a focused manual and automated verification checklist. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Implement an interactive component with clear semantics, keyboard behavior, focus handling, and useful errors. Account for loading and empty states rather than only the successful interaction.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
Component code, interaction-state table, accessibility notes, and a focused manual and automated verification checklist. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Implement an interactive component with clear semantics, keyboard behavior, focus handling, and useful errors. Account for loading and empty states rather than only the successful interaction.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
Component code, interaction-state table, accessibility notes, and a focused manual and automated verification checklist. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Review a workflow for missing or inconsistent authorization checks. Follow data from user input to the protected action and avoid relying on client-side controls for enforcement.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A threat-oriented data-flow review, server-side checks, negative test cases, and a list of assumptions requiring confirmation. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Review a workflow for missing or inconsistent authorization checks. Follow data from user input to the protected action and avoid relying on client-side controls for enforcement.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A threat-oriented data-flow review, server-side checks, negative test cases, and a list of assumptions requiring confirmation. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Review a workflow for missing or inconsistent authorization checks. Follow data from user input to the protected action and avoid relying on client-side controls for enforcement.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A threat-oriented data-flow review, server-side checks, negative test cases, and a list of assumptions requiring confirmation. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Review a workflow for missing or inconsistent authorization checks. Follow data from user input to the protected action and avoid relying on client-side controls for enforcement.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A threat-oriented data-flow review, server-side checks, negative test cases, and a list of assumptions requiring confirmation. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Review a workflow for missing or inconsistent authorization checks. Follow data from user input to the protected action and avoid relying on client-side controls for enforcement.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A threat-oriented data-flow review, server-side checks, negative test cases, and a list of assumptions requiring confirmation. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Review a workflow for missing or inconsistent authorization checks. Follow data from user input to the protected action and avoid relying on client-side controls for enforcement.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A threat-oriented data-flow review, server-side checks, negative test cases, and a list of assumptions requiring confirmation. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design a background task for retries, partial progress, duplicate delivery, cancellation, and observability. Choose safe behavior when the worker stops between external side effects.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A job state machine, idempotency strategy, pseudocode or implementation, and failure-injection tests. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design a background task for retries, partial progress, duplicate delivery, cancellation, and observability. Choose safe behavior when the worker stops between external side effects.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A job state machine, idempotency strategy, pseudocode or implementation, and failure-injection tests. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design a background task for retries, partial progress, duplicate delivery, cancellation, and observability. Choose safe behavior when the worker stops between external side effects.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A job state machine, idempotency strategy, pseudocode or implementation, and failure-injection tests. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design a background task for retries, partial progress, duplicate delivery, cancellation, and observability. Choose safe behavior when the worker stops between external side effects.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A job state machine, idempotency strategy, pseudocode or implementation, and failure-injection tests. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design a background task for retries, partial progress, duplicate delivery, cancellation, and observability. Choose safe behavior when the worker stops between external side effects.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A job state machine, idempotency strategy, pseudocode or implementation, and failure-injection tests. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Design a background task for retries, partial progress, duplicate delivery, cancellation, and observability. Choose safe behavior when the worker stops between external side effects.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A job state machine, idempotency strategy, pseudocode or implementation, and failure-injection tests. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Turn a set of changes into a focused review package by stating the user-visible problem, the implementation decision, and the validation evidence. Identify tradeoffs without narrating every editing step.

THE SETTING — A SMALL WEB APPLICATION
Assume a maintainable application with a modest user base and a small engineering team. Prefer clear standard-library or framework patterns over unnecessary infrastructure.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Begin with the central decision and the supplied constraints. Work through the task in a clear sequence. Show one concrete example before giving the reusable final result. Explain any important dependency that changes the order of work.

WHAT TO DELIVER
A PR description, reviewer guide, test evidence summary, and a list of concrete unresolved questions. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Turn a set of changes into a focused review package by stating the user-visible problem, the implementation decision, and the validation evidence. Identify tradeoffs without narrating every editing step.

THE SETTING — AN INHERITED CODEBASE
Assume incomplete documentation and existing users. Preserve behavior until evidence supports change and show how to inspect relevant assumptions before editing.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Develop three genuinely different directions before selecting one to refine. Explain the tradeoff behind the selection and retain one unexpected but practical alternative. Make the final result distinctive without adding complexity that the situation cannot support.

WHAT TO DELIVER
A PR description, reviewer guide, test evidence summary, and a list of concrete unresolved questions. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Turn a set of changes into a focused review package by stating the user-visible problem, the implementation decision, and the validation evidence. Identify tradeoffs without narrating every editing step.

THE SETTING — A PUBLIC-FACING SERVICE
Account for untrusted inputs, concurrent requests, and observable error behavior. Avoid exposing internal details and include realistic load or abuse boundaries.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Produce a ready-to-use artifact that can be adapted without reconstructing your reasoning. Include a short worked example and clearly mark the fields the user should replace. Keep essential instructions next to the part of the artifact they govern.

WHAT TO DELIVER
A PR description, reviewer guide, test evidence summary, and a list of concrete unresolved questions. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Turn a set of changes into a focused review package by stating the user-visible problem, the implementation decision, and the validation evidence. Identify tradeoffs without narrating every editing step.

THE SETTING — A DATA-HEAVY WORKFLOW
Assume imperfect records, large batches, and occasional partial failure. Pay attention to data validation, memory use, checkpointing, and repeatability.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Examine the difficult edge cases and hidden assumptions before finalizing the output. Compare a conventional approach with a credible alternative. Include an explicit review of likely failure modes and explain which evidence would change your recommendation.

WHAT TO DELIVER
A PR description, reviewer guide, test evidence summary, and a list of concrete unresolved questions. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Turn a set of changes into a focused review package by stating the user-visible problem, the implementation decision, and the validation evidence. Identify tradeoffs without narrating every editing step.

THE SETTING — A MOBILE WEB EXPERIENCE
Assume touch, narrow screens, variable network quality, and interrupted sessions. Make state recoverable and avoid relying on hover or constant connectivity.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Provide the requested core deliverable, then organize practical follow-through into a seven-day plan. Give each day a clear action and completion signal, account for preparation and review, and offer a shorter fallback if the available time is limited.

WHAT TO DELIVER
A PR description, reviewer guide, test evidence summary, and a list of concrete unresolved questions. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.

Act as a careful senior software engineer.

THE TASK
Turn a set of changes into a focused review package by stating the user-visible problem, the implementation decision, and the validation evidence. Identify tradeoffs without narrating every editing step.

THE SETTING — A TEACHING-ORIENTED IMPLEMENTATION
Assume the reader wants to understand the engineering choices. Keep the implementation production-minded but explain the key decisions and realistic limitations plainly.

MY DETAILS
Use [my specific goal], [the audience or people involved], [source material or starting point], [available time and resources], and [non-negotiable constraints]. Treat these as editable inputs. If an essential detail is missing, ask one focused question; otherwise state reasonable assumptions and proceed.

HOW TO WORK
Create a strong first version and then critique it against the stated goal. Revise the weakest part rather than rewriting everything. Show the key before-and-after change and finish with a short checklist the user can apply independently.

WHAT TO DELIVER
A PR description, reviewer guide, test evidence summary, and a list of concrete unresolved questions. Tailor every section to the setting above and the details I supply. Make the final artifact usable, not just a list of general suggestions.

QUALITY CHECK
Use the supplied language and framework versions. Do not invent APIs or claim code was run. Handle errors deliberately, protect secrets, and separate verified facts from hypotheses. Prefer the smallest change that satisfies the task. Close with the smallest useful next step and identify one assumption I should verify before relying on the result.