Stop staring at a blank chat box. PromptNest gives you ready-to-customize AI prompts for studying, coding, career moves, and the busy weeks between them.
No sign-up needed to browse and copy the starter library.
PromptNest / study session
Feynman Concept Explainer
Explain any hard topic with an analogy, the formal definition, a worked example, and self-check questions.
Find → Copy → Build
Choose your lane
Every prompt is written to get you past generic answers: provide context, define the output, and make the AI show its work.
The starter library
51 ready-to-customize prompts for the work engineering students actually do.
Act as a patient engineering tutor. Explain [TOPIC] as if I am a first-year student seeing it for the first time. Start with an everyday analogy, then give the formal definition, a worked engineering example, three common misconceptions, and five quick self-check questions. Keep the math accurate and define every symbol.
Act as a patient engineering tutor. Explain [TOPIC] as if I am a first-year student seeing it for the first time. Start with an everyday analogy, then give the formal definition, a worked engineering example, three common misconceptions, and five quick self-check questions. Keep the math accurate and define every symbol.
I have an exam in [COURSE] on [DATE]. Based on these topics: [TOPICS], create a realistic revision plan from today to the exam. Prioritize high-yield foundations, include active recall and problem practice, schedule short review loops, and leave one buffer session. Return a day-by-day table with specific tasks and estimated minutes.
Turn the rough lecture notes below into a concise engineering study sheet. Preserve technical accuracy, organize ideas into headings, define key terms, flag any unclear or likely incorrect statements, and end with a formula or concept checklist. Notes: [PASTE NOTES]
Create 15 challenging multiple-choice questions on [TOPIC] for an engineering undergraduate. Mix conceptual, calculation, and application questions. Give four options each, put the answer key after all questions, and explain why every correct answer is right and why each tempting distractor is wrong.
Teach me how to derive [EQUATION OR RESULT] step by step. State the assumptions first, explain the purpose of every transformation, check units where relevant, and point out where students commonly make mistakes. Do not skip algebra. End by showing when the result does and does not apply.
Help me solve this engineering problem without jumping straight to the final answer. First identify the knowns, unknowns, governing principles, and unit conversions. Then propose a solution plan, ask me for my next step, and only reveal the full worked solution after I attempt it. Problem: [PASTE PROBLEM]
Build a one-page formula sheet for [COURSE OR TOPIC]. Group formulas by use case, define every variable with SI units, include conditions or assumptions, and add a tiny decision guide for choosing the right formula. Include only formulas a student can apply in an exam.
Review this engineering lab report section as a strict TA. Check whether the method, results, uncertainty discussion, figures, and conclusion are technically sound. List specific revisions in priority order, identify unsupported claims, and suggest clearer academic wording without inventing data. Text: [PASTE SECTION]
Create 25 high-quality active-recall flashcards from this material: [PASTE MATERIAL]. Use short questions that test understanding rather than recognition. Include definitions, cause-and-effect, comparisons, and application prompts. Format as a two-column table: Front | Back.
Help me read this engineering research paper excerpt: [PASTE EXCERPT]. Explain the research question, method, variables, main claim, limitations, and what background knowledge I need. Separate what the authors demonstrate from what they only suggest. End with five questions I should ask before citing it.
Act as an engineering viva examiner for [TOPIC OR LAB]. Ask one question at a time, wait for my answer, then grade it for correctness, precision, and depth. Give a better model answer and a follow-up question that is slightly harder. Start with an easy foundational question.
Break down this engineering assignment brief into a practical checklist: [PASTE BRIEF]. Identify deliverables, grading signals, hidden constraints, required evidence, likely pitfalls, and a recommended order of work. Do not write the assignment for me; help me plan an original, well-supported submission.
Create a 60-minute study-group agenda for [TOPIC] with [NUMBER] engineering students. Include a five-minute warm-up, one teach-back segment, two collaborative problem-solving activities, individual retrieval practice, and a closing action list. Make sure everyone has a role and the session does not become passive note-reading.
Act as a senior software engineer. Help me debug this code: [PASTE CODE]. Do not rewrite everything immediately. First restate the expected behavior, identify likely failure points, give a minimal reproduction strategy, and rank hypotheses by probability. Then propose the smallest safe fix, explain why it works, and add focused test cases.
Analyze the time and space complexity of this code: [PASTE CODE]. Walk through each loop, recursion branch, and data structure choice. State best, average, and worst case when they differ. Then suggest one optimization only if it improves the real bottleneck, with a trade-off explanation.
Review this pull request as a thoughtful teammate: [PASTE DIFF OR CODE]. Focus on correctness, edge cases, naming, readability, security, and maintainability. Categorize comments as blocking, important, or optional. Be specific and kind. Finish with a short summary a student developer could use in their PR description.
Design a clean REST API for [FEATURE]. Define resources, endpoints, request and response shapes, status codes, validation rules, authentication assumptions, and error responses. Include one example request and response for each endpoint. Prefer simple conventions suitable for a student project.
Help me improve this SQL query: [PASTE QUERY AND SCHEMA]. Explain what it does, check correctness and edge cases, identify performance risks, and propose a clearer version if needed. Mention useful indexes only when justified by the query pattern. Keep database-specific syntax explicit.
Create a focused test plan for this function or feature: [PASTE CODE OR DESCRIPTION]. Cover happy paths, boundaries, invalid input, state transitions, and regression risks. Return a table with test name, setup, action, expected result, and why it matters. Use the testing stack I specify: [STACK].
I am in this Git situation: [DESCRIBE STATUS, COMMANDS, AND GOAL]. Give me the safest recovery plan with exact commands, but first explain what each command will change. Include a backup step, flag destructive commands clearly, and offer an alternative if shared remote history is involved.
Explain this project structure to a new contributor: [PASTE TREE OR FILE LIST]. Identify the entry points, data flow, important modules, external services, and likely places to make changes for [FEATURE]. Then suggest a 30-minute onboarding path with files to read in order.
Act as a technical interviewer. Give me a [EASY/MEDIUM/HARD] data structures and algorithms problem about [TOPIC]. Ask clarifying questions as I work, do not reveal the solution early, and evaluate my approach for correctness and complexity. At the end, show an optimal solution in [LANGUAGE].
Draft a concise README for this student project: [PROJECT DETAILS]. Include a clear problem statement, features, tech stack, setup instructions, usage, project structure, limitations, and future improvements. Avoid hype and do not claim features that are not implemented.
Translate this error into plain English and help me fix it: [PASTE ERROR, STACK TRACE, AND RELEVANT CODE]. Explain the immediate cause, the underlying concept, a minimal fix, and one way to prevent it next time. If information is missing, list the exact file or command output you need.
I want to refactor this code without changing behavior: [PASTE CODE]. Propose small ordered steps, identify seams for tests, and show the first refactor only. Preserve public interfaces unless there is a strong reason to change them. Explain how each step reduces risk.
Review this student web app feature for common security issues: [PASTE CODE OR FLOW]. Check input handling, auth boundaries, secrets, error exposure, dependency use, and data access. Explain risk in practical terms, label severity, and give the smallest responsible fix. Do not invent vulnerabilities without evidence.
Convert this [SOURCE LANGUAGE] code to idiomatic [TARGET LANGUAGE]: [PASTE CODE]. Keep behavior identical, explain important language differences, preserve error handling, and provide a small example input/output. Point out any construct that cannot be translated one-to-one.
Turn this engineering experience into three strong, truthful resume bullets: [PASTE EXPERIENCE]. Use action + technical work + measurable outcome where evidence exists. Do not invent numbers. Tailor the wording for a [TARGET ROLE] internship and keep each bullet under two lines.
Help me explain this project in an interview: [PROJECT DETAILS]. Create a 60-second answer using problem, constraints, my contribution, technical decisions, result, and what I would improve. Keep it honest, technically specific, and easy for a recruiter to follow.
Write a clear LinkedIn About section for an engineering student based on: [BACKGROUND, SKILLS, PROJECTS, INTERESTS]. Use a confident but grounded voice, name the problems I enjoy working on, and include a simple invitation to connect. Avoid buzzword lists and unproven claims.
Analyze this internship or graduate job description: [PASTE DESCRIPTION]. Extract the must-have skills, nice-to-haves, key responsibilities, and repeated signals. Compare them with my background: [PASTE BACKGROUND]. Then give me a focused one-week preparation plan and five honest resume changes.
Interview me for a [TARGET ROLE] internship using behavioral questions. Ask one question at a time and wait for my answer. Then score it for clarity, ownership, impact, and reflection; help me strengthen it with STAR structure while keeping my story truthful.
Run a mock technical interview for a [ROLE] student candidate. Use my skills: [SKILLS]. Start with fundamentals, then one practical scenario. Ask follow-ups based on my answers, correct misconceptions respectfully, and finish with a rubric plus the three topics I should review next.
Draft a short, respectful outreach email to [PERSON/ROLE] about [TOPIC OR OPPORTUNITY]. Use this context: [CONTEXT]. Include a specific reason I am reaching out, one low-effort question, and no exaggerated flattery. Keep it under 130 words and provide three subject lines.
Review my engineering portfolio or GitHub project page: [PASTE LINK CONTENT OR DESCRIPTION]. Evaluate whether a recruiter can quickly see the problem, my role, stack, evidence of work, and outcomes. Give a prioritized list of edits and suggest what screenshots or demos would add the most credibility.
Help me answer this application question: [QUESTION]. Use my real background: [BACKGROUND]. First identify what the employer is assessing, then outline a precise answer. Draft a version under [WORD LIMIT] words that is direct, specific, and free of generic claims. Mark every place I should personalize.
Create a practical four-week networking plan for an engineering student targeting [FIELD]. Include campus groups, alumni outreach, events, a simple tracking system, and weekly outreach goals. Make it sustainable alongside classes and focus on learning conversations rather than asking strangers for jobs.
I received an internship offer for [ROLE/COMPANY TYPE]. Give me a thoughtful list of questions to ask before accepting, grouped by work, mentorship, expectations, logistics, and growth. Keep the tone professional and do not assume the offer is negotiable.
Draft a concise cover letter for this role: [JOB DESCRIPTION]. Use my background: [BACKGROUND]. Connect two or three specific experiences to the role requirements, keep every claim truthful, and avoid restating my resume. Return a version under 300 words plus a checklist of details I should verify.
Plan my week around these fixed commitments: [COMMITMENTS], deadlines: [DEADLINES], and priorities: [PRIORITIES]. Create a realistic schedule with focused study blocks, coding practice, rest, and catch-up time. Use time estimates, avoid overpacking, and identify the one task I should protect first each day.
Help me triage this task list: [PASTE LIST]. Classify each item by impact, urgency, energy required, and whether it can be delegated, deleted, or deferred. Then give me a short today plan with no more than three must-do tasks and a sensible next-action for everything else.
Design a 90-minute deep-work sprint for [TASK]. Break it into setup, focused work, a short reset, and a closing review. Define a visible finish line, likely distractions, and a fallback if I get stuck. Keep the plan concrete enough to start in the next five minutes.
Turn this engineering project idea into a two-week MVP plan: [IDEA]. Define the smallest valuable version, user flow, tech choices to validate, milestones, risks, and a simple demo checklist. Favor shipping a working slice over adding lots of features.
Turn these meeting notes into a clean action list: [PASTE NOTES]. Separate decisions, owners, deadlines, open questions, and risks. Rewrite vague commitments into clear next actions without assigning people who are not named. End with a brief follow-up message I can send to the group.
Help me build a sustainable learning system for [SKILL] while I have [HOURS] hours per week. Create a loop of learn, practice, retrieve, build, and reflect. Include milestone projects, ways to measure progress, and rules for choosing what to skip so I do not drown in tutorials.
I am avoiding [TASK] because [REASON]. Help me reset without guilt. Break the task into a two-minute starting action, a 25-minute first session, and a low-friction reward. Identify the decision or uncertainty I am avoiding and give me one concrete way to resolve it.
Help me make this decision: [OPTIONS AND CONTEXT]. Identify the criteria that actually matter, assign reasonable weights, score the options transparently, and show sensitivity if one criterion changes. Include non-quantifiable concerns and end with a recommendation framed as a trade-off, not false certainty.
Create a 20-minute weekly review for an engineering student. Include wins, unfinished work, upcoming deadlines, calendar cleanup, project progress, energy check, and the next week’s top three outcomes. Make it a repeatable checklist I can copy into Notion or a notes app.
Create a lightweight team charter for a [COURSE/PROJECT] group of [NUMBER]. Cover goals, roles, communication norms, meeting cadence, version-control rules, definition of done, feedback habits, and what to do when someone is blocked or misses a commitment. Keep it practical and non-corporate.
Build a simple personal dashboard for preparing for [TARGET INTERNSHIP TYPE] over [TIMEFRAME]. Balance applications, coding practice, projects, networking, and interview prep. Give me weekly metrics that encourage progress without turning every hour into a spreadsheet.
Help me plan a [LENGTH]-minute technical presentation about [TOPIC] for [AUDIENCE]. Create a slide-by-slide story, a hook, key visuals to include, transitions, and a rehearsal plan. Keep technical depth appropriate for the audience and include likely questions with concise answers.
What’s next
PromptNest Pro gives engineering students full prompt packs for technical interviews, semester revision, project shipping, and more—with new additions every week.
PromptNest Pro — Founding Member
$4.99/month for full prompt packs and weekly drops. Keep the useful free starter library; upgrade when you want a deeper edge.
Become a Founding Member Compare plans