Text & chatWrite
Build a typed React component from requirements
Build a component with explicit behaviour and interfaces.
Use this prompt
What to provide
- Requirements
- Version, styling and project conventions
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 & chatPlan
Model valid states with TypeScript types
Model data and states with useful TypeScript types.
Use this prompt
What to provide
- Domain / data
1 input to replace
Text & chatReview
Choose where frontend state belongs
Choose where state belongs and how it changes.
Use this prompt
What to provide
- Feature
1 input to replace
Text & chatReview
Review React effects and cleanup
Check whether effects are needed and correctly scoped.
Use this prompt
What to provide
- Code
1 input to replace
Text & chatPlan
Design a resilient data-fetching experience
Design a reliable data-fetching experience.
Use this prompt
What to provide
- Feature / API
- Stack conventions
2 inputs to replace
Text & chatPlan
Build a form with accessible validation
Implement forms with accessible validation and state handling.
Use this prompt
What to provide
- Form
- React stack
2 inputs to replace
Text & chatReview
Investigate frontend performance from traces
Investigate frontend performance using actual measurements.
Use this prompt
What to provide
- Performance traces / code
- Page
2 inputs to replace
Text & chatWrite
Diagnose rerenders and stale rendering
Diagnose unexpected rerenders or stale rendering.
Use this prompt
What to provide
- Rendering issue
- Component code / profile
2 inputs to replace
Text & chatPlan
Design application routing and navigation
Plan navigation and route behaviour.
Use this prompt
What to provide
- Application
- Framework / version
2 inputs to replace
Text & chatPlan
Design frontend authentication states
Implement UI behaviour around authenticated sessions.
Use this prompt
What to provide
- App / provider
1 input to replace
Text & chatWrite
Build a maintainable responsive CSS layout
Solve a layout requirement with maintainable CSS.
Use this prompt
What to provide
- Layout
- Existing conventions
2 inputs to replace
Text & chatWrite
Choose meaningful frontend behaviour tests
Choose meaningful component and interaction tests.
Use this prompt
What to provide
- Frontend behaviour
- Test stack
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.