Every reusable prompt
Collected from prompt fences in the curriculum. Edit the context before you run one; review the output before it changes the project.
Steps
Context: I am starting the [landing-page/app] route. The intended project folder is [path]. My finish line is [observable result]. Inspect only. Do not install, create, edit, dele…
02Steps
Context: Below are my original input and the answer I received. Audit the answer; do not rewrite it yet. Create a table with: - claim, - supplied by my input / derived / externall…
03Steps
Context: I need an AI system to [describe the recurring job]. The source material changes [how often]. The output must pass [named checks]. Explain which parts belong to: - base-m…
04Steps
Context: My task is [task]. A passing result must [checks]. The consequence of an error is [impact]. My latency and cost constraints are [constraints]. Available model and effort…
05Steps
Context: My goal is [goal]. The available files are [short file list with one-line descriptions]. A passing result must [checks]. Do not solve the task yet. Propose the smallest c…
06Steps
Context: The recurring task is [task]. Here are representative failures: [examples]. A passing result must [checks]. Source material changes [frequency] and is located [location]…
07Steps
Context: The task is [exact task]. The allowed inputs are [inputs]. The allowed changes are [changes]. The result must be saved [location] and pass [checks]. Compare chat, a proje…
08Steps
Context: Work only in [project folder]. The goal is [goal]. A passing result must [checks]. Relevant files are [files]. Non-goals are [non-goals]. Inspect and plan only. Do not ed…
09Steps
Context: The connected system is [system/account]. The task is [task]. Allowed actions are [search/read only]. Disallowed actions are [writes, sends, deletes, permission changes…
10Steps
Context: My server-side feature is [feature]. It will call [provider/API]. The users are [users] and the expected request pattern is [pattern]. Do not request or display a real cr…
11Steps
Context: My intended project folder is [exact path]. Review this command: [command] Do not run it. Explain: 1. the program, flags, targets, operators, and resolved working folder…
12Steps
Context: The approved project root is [path]. Inspect only. Do not edit, move, install, generate, commit, or run the app. Return a concise map of: - project purpose from the READM…
13Steps
Context: Inspect this project's README, package.json, package-manager field, and lockfiles. The task is [task]. Do not install or edit. Report: 1. required runtime and where that…
14Steps
Context: I want a Git save point for [milestone]. Inspect only. Review git status, unstaged diff, staged diff, current branch, and recent commit. List: - files that belong in this…
15Steps
Context: I plan to publish branch [branch] from local repository [name] to GitHub repository [owner/name] with visibility [public/private]. Inspect only. Do not change remotes, st…
16Steps
Context: These files are candidate source material for [project]. The intended audience and page goal are [details]. Inspect only. Do not rename, move, convert, compress, rewrite…
17Steps
Context: The project is [landing page/app]. The user action is [action]. Proposed services are [services]. The authoritative source and data are [locations]. Map the action from b…
18Steps
Context: You may read project-brief.md and the files in source/. Do not write website copy yet. Produce: 1. an inventory of every supplied file; 2. the public claim or page need i…
19Steps
Context: Read the approved project-brief.md, the source inventory, and the public-ready files. Use the knowledge-base.md template. Create a compact site knowledge base. Preserve e…
20Steps
Context: Read project-brief.md, knowledge-base.md, the approved brand assets, and the supplied reference notes. Write into the design.md template. Do not write code. For every pro…
21Steps
Context: Read the approved brief, knowledge base, design rules, and current file tree. Do not edit files and do not install anything. Produce an implementation plan with: - route…
22Prepare the change
Context: Read AGENTS.md if present, then the approved brief, knowledge base, design rules, implementation plan, and current diff. Plan only milestone [NAME]. Do not install, scaff…
23Steps
Context: Review the running site against project-brief.md, knowledge-base.md, design.md, implementation-plan.md, and qa-checklist.md. Do not change code yet. Report only reproduci…
24Prepare the deployment
Context: Prepare this reviewed Astro repository for GitHub and Vercel. Do not push or deploy. Inspect tracked files, .gitignore, package scripts, Astro configuration, and the revi…
25Prepare the change
Context: Read the approved brief, live URL, launch checklist, and current site metadata/configuration. Do not create accounts or change external systems. Produce a launch-gap repo…
26Steps
Context: Interview me to complete prd.md for my own app. Do not propose a sample product, schema, feature, customer, or business model. Ask one decision-sized question at a time…
27Steps
Context: Audit this freshly cloned app starter against commit e887b0cc9d380576aa3318bf8c095afbc3d768cb. Do not modify source. Report the current HEAD, remotes, licence, package ma…
28Prepare the cleanup
Context: Read the approved PRD, keep-change-ignore.md, package.json, environment schema, routes, navigation, client-side polling, tests, and starter copy. Do not delete or edit ye…
29Prepare the connection
Context: Inspect the pinned starter's environment schema, .env.example, .gitignore, Drizzle configuration, and migration files. Do not reveal values and do not apply a migration…
30Prepare the model
Context: Read the approved PRD, data-model.md, existing schema/migrations, and current database access code. Do not generate or apply a migration yet. Propose the minimum core sch…
31Prepare the change
Context: Inspect the pinned auth form, Supabase browser client, provider registry, callback route, profile trigger, sign-out route, and tests. Do not change provider dashboards. P…
32Prepare the slice
Context: Read the approved PRD, data-model.md, migration, auth helpers, data-access code, and selected acceptance criteria. Plan one vertical slice through UI, validation, authent…
33Prepare the feature
Context: Read the approved differentiator and its acceptance criteria. The existing protected vertical slice must remain intact. Propose the smallest implementation and evaluation…
34Prepare the test
Context: Read the frozen PRD, eval-plan.md, test configuration, current tests, and release-candidate diff. Do not change code. Build an acceptance matrix mapping every criterion t…
35Prepare the release
Context: Prepare a production release report for this frozen commit. Do not push, migrate, change dashboards, or deploy. Inspect source, package scripts, environment schema, migra…
36Prepare the addition
Context: The verified core app works. Read the approved new PRD criterion and the current keep/change/defer map. Do not add a dependency or create an account. For the single syste…
37Steps
Context: I am about to perform [ACTION]. Do not perform it. Prepare an approval packet with: - current and proposed state; - exact target and scope; - commands or external writes…
38Prepare the configuration
Context: Inspect environment schemas, .env.example, ignore rules, source reads, and deployment documentation. Never print or repeat any value. Produce a table of variable name, pu…
39Steps
Task: [one concrete milestone] Done when: [observable evidence] Read first: - [governance/instructions] - [approved PRD or brief] - [relevant source and tests] Current state: - co…
40Steps
Context: Read the approved requirements and current implementation. Do not change code or prompts. Create a compact evaluation matrix with ID, requirement, setup/input, action, ex…
41Prepare the signals
Context: Inspect only the systems this released feature actually uses. Do not install monitoring or analytics. For each critical workflow, propose the minimum signal set for succe…
42Steps
Context: Read the approved scope, reviewed commit, diff from the last save point, eval results, deployment/health evidence, and open issues. Do not change or deploy anything. Reco…
43Ask for diagnosis only
Context: The intended result is [result]. The failing step is [step]. The environment is [local/preview/production]. The project folder and branch are [details]. Here is the redac…
No prompts match that search.