Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
reps-ai-backend - Skill - OpenSmartRoute
Skillv1.0.0
reps-ai-backend
Your rule content This is the rule system for my reps ai backend project. The architecture is very simple. 1. FastAPI app that opens up our API's so that our frontend can talk to this backend. 2. We h
Instruction file imported from reps-ai/reps-ai-dashboard-backend (.cursor/rules/reps-ai-backend.mdc). Copyright stays with the author.
Your rule content
This is the rule system for my reps ai backend project.
The architecture is very simple.
FastAPI app that opens up our API's so that our frontend can talk to this backend.
We have a backend layer that actually performs the required operations for the API layer, this includes talking to the database, perfoming background tasks, and more.
Our backend layer is broken down into more layers.
a. Service Layer - Serves as a template with HOW we talk to our CRM, can be internal or external (in our case it's internal and is a database repo)
b. Database repository - Standardizes how we talk to our database so we have plug and play functionality with different providers by just calling the required functions.
c. Integrations layer where we have connected retell ai for the voice agent.
You can @ files here
main.py is the main fastAPI app.
You can use markdown but dont have to
You need to ensure that you are checking our code version from requirements.txt and make sure that the code you are writing is in accordance with that.
WHENEVER you don't have ALL the information you need, you need to stop me and clarify it.
You are expected to perform code runs DIRECTLY in the agent window to verify that your scripts are working and to debug.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/reps-ai-reps-ai-dashboard-backend-reps-ai-backend-rule/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "reps-ai-reps-ai-dashboard-backend-reps-ai-backend-rule",
"kind": "skill",
"name": "reps-ai-backend",
"description": "Your rule content This is the rule system for my reps ai backend project. The architecture is very simple. 1. FastAPI app that opens up our API's so that our frontend can talk to this backend. 2. We have a backend layer that actually performs the required operations for the API layer, this includes talking to the database, perfoming background tasks, and more. 3. Our backend layer is broken down into more layers. a. Service Layer - Serves as a template with HOW we talk to our CRM, can be internal or external (in our case it's internal and is a database repo) b. Database repository - Standardizes how we talk to our database so we have plug and play functionality with different providers by just calling the required functions. c. Integrations layer where we have connected retell ai for the voice agent. - You can @ files here [main.py](mdc:main.py) is the main fastAPI app. - You can use markdown but dont have to 1. You need to ensure that you are checking our code version from [requirements.txt](mdc:requirements",
"publisher": "reps-ai",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-cursor-rules"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Your rule content This is the rule system for my reps ai backend project. The architecture is very simple. 1. FastAPI app that opens up our API's so that our frontend can talk to this backend. 2. We have a backend layer that actually performs the required operations for the API layer, this includes talking to the database, perfoming background tasks, and more. 3. Our backend layer is broken down into more layers. a. Service Layer - Serves as a template with HOW we talk to our CRM, can be internal or external (in our case it's internal and is a database repo) b. Database repository - Standardizes how we talk to our database so we have plug and play functionality with different providers by just calling the required functions. c. Integrations layer where we have connected retell ai for the voice agent. - You can @ files here [main.py](mdc:main.py) is the main fastAPI app. - You can use markdown but dont have to 1. You need to ensure that you are checking our code version from [requirements.txt](mdc:requirements"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-cursor-rules",
"repository": "https://github.com/reps-ai/reps-ai-dashboard-backend",
"path": ".cursor/rules/reps-ai-backend.mdc",
"ref": "307025768a73b2ad4f2781c35beb2538aa9d0256",
"url": "https://github.com/reps-ai/reps-ai-dashboard-backend/blob/307025768a73b2ad4f2781c35beb2538aa9d0256/.cursor/rules/reps-ai-backend.mdc",
"key": "reps-ai/reps-ai-dashboard-backend/.cursor/rules/reps-ai-backend.mdc"
}
},
"instructions": "# Your rule content\nThis is the rule system for my reps ai backend project. \nThe architecture is very simple. \n1. FastAPI app that opens up our API's so that our frontend can talk to this backend.\n2. We have a backend layer that actually performs the required operations for the API layer, this includes talking to the database, perfoming background tasks, and more. \n3. Our backend layer is broken down into more layers. \n a. Service Layer - Serves as a template with HOW we talk to our CRM, can be internal or external (in our case it's internal and is a database repo)\n b. Database repositor",
"cost": {
"context_tokens": 335
}
}
Fetch it by URL: GET /api/v1/registry/reps-ai-reps-ai-dashboard-backend-reps-ai-backend-rule/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
