Good at
Brainstorming, explaining, restructuring, summarising supplied text, drafting, and generating starting-point code.
Large language models can help you explore ideas, explain concepts, draft text, and generate code. They can also produce convincing errors. This short guide shows a reliable workflow for using them with TechTahi.
An LLM generates a response one piece of text at a time using patterns learned during training and the context you provide. It does not automatically know whether each statement is true, current, appropriate, or supported by a real source.
Brainstorming, explaining, restructuring, summarising supplied text, drafting, and generating starting-point code.
Facts, quotations, references, calculations, recent events, legal or health guidance, and code behaviour.
Set the goal, provide relevant context, test the result, correct mistakes, and take responsibility for the final work.
Clear and specific instructions usually work better than long, vague requests. Include only context that helps with the task, define constraints, and say exactly what the output should look like.
State the outcome you want in one direct sentence.
Give the audience, purpose, inputs, and any background the model needs.
Specify requirements, exclusions, length, technologies, tone, or accessibility needs.
Define the format and ask the model to check the result against your requirements.
Keep the cycle small so errors are easy to find.
Use TechTahi’s Prompt Builder to describe the problem, users, behaviour, and constraints.
Send the prompt to your chosen LLM. Paste its complete HTML response into Generated Output.
Try every control, test narrow screens, and inspect the browser console if something fails.
Describe what happened, what you expected, and any error message. Ask for a targeted fix.
Use TechTahi’s visual editor for text, layout, and style adjustments, then preview again.
Save only after the page works as expected and you have reviewed its content and data use.
Fluent wording is not evidence. Verification should match the risk: a colour suggestion needs little checking; a medical claim, assessment answer, or security decision needs authoritative evidence and qualified review.
Do not paste passwords, API keys, personal records, confidential material, unpublished research data, or identifiable student/client information into an AI service unless its approved data controls make that use appropriate.
AI permission can differ by course and assessment. Check the assessment instructions, be transparent about permitted use, and ask your lecturer when unsure.
Do not present unreviewed AI output as your expertise. Check originality, attribution, copyright requirements, and whether AI use must be acknowledged.
Do not automate consequential decisions without appropriate oversight. People affected by a decision should have suitable safeguards and a way to challenge errors.
Product features and institutional rules change. Use current official documentation when details matter.