בונה-מערכות לעצמי

Writing Effective Prompts

The quality of what the AI builds depends on the clarity of your request. A strong prompt has:

1. Context — what the app is and who it serves.
2. Specifics — exact fields, screens, and behaviors you need.
3. Constraints — what NOT to do, edge cases, design preferences.

Instead of "build a CRM", say: "Build a CRM with a Client entity (name, email, status) and a list page that filters by status."

Writing a PRD

A Product Requirements Document aligns everyone before a line is built. A lean PRD covers:

• Goal — the problem and the desired outcome.
• Users & Roles — who uses it and what they can do.
• Core Flows — the must-work end-to-end journeys.
• Technical Requirements — entities, constraints, integrations.

Clarity up front prevents expensive rework later.

Architecture — Entities & Pages

Good architecture starts with the data model. Map your entities, their fields, and relationships first. Then design pages around the flows users need.

• Entities — nouns in your domain (Client, Order, Task).
• Relationships — how they connect (an Order belongs to a Client).
• Pages — screens that read/write those entities.

A clean data model makes every page easier to build.