As of 13 August 2026, AI can write JavaScript for your business website.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the website editor or code repository and copy the relevant page HTML, CSS and existing JavaScript into a separate working document.
   2. Write down the feature's trigger, expected result, validation rules, API details and the browsers and devices the site must support.
   3. Remove passwords, API keys, customer details and other private data, then paste the remaining code and requirements into the prompt.
   4. Ask the model to produce the JavaScript, exact installation instructions and the test checklist without inventing missing platform or API details.
   5. Apply the code in a staging site or local copy rather than the live website, and run the checklist with valid, empty, invalid, repeated and slow-network inputs.
   6. Open the browser developer tools, check the Console and Network panels for errors or unexpected requests, and compare the behaviour with the stated business rules.
   7. Ask a developer or experienced colleague to inspect authentication, personal-data handling, API permissions and failure behaviour before publishing the change.
   8. Publish only after backing up the current site, confirming the feature works on the required mobile and desktop browsers, and recording how to remove or roll back the code.

   Prompt

   Write the JavaScript needed for this business website feature.
   
   Goal: [describe exactly what the visitor should be able to do]
   Website platform: [for example WordPress, Shopify, Webflow or custom HTML]
   Where the code will run: [page URL or page type]
   Existing HTML: [paste the relevant HTML]
   Existing CSS: [paste relevant CSS]
   Existing JavaScript: [paste relevant JavaScript]
   External services or APIs: [name them, or say none]
   Input and output data: [describe the fields, formats and expected results]
   Browser support: [list required browsers, or say modern desktop and mobile browsers]
   Security and privacy constraints: [describe personal data, payments, authentication or other sensitive areas, or say none]
   
   Return:
   1. The complete JavaScript, clearly separated into files or script blocks where needed.
   2. The exact HTML or CSS changes required.
   3. Exact instructions for where to place each part on this platform.
   4. A short explanation of the main logic and assumptions.
   5. A test checklist covering normal use, empty and invalid inputs, repeated clicks, slow network responses, mobile layout and API failures.
   6. A list of anything you cannot determine from the information provided.
   
   Do not invent API endpoints, credentials, fields, platform features or business rules. Do not include real secrets. If this feature handles payments, authentication or personal data, mark the security-sensitive parts and explain what a developer must review before launch.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.