Instruction file imported from MohamedTBadr/EpicHub (.cursor/rules/project-scope-and-backend.mdc). Copyright stays with the author.

Project scope and backend boundary

Name: project-scope-and-backend
Author: MohamedTBadr

The maintainer is the project lead, frontend, and business logic developer—not the backend developer.

What to change in this repo

Do: Work on the Front-End, shared frontend types/interfaces used by the UI, business logic docs or specs that live with the product (e.g. business_logic_reference.md when relevant).
Do not: Edit, refactor, or “fix” the API / backend (API/, server C#, middleware, etc.). Treat the backend as read-only from this agent’s perspective.

Backend issues

If a bug, missing endpoint, contract mismatch, or any change is needed in the backend:

Do not implement backend changes.
Summarize clearly for the backend developer: what’s wrong, expected vs actual, suggested API shape or behavior (if helpful), and file/area hints only as observation—not as edits.

Uncertainty and inconsistencies

Ask the user when something is ambiguous (API behavior, env, ownership of a file).
Surface unclear or inconsistent behavior (e.g. types vs real responses, docs vs code) so the user can align with the backend dev or product.

{ "ocm": "1", "id": "mohamedtbadr-epichub-project-scope-and-backend-rule", "kind": "skill", "name": "project-scope-and-backend", "description": "Scope (frontend + business logic only); backend is hands-off—escalate to backend dev", "publisher": "MohamedTBadr", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Scope (frontend + business logic only); backend is hands-off—escalate to backend dev" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/MohamedTBadr/EpicHub", "path": ".cursor/rules/project-scope-and-backend.mdc", "ref": "b8178b97d416416a080b99c91ea81614abc8b4c5", "url": "https://github.com/MohamedTBadr/EpicHub/blob/b8178b97d416416a080b99c91ea81614abc8b4c5/.cursor/rules/project-scope-and-backend.mdc", "key": "MohamedTBadr/EpicHub/.cursor/rules/project-scope-and-backend.mdc" } }, "instructions": "# Project scope and backend boundary\n\nThe maintainer is the **project lead**, **frontend**, and **business logic** developer—not the backend developer.\n\n## What to change in this repo\n\n- **Do**: Work on the **Front-End**, shared frontend types/interfaces used by the UI, **business logic** docs or specs that live with the product (e.g. `business_logic_reference.md` when relevant).\n- **Do not**: Edit, refactor, or “fix” the **API / backend** (`API/`, server C#, middleware, etc.). Treat the backend as read-only from this agent’s perspective.\n\n## Backend issues\n\nIf a bug, missing endpoint, contrac", "cost": { "context_tokens": 288 } }

project-scope-and-backend

About

Project scope and backend boundary

What to change in this repo

Backend issues

Uncertainty and inconsistencies

Use it

Manifest

Reviews