Understand the problem, then generate three app ideas from it. For each idea, include a name, a concept summary, core features, who it helps, and one hypothesis to check with real people before treating demand as proven. Mark each idea as untested. Write for a solo founder.

Here's the idea: [IDE_APLIKASI]

Understand the problem, then generate three app ideas from it. For each idea, include a name, a concept summary, core features, who it helps, and one hypothesis to check with real people before treating demand as proven. Mark each idea as untested. Write for a solo founder.

Here's the idea: A QR code generator for a presenter who needs to share a URL on a slide or a web page.

I choose this idea from our previous discussion: [IDE]. Help me narrow the first version to one useful end-to-end user journey.

Describe the target user, their problem, the steps from opening the page to getting a result, at most three essential features, and the features to postpone.
Use HTML, CSS, and JavaScript that run in the browser. Do not add accounts, a database, a back end, or payments.
Give me five acceptance criteria that I can check myself in a browser. Explain technical terms in plain language.
If this idea needs a server or secret data, explain why and suggest a smaller first version.

I choose this idea from our previous discussion: SlideQR: a presenter enters a URL, sees a high-contrast QR code that is easy to scan, and downloads a PNG for a presentation slide. Help me narrow the first version to one useful end-to-end user journey.

Describe the target user, their problem, the steps from opening the page to getting a result, at most three essential features, and the features to postpone.
Use HTML, CSS, and JavaScript that run in the browser. Do not add accounts, a database, a back end, or payments.
Give me five acceptance criteria that I can check myself in a browser. Explain technical terms in plain language.
If this idea needs a server or secret data, explain why and suggest a smaller first version.

Turn the decisions we agreed on into the full content of PROJECT.md for [PROJECT NAME], the project brief that my coding agent will read.

Include these sections: goal, target user, main user journey, essential features, out of scope, technology, and a checklist of acceptance criteria.
Cover the initial state, invalid input, successful result, and mobile layout.
Use HTML, CSS, and JavaScript in the browser so the finished files can be hosted as a static website. If you propose a library, explain its purpose and how its required assets will be included in the project.
Do not invent decisions we have not made. List unresolved points as questions.
Return the complete Markdown in one code block so I can save it. Do not implement the app yet.

Turn the decisions we agreed on into the full content of PROJECT.md for SlideQR, the project brief that my coding agent will read.

Include these sections: goal, target user, main user journey, essential features, out of scope, technology, and a checklist of acceptance criteria.
Cover the initial state, invalid input, successful result, and mobile layout.
Use HTML, CSS, and JavaScript in the browser so the finished files can be hosted as a static website. If you propose a library, explain its purpose and how its required assets will be included in the project.
Do not invent decisions we have not made. List unresolved points as questions.
Return the complete Markdown in one code block so I can save it. Do not implement the app yet.

Using the PROJECT.md we agreed on, design a single page for [PROJECT NAME].
List the sections from top to bottom, including the heading text, input labels, primary button, result area, and error messages.
Describe the journey from the initial state to entering information, then either a successful result or a clear error.
Make the same journey usable on a phone. Give every input a visible label, not placeholder text alone.
Present the design in plain text. Do not add features or write code yet.

Using the PROJECT.md we agreed on, design a single page for SlideQR.
List the sections from top to bottom, including the heading text, input labels, primary button, result area, and error messages.
Describe the journey from the initial state to entering information, then either a successful result or a clear error.
Make the same journey usable on a phone. Give every input a visible label, not placeholder text alone.
Present the design in plain text. Do not add features or write code yet.

The visual direction I want is: [VISUAL DIRECTION].
Turn that into a short design guide covering colors, text sizes and hierarchy, spacing, button appearance, and mobile layout.
Prioritize readable text, sufficient contrast, visible keyboard focus, and one clear primary action.
Add the page design and visual guide to PROJECT.md without changing the agreed feature scope.
Return the complete updated PROJECT.md in one Markdown code block, not only the changed sections.

The visual direction I want is: SlideQR should feel like a clean presentation tool: white background, dark text, blue primary button, a black-and-white QR code with quiet space around it, and no decoration that interferes with scanning.
Turn that into a short design guide covering colors, text sizes and hierarchy, spacing, button appearance, and mobile layout.
Prioritize readable text, sufficient contrast, visible keyboard focus, and one clear primary action.
Add the page design and visual guide to PROJECT.md without changing the agreed feature scope.
Return the complete updated PROJECT.md in one Markdown code block, not only the changed sections.

Read PROJECT.md in this folder. I am a nontechnical beginner. Explain each action in plain English.
Build the first version of [PROJECT NAME] from the brief using HTML, CSS, and JavaScript. Implement only the essential features and one main user journey.
If a decision blocks implementation, ask a short question. Do not add accounts, a database, payments, or other services.
Save every file needed for static hosting. If a library already provides the algorithm, use it. Do not write that algorithm yourself. Explain any dependency you choose.
Run the available checks. Tell me what was and was not tested, which files you created, and how to open a local preview in my browser, including the command and address if needed.
Do not deploy yet.

Read PROJECT.md in this folder. I am a nontechnical beginner. Explain each action in plain English.
Build the first version of SlideQR from the brief using HTML, CSS, and JavaScript. Implement only the essential features and one main user journey.
If a decision blocks implementation, ask a short question. Do not add accounts, a database, payments, or other services.
Save every file needed for static hosting. If a library already provides the algorithm, use it. Do not write that algorithm yourself. Explain any dependency you choose.
Run the available checks. Tell me what was and was not tested, which files you created, and how to open a local preview in my browser, including the command and address if needed.
Do not deploy yet.

I tried the app. Here is the change I need: [CHANGE].
Inspect the related code and make the smallest change that meets this need. Preserve the other working features and the scope in PROJECT.md.
If this expands the scope, explain that before making the change.
Then run relevant checks and give me steps to verify both the change and the main user journey. State clearly what you could not verify.

I tried the app. Here is the change I need: In SlideQR, when the URL field is empty and I press Generate QR, show 'Enter a URL first' beside the field. Right now there is no clear message.
Inspect the related code and make the smallest change that meets this need. Preserve the other working features and the scope in PROJECT.md.
If this expands the scope, explain that before making the change.
Then run relevant checks and give me steps to verify both the change and the main user journey. State clearly what you could not verify.

Read PROJECT.md and the current app. Create a test checklist with columns for action, expected result, and an empty actual result.
Cover the main user journey, empty input, invalid input, repeated use, phone layout, and navigation with the Tab key.
Add this project-specific check: [PROJECT-SPECIFIC CHECK].
Run the available automated tests and report their actual results. Separate passed automated checks from manual checks that have not been done.
Do not mark a manual check as passed without trying it. Do not change code in this step.

Read PROJECT.md and the current app. Create a test checklist with columns for action, expected result, and an empty actual result.
Cover the main user journey, empty input, invalid input, repeated use, phone layout, and navigation with the Tab key.
Add this project-specific check: In SlideQR, the PNG must download, and scanning the QR in that PNG with a phone must open the correct URL, including a URL with query parameters. When the URL changes, the QR and downloaded PNG must update too.
Run the available automated tests and report their actual results. Separate passed automated checks from manual checks that have not been done.
Do not mark a manual check as passed without trying it. Do not change code in this step.

There is a problem with the app.
Steps to reproduce it: [STEPS].
What I expected: [EXPECTED RESULT].
What actually happened: [ACTUAL RESULT].

Investigate the cause using the code and this evidence. If it is not enough, ask for the single most useful piece of information. Do not guess or change many things at once.
Reproduce the issue if possible, make the smallest fix, then repeat the failing steps and check the main user journey.
Report the cause, the change, and the verification result. If you could not test it, say so clearly.

There is a problem with the app.
Steps to reproduce it: Open SlideQR, make a QR for https://example.com, change the input to https://example.org, make another QR, then download the PNG.
What I expected: The final PNG opens https://example.org.
What actually happened: Scanning the PNG still opens https://example.com. Replace this placeholder with what you observe.

Investigate the cause using the code and this evidence. If it is not enough, ask for the single most useful piece of information. Do not guess or change many things at once.
Reproduce the issue if possible, make the smallest fix, then repeat the failing steps and check the main user journey.
Report the cause, the change, and the verification result. If you could not test it, say so clearly.

Use the domainesia-hosting connection to check whether [PROJECT NAME] is ready to deploy.
Treat the step as read-only. Do not upload, change, or delete files.
Check whether the connection is active, which domains or subdomains are available, and each website's destination folder (document root).
Check whether the destination contains an existing website or files, and whether the hosting supports this static app.
Show me the possible destinations and the risk of overwriting files, then wait for me to choose the exact domain and folder.
Do not display passwords or tokens. If the connection is unavailable, explain what I need to set up. Do not claim that you connected.

Use the domainesia-hosting connection to check whether SlideQR is ready to deploy.
Treat the step as read-only. Do not upload, change, or delete files.
Check whether the connection is active, which domains or subdomains are available, and each website's destination folder (document root).
Check whether the destination contains an existing website or files, and whether the hosting supports this static app.
Show me the possible destinations and the risk of overwriting files, then wait for me to choose the exact domain and folder.
Do not display passwords or tokens. If the connection is unavailable, explain what I need to set up. Do not claim that you connected.

I choose the domain [DOMAIN] and document root [DESTINATION FOLDER] from the previous inspection.
Deploy this static app there using domainesia-hosting.
Confirm that the domain and folder match the inspected destination. If they do not match or were not verified, stop and ask me. Do not guess.
Upload only the app files and assets needed. Do not upload .env files, passwords, tokens, or private notes.
If existing files need to be overwritten, list them and explain the backup plan, then ask for approval first. Do not delete unrelated files or change DNS without approval.
After deployment, provide the public URL, a list of changes, and steps to restore the previous version. Do not call it finished until you inspect the page being served.

I choose the domain slideqr.example.com (replace with your domain from prompt 10) and document root /folder-from-prompt-10 (replace with the document root you inspected) from the previous inspection.
Deploy this static app there using domainesia-hosting.
Confirm that the domain and folder match the inspected destination. If they do not match or were not verified, stop and ask me. Do not guess.
Upload only the app files and assets needed. Do not upload .env files, passwords, tokens, or private notes.
If existing files need to be overwritten, list them and explain the backup plan, then ask for approval first. Do not delete unrelated files or change DNS without approval.
After deployment, provide the public URL, a list of changes, and steps to restore the previous version. Do not call it finished until you inspect the page being served.

Verify the app at [PUBLIC URL] against PROJECT.md.
Confirm that the correct app appears instead of the hosting provider's default page. Check its assets, main user journey, invalid input, and phone layout if tools are available.
An HTTP 200 response alone is not enough. Report which checks you actually ran, their results, and which manual checks I still need to do.
Do not change hosting configuration or code without explaining the finding and proposed fix.
After verification, help me draft a short invitation for one potential user to try it. Ask what they did and where they struggled, not whether they liked the idea. Do not send the message.

Verify the app at https://slideqr.example.com (replace with your deployed URL) against PROJECT.md.
Confirm that the correct app appears instead of the hosting provider's default page. Check its assets, main user journey, invalid input, and phone layout if tools are available.
An HTTP 200 response alone is not enough. Report which checks you actually ran, their results, and which manual checks I still need to do.
Do not change hosting configuration or code without explaining the finding and proposed fix.
After verification, help me draft a short invitation for one potential user to try it. Ask what they did and where they struggled, not whether they liked the idea. Do not send the message.