All libraries

1. Ask AI to help screen ideas for a first app

   Use it when: You have several first-app ideas and are not sure which is small enough to build with AI in a few days.

   Works with any AI assistant.

   Fill in your parts

   Your app ideasFor example: team equipment loans; meeting room duty roster; office visitor log

   Your prompt

   Goal: I want to choose one small first app to build with AI in a few days.
   Reader: myself; I have never worked as a programmer.
   Material: my ideas below, each with who its users are and how the work is done today.
   ‹daftar-ide›
   Limits: do not choose for me. Do not add features to my ideas. Flag ideas that use sensitive data, payments or public users.
   Shape: a table with columns idea, number of users, sensitive data yes or no, estimated size of the first version (small, medium, large), and risk if it breaks.
   Check: for each idea, name one thing I need to confirm myself before choosing.

   Copy prompt

   Learn it in: What building with AI means

2. Ask AI to map one feature

   Use it when: When you want to understand one feature's flow from click to stored data, without changing the code.

   Works with any AI assistant.

   Fill in your parts

   Feature nameFor example: save a loan

   Related filesFor example: the form component, the loans API route, the table schema file

   Your prompt

   Goal: I want to understand how the ‹nama-fitur› feature works from click to saved data.
   Reader: me, a beginner builder who can read a little code.
   Material: the following files from my project.
   ‹berkas›
   Limits: do not change any code. If a part is not visible in these files, say you do not know rather than guess.
   Shape: a numbered step-by-step list. For each step, write the file, whether it runs in the browser or on the server, and what can fail there.
   Check: flag every access check or secret key that turns out to run in the browser.

   Copy prompt

   Learn it in: The parts of a web app

3. Ask AI to interview you about your idea

   Use it when: Your idea is still rough notes and you need help finding the decisions not yet made before writing a spec.

   Works with any AI assistant.

   Fill in your parts

   Your app ideaFor example: a team equipment-loan tool

   Your first notesFor example: five people, using a spreadsheet now, often forget to record returns

   Your prompt

   Goal: I want to write a one-page spec for ‹ide-aplikasi›, and I need help finding the decisions I have not made yet.
   Reader: myself.
   Material: my first notes: ‹catatan›
   Limits: do not write the spec. Ask questions one at a time and wait for my answer before the next. At most ten questions.
   Shape: each question names the part of the spec it is about: users, flow, data, acceptance criteria or out of scope.
   Check: at the end, summarise my answers per part without adding anything I did not say.

   Copy prompt

   Learn it in: From idea to spec

4. Template: ask for a diff explanation, not a verdict

   Use it when: AI has given you a diff and you need to understand it line by line before deciding yourself whether to accept it.

   Works with any AI assistant.

   Fill in your parts

   Goal of the changeFor example: adding late fees to the loan list

   Your roleFor example: a team tool builder who is new to reading code

   Rule or specFor example: the written fee rule: the first three days are free

   Examples to work outFor example: loans 2 days and 5 days late

   Your prompt

   Goal: I want to understand the change for ‹tujuan-perubahan› before I decide whether to accept it.
   Reader: me, ‹peran-saya›.
   Material: the diff below and ‹aturan-atau-spesifikasi›.
   Limits: do not judge whether the diff should be accepted; do not change the code.
   Shape: per chunk, what each line does in plain words; then a list of the code's assumptions about the data and the inputs that make it behave differently.
   Check: work through ‹contoh-uji› step by step and point to the line most likely to be wrong.

   Copy prompt

   Learn it in: Reading code from AI

5. Template: one code change request

   Use it when: You want to ask for one small code change with clear limits: which files may be touched and what is off-limits.

   Works with any AI assistant.

   Fill in your parts

   Change the user seesFor example: staff can mark a tool as returned

   Scope of this stepFor example: the button and saving it, no history

   Who uses itFor example: warehouse staff

   Files and materialFor example: the loan list page and the simpanPinjaman function

   Files that may changeFor example: the loan page file and the loan route file

   Limit specific to this taskFor example: A status already Returned cannot be changed again from this page.

   How to checkFor example: click Mark returned on the first row, reload, the status stays Returned

   Your prompt

   Goal: ‹perubahan-perilaku›. This step is only ‹cakupan-langkah›.
   Reader: ‹pengguna-fitur›; me, reading the diff.
   Material: ‹berkas-dan-bahan›.
   Limits: change only ‹berkas-yang-boleh›; do not add packages; do not change the schema or create migrations; do not delete or loosen tests; do not touch the env file; do not commit or release. ‹batas-khusus›
   Shape: diff, list of changed files, a three-line summary, and what is not done yet.
   Check: ‹cara-memeriksa›

   Copy prompt

   Learn it in: Asking for small changes