RafeeqPro: AI Prompt Framework and Limitation Prompt

That makes perfect sense. Setting a hard cap of 25–30 files is the smartest way to manage Greta’s credit consumption and avoid the "agent limit" loop that has been failing you.

If you'd like me to save or delete info about your preferences like this, you'll need to turn on the feature on the Saved info page.

Since we are moving to a new project to fix this, here is the Master Rebuild Prompt I promised. This is specifically engineered to keep your file count low while maintaining the complex logic for your prayer app.

The "Constraint-First" Rebuild Prompt

Paste this into the initial chat of your new Greta project:

System Constraints & Architecture:

1. File Limit: This project must never exceed 25 files.

2. Consolidation: Combine related UI components into a single components.tsx file. Do not create separate folders or files for every button, card, or icon.

3. Non-Destructive Updates: When I ask for an update, do not overwrite existing logic unless explicitly asked. Always verify that the existing build remains functional before committing changes.

4. Stack: Use React, Tailwind CSS, and Adhan.js for prayer calculations.

Project Goal:

Rebuild the Prayer & Masjid Finder app shown in the attached screenshots.

• Primary Theme: Dark emerald green (#022c22) with gold/amber accents.

• Screen 1 (Home): Large digital clock, current prayer highlighted, and a card showing "Next Prayer" countdown.

• Screen 2 (Schedule): A list view of the 5 prayers + Sunrise with Iqamah times.

• Screen 3 (Masjid): A map view and list of nearby Masjids.

Step 1: Build the core theme and the Home Screen UI using only 3 files: App.tsx, components.tsx, and types.ts. Stop and show me the result.

Why this works:

• The 3-File Start: By forcing Greta to start with only 3 files, you prevent it from generating the usual "boilerplate" bloat (like Button.tsx, Header.tsx, Layout.tsx as separate entities).

• Adhan.js Requirement: Specifying the library prevents the AI from "hallucinating" its own math, which is usually where the build breaks and eats your credits.

• "Stop and Show Me": This is crucial. It forces Greta to give you a checkpoint. If the UI looks wrong, you can fix it before the project gets too deep into the file limit.

A Note on "Overwriting":

Greta's biggest flaw is "forgetting" old code when adding new features. By explicitly telling her "verify that the existing build remains functional," you are triggering her internal "test-before-write" protocol, which is more stable in the 2026 version of Questera.

Give that prompt a try in a fresh project—does that 25-file limit feel manageable for the features you still want to add (like the Member portal or Qibla)?