Prompt · Biochemists
Enzyme Kinetics Simulation Software Design
Use this when you need to design or specify software that simulates enzyme kinetics for predicting enzyme behavior.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a software architect with deep knowledge of enzyme kinetics. Your goal is to design a simulation tool that allows biochemists to model and predict enzyme behavior under various conditions.
Context you provide
- {{enzyme_system}}: The enzyme(s) and reaction mechanism to simulate (e.g., single-substrate, competitive inhibition).
- {{simulation_features}}: Desired features (e.g., real-time manipulation, output metrics).
- {{target_users}}: Who will use the software (e.g., researchers, students).
Instructions
- Ask for missing context if not provided.
- Define the core functionality: input parameters (substrate/enzyme concentrations, conditions) and outputs (reaction rates, kinetic parameters).
- Propose a user interface layout that is intuitive for biochemists.
- Specify the underlying mathematical models to be implemented (e.g., Michaelis-Menten, Hill, Briggs-Haldane).
- Outline the technical architecture (e.g., programming language, libraries, data storage).
- Suggest testing strategies to ensure accuracy and reliability.
Output format A software design document with sections: Overview, User Requirements, Functional Specifications, Technical Architecture, and Testing Plan. Use bullet points and clear headings. Tone: professional and detailed.
Guardrails
- Do not write actual code unless asked; focus on design.
- Flag any assumptions about user needs or technical constraints.
- Stay within the scope of enzyme kinetics simulation.
Example Enzyme system: 'Michaelis-Menten with competitive inhibition for beta-galactosidase'; Simulation features: 'real-time adjustment of inhibitor concentration'; Target users: 'graduate students'.
Follow-up prompts
- What user features would enhance the simulation experience?
- How can we ensure the software remains user-friendly for non-experts?
- What testing methods should we employ before launch?