Start from constraints
Audience, existing code, delivery ownership, integrations, and maintenance needs come before a framework preference.
For technical evaluators
Technical stack
The tools I currently use to turn product requirements into reviewable web software. The list shows working familiarity—not equal depth or a claim that every project needs every tool.
- Next.js
- React
- Prisma ORM
- Tailwind CSS
- Typescript
- Express.js
- Redux
- Git
- Rest API
- Mongo DB
- UI UX Patterns
- Framer Motion
How choices are made
The requirement chooses the stack
Prefer inspectable defaults
Typed boundaries, explicit data flow, and readable structure matter more than adding libraries for their own sake.
Explain the trade-off
A technical choice should be explainable through the product constraint it addresses and the cost it introduces.
Continue the evaluation
- Relevant evidenceInspect create-mohsen-app
- Relevant toolCompare stack trade-offs
- Role conversationShare the role
