@moeen

#BuildWithLLMs day 2 1. Prep every doc for what you need, like SDKs, especially if you plan to use thirdweb, privy, 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.

0 reply

0 recast

0 reaction