Improve code and API naming
Improve names to communicate intent.
Use this prompt
What to provide
- Code / API / schema
- Conventions
Techotick / Prompt library
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
Improve names to communicate intent.
Add documentation where it improves understanding.
Assess whether a codebase supports its intended needs.
Turn maintenance concerns into actionable work.
Plan a software migration with verifiable checkpoints.
Check an interface for consistency and compatibility.
Review supplied code for defensive security issues.
Explain a code change for an independent reviewer.
Design a .NET solution around explicit requirements.
Specify or implement an ASP.NET Core endpoint.
Review service registration and lifetime correctness.
Improve an Entity Framework Core query safely.
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.
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.
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.