Top Tweets for #BuildWithLLMs

12 months ago

#BuildWithLLMs day 3 1. Write a clear, very specific prompt, always pointing to the part you are editing. 2. Put the prompt first, then paste the logs. 3. Ask for focused edits only. 4. When the LLM suggests changes, read them carefully; it often tweaks sections that don’t need it. 4. Keep functions in separate files. Stay modular; one giant file breaks easily. 5. Before any edits, have the LLM draft a Plan and a TODO list. 6. Ask the LLM to add code comments for everything.

531

Moeen @Moeenxyz

12 months ago

#BuildWithLLMs day 2 1. Prep every doc for what you need, like SDKs, especially if you plan to use @thirdweb, @privy_io, or any newer web3 SDKs. Give that full context to the LLM; most models struggle with web3 SDK details. 2. Read the docs yourself so when the LLM hallucinates, you can spot and fix it. 3. Create a rule file with naming and structure standards: • camelCase for xx, PascalCase for yy • Put functions in the zz folder • always use clear, descriptive names • Anything else that matters (Comment if you want the complete rule file.) 4. Use official docs or the LLM to spin up your base folder structure. Keep it clear: frontend and backend in separate roots, then organize each layer and log every rule in the rule file. 5. Add a guides folder. Drop all text docs there. Tell the LLM to read them and, after finishing each part of the app, have it generate a doc for that part. e.g., when an API endpoint is done, get the LLM to write the doc, then feed that back to wire the API into the frontend. 6. Learn git: small commits, cherry-pick, revert. Commit every step so you can roll back fast when the LLM breaks something.

835

Moeen @Moeenxyz

12 months ago

#BuildWithLLMs day 1: Prep before code a single line: 1. Draft a PRD in depth. Take your regular spec and pack it with every extra detail. 2. Slice it up. I aim for at least 5 chunks; some builds hit 20+ in the first run, and can get to 100 or more at the end. 3. Go deep on each chunk: stack calls, SDK picks, tiny code snippets, every note, and smaller details in your mind. 4. Add all possible changes, connections, add-ons, or comments. 5. Map the flow. Mermaid diagrams are super LLM-friendly and let you see how every piece clicks together. 6. Iterate until you're satisfied it's a good starting point. 7. Pass every chunk to an LLM and ask it to polish the wording for dev use. Then read every line yourself to be sure nothing vital got lost or invented. This will take a good amount of time, but it saves tons of time when coding.

987

Top Tweets for #BuildWithLLMs

Last Seen Hashtags on Sotwe

Trends for you

Most Popular Users