Text & chatPlan
Plan an EF Core schema migration
Plan a database change through EF Core.
Use this prompt
What to provide
- Schema change
- Database / version
2 inputs to replace
← All prompt libraries
Techotick / Prompt library
Text prompts
Explore 400 text prompts for writing, research, planning, coding and everyday tasks. Choose a goal, customise the inputs and check the response against your sources.
400 prompts to explore
Text & chatReview
Review asynchronous C# correctness
Find correctness and performance issues in asynchronous C#.
Use this prompt
What to provide
- C# code
1 input to replace
Text & chatPlan
Design reliable background processing
Design reliable background processing.
Use this prompt
What to provide
- Workload
- Environment
2 inputs to replace
Text & chatPlan
Design a modular .NET platform with typed contracts
Design independently usable modules with typed contracts.
Use this prompt
What to provide
- Modules
1 input to replace
Text & chatPlan
Design authentication and authorisation boundaries
Design identity and access around real trust boundaries.
Use this prompt
What to provide
- Application
1 input to replace
Text & chatCompare
Compare application multi-tenancy approaches
Evaluate how to isolate organisations within an application.
Use this prompt
What to provide
- System
1 input to replace
Text & chatPlan
Design caching and invalidation rules
Choose caching boundaries and invalidation rules.
Use this prompt
What to provide
- Application / workload
1 input to replace
Text & chatPlan
Plan compatible API evolution
Plan changes to an API without surprising clients.
Use this prompt
What to provide
- API / clients
1 input to replace
Text & chatPlan
Design a reliable system integration
Design a reliable connection between systems.
Use this prompt
What to provide
- System A
- System B
2 inputs to replace
Text & chatWrite
Plan service observability around user outcomes
Make a .NET service diagnosable in production.
Use this prompt
What to provide
- Service
1 input to replace
Text & chatWrite
Plan improvements to a legacy .NET system
Plan a safe improvement to a legacy .NET application.
Use this prompt
What to provide
- Legacy .NET system / change
1 input to replace
Text & chatWrite
Write an architecture decision record
Record a consequential software architecture choice.
Use this prompt
What to provide
- Choice
- Evidence
2 inputs to replace
Give the prompt a useful brief
A text prompt is most useful when it names the task, supplies the source material and describes the result you need. Replace the square-bracket inputs with your own details before copying it into your tool.
Make a summary easier to check
For a meeting summary, provide the notes and ask for decisions, action owners and unresolved questions in separate sections. Tell the tool to mark missing owners as unknown. Compare the result with the original notes before sharing it.
Refine one thing at a time
If an answer is too broad, specify the audience or ask for a shorter format. If it adds facts that are absent from your source, ask it to use only the supplied material and identify gaps. Keep sensitive information out of examples unless you have permission to use it.
Questions about text prompts
Supply the information named by each input, such as the text to summarise, your audience or the required format. The preview updates as you fill in the fields. Unfilled brackets remain visible so you can spot missing context.
Yes, but check the instructions and examples first. Change the goal, source material and output format together, then review the response. A prompt tested for one task does not guarantee the same result elsewhere.