An AI prompt library for the next thing you’re building. Search built-in tasks and approved community contributions. Find your next change and copy clear instructions into your coding assistant.
102 practical tasks
Browse free · Copy freelyHelp visitors understand a chart without interpreting every data point. Show the starting price, ending price, dollar change, and percentage change for the selected location and time period.
Tested with: ChatGPT · Astra · High
Setup: see the contributor’s requirements before using.
Prevent users from accidentally losing changes when they navigate away from a form they haven’t saved or submitted.
Tested with: Chat GPT · Astra · High
Setup: see the contributor’s requirements before using.
Give your pages a different mood with one clear color choice.
Change the main website background to warm ivory #F5F2EB. Keep cards white.
Carry your color palette through the parts visitors interact with.
Primary: forest green #285D49. Accent: pale mint #DDEBDF.
Make headings and body text feel like they belong together.
Use a clean system sans-serif. Make headings bolder and body text at least 16px.
Make the next action easier to spot.
Make primary buttons dark green with white text and gently rounded corners.
Give visitors a comfortable alternate color theme.
Add a light/dark toggle in the header; default to the system preference.
Make repeated items easier to scan.
Use thin borders, 16px corners, a subtle hover, and consistent padding.
Give your layout a calmer, more intentional rhythm.
Use consistent section spacing and reduce the gap below the hero on mobile.
Help readers recognize what they can click.
Underline links in article text and use the brand green.
Bring scattered visual details into one style.
Use consistent 20px outline icons throughout the navigation and buttons.
Make text more comfortable to read on wide screens.
Limit article text to about 70 characters per line while keeping the hero wider.
Make the top of your website clearer and more useful.
Keep the logo on the left, add Features and Pricing links, and put Get started on the right.
Keep navigation available as visitors scroll.
Keep the header visible at the top with a subtle border when scrolling.
Make navigation usable on smaller screens.
Collapse navigation into a menu button below 768px.
Group related destinations without overcrowding the header.
Add a Resources menu containing Guides, Templates, and FAQ using their existing routes.
Show visitors where they are in the site.
Highlight the current navigation item and underline it.
Help readers move back through a deeper site.
Add breadcrumbs above article titles: Home, Guides, current article.
Put useful links and business details within easy reach.
Add About, Contact, and Privacy links using the existing pages.
Make a long page easier to navigate.
Show a small back-to-top button after scrolling one screen.
Help readers jump straight to the answer they need.
Add a linked table of contents below the introduction.
Make existing site search easier to find.
Add a search button to the header that opens the existing search interface.
Tell visitors what your product does in fewer words.
Use: Build your first app with a little help from AI.
Give the primary button a clear purpose.
Change the hero button to Explore the prompts and link it to the prompt library.
Make the first image match what you offer.
Use my supplied dashboard screenshot as the hero image.
Answer common questions without overwhelming the page.
Add these questions and my supplied answers below the pricing section.
Make actual plan differences easier to compare.
Create three cards using the plan names, prices, and features I provide.
Give readers a quick overview of the useful parts.
Turn my six supplied features into a clean two-column grid.
Make genuine customer feedback easier to read.
Add the three customer quotes and attribution details I provide.
Help visitors understand who is behind the project.
Add a short founder bio using the facts and photo I supply.
Give visitors a clear way to reach you.
Add a contact section using my business email and existing contact form.
Put a timely update where people will see it.
Add a dismissible banner saying New beginner guides are here with a link to Guides.
Keep the page within the width of the phone.
The homepage scrolls sideways at 390px wide. Find and fix the element causing it.
Help people read without zooming.
Improve paragraph and form text sizes on mobile without making desktop text larger.
Turn a desktop layout into a clear vertical flow.
Stack the hero text above its image below the tablet breakpoint.
Reduce missed taps on phones.
Increase the mobile navigation and action-button touch areas.
Keep the page title from hiding under navigation.
The page heading is hidden behind the header on mobile.
Keep pictures from stretching or breaking the layout.
Make article images scale to their containers without distortion.
Keep floating actions from covering important content.
Move the floating action button so it does not cover the mobile form submit button.
Keep detailed comparisons usable on small screens.
Make the pricing comparison table horizontally scroll inside its own container.
Keep controls clear of device edges and cutouts.
Add safe-area spacing to the fixed bottom navigation.
Improve the layout between phone and desktop widths.
At around 900px, the navigation collides with the logo.
Make submissions reach the intended destination.
Connect the contact form to the existing backend and confirm successful delivery.
Explain what a visitor needs to correct.
Add clear required-field and email validation to the contact form.
Make it clear when a submission really worked.
After a confirmed successful submission, show Thanks, your request has been sent.
Tell people that their action is being processed.
Disable the submit button while the request is in progress and show Sending.
Make every field understandable.
Add visible labels to each field in the signup form.
Make a fixed set of choices easier to enter.
Add a Project type dropdown with Website, Web app, and Mobile app.
Make a large form easier to complete.
Split the onboarding form into Account, Preferences, and Review steps.
Let visitors return to unfinished work on the same device.
Save the app-project brief draft locally; do not store passwords, tokens, or sensitive details.
Let visitors select more than one relevant option.
Add checkboxes for Design, Development, and Maintenance in the inquiry form.
Explain file limits and upload progress.
Show allowed file types, size limits, progress, and errors on the current upload form.
Help visitors find an item without scanning everything.
Add instant search across the title and description of the existing prompt cards.
Make a long collection feel manageable.
Add category filters to the resource cards and include an All option.
Let visitors choose how to browse.
Add alphabetical and newest-first sorting to the resource list.
Make a large collection easier to browse in chunks.
Show 12 cards initially and add a Load more button.
Let visitors keep a personal shortlist.
Add bookmark buttons and a Saved view stored on this device.
Make useful pages easy to pass along.
Add a share action using the device share sheet with a copy-link fallback.
Help visitors reuse text accurately.
Add a Copy prompt button to each card with a confirmation message.
Group related views without losing context.
Show Overview, Examples, and Details as accessible tabs.
Make a page useful on paper or as a PDF.
Add print styles for the project checklist with readable headings and no navigation.
Keep a small interface choice between visits.
Remember whether a visitor chose grid or list view on this device.
Restore a broken action without redesigning the page.
The Save button in settings does nothing when clicked.
Send visitors to the destination they expect.
The pricing link in the header returns a 404.
Resolve the error behind a visible problem.
I will paste the exact console error and the steps that trigger it.
Get a route rendering again.
The dashboard becomes blank immediately after signing in.
Align the server-rendered page with the browser render.
I will paste the hydration warning and the affected route.
Restore an image and handle missing assets gracefully.
The hero image works locally but is missing in the deployed build.
Show current data after a successful action.
After editing a profile, the old name stays visible until I reload.
Stop one user action from creating two records.
Double-clicking the submit button creates two requests.
Give visitors a useful next step when something fails.
Show a clear retry option when the dashboard request fails.
Make direct visits behave like in-app navigation.
Refreshing /dashboard/settings returns a 404, but clicking to it works.
Reduce page weight while preserving useful image detail.
Review the homepage images and optimize the largest unnecessary downloads.
Avoid loading everything before it is needed.
Lazy-load below-the-fold images while keeping the hero image eager.
Make the page feel steady as it loads.
The hero text jumps when the image loads.
Keep text readable while fonts are loading.
Reduce the font flash on first load using the existing fonts.
Send less code for the page to run.
Find avoidable JavaScript on the landing page and make a small targeted improvement.
Keep a large collection responsive.
Filtering the product list becomes laggy with 1,000 items.
Avoid fetching the same data unnecessarily.
The dashboard fetches the same data multiple times on one navigation.
Stop the app from doing repeated work.
The profile component keeps rerendering after I edit a field.
Identify files the app no longer needs.
Identify unused assets and propose a cleanup list before removing anything.
Find the biggest delay before changing things.
Inspect the homepage and identify the top three causes of slow initial loading.
Give each page a clear name in tabs and search results.
Set the homepage title to Building Apps Without Code | Practical AI Guides.
Summarize the page for search visitors.
Describe the prompt library as 100 practical prompts for building and fixing apps with AI.
Make a shared page show useful text and imagery.
Use the supplied preview image, page title, and description when this page is shared.
Help machines understand content that is actually on the page.
Add Article structured data using the real author, title, dates, and image already on the page.
Provide a clear inventory of public content pages.
Include the current public pages and exclude drafts, redirects, and noindex pages.
Clarify the preferred version of a page.
Check that each public page points to its own correct preferred HTTPS URL.
Make meaningful images understandable beyond their pixels.
Add concise alt text to informative images and empty alt text for decorative ones.
Make the interface easier to use without a mouse.
Make focus clearly visible on navigation links, buttons, and form inputs.
Make important content easier to read.
Improve the muted gray text on white cards while keeping the same overall palette.
Give the page a useful reading outline.
Make the article page use a logical heading hierarchy without changing its appearance unnecessarily.
Get your bearings before asking for changes.
Explain how this website is organized and where I would edit the homepage and header.
Turn a confusing error into a useful next step.
I will paste the error message and tell you what I was doing.
Learn what this project needs to run.
Read the project and tell me the exact prerequisites and setup commands.
See the current project in your browser.
Start the existing development preview and tell me the local URL.
Resolve a concrete production-build problem.
Run the existing build, investigate its error, and make the smallest fix.
Catch obvious problems before sharing a change.
Check the journey from homepage to pricing to contact form.
Understand what the AI edited before accepting it.
Review the current diff for unintended changes and likely bugs.
Reverse a small edit while keeping other work.
Undo only the background-color change while preserving the other edits.
Understand the work before upgrading packages.
Review outdated dependencies and propose a small, prioritized update plan.
Find the important gaps before you publish.
Review the site for broken links, unfinished content, build errors, and missing configuration.
Provide the project context, ask for one change, name anything that must stay the same, and describe how you will check the result. Our customizer includes those boundaries.
Follow a complete workflow →