# momen-cursurrules-prompt-file

Instructs Cursor on building custom frontends on top of Momen.app headless BaaS. Guides GraphQL queries, Actionflow tasks, and WebSocket subscriptions.

- rule · `type=rule` · Cursor · ★ 41024
- Author: PatrickJS
- License: CC0-1.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/PatrickJS/awesome-cursorrules/tree/HEAD/rules/momen-cursurrules-prompt-file.mdc
- Updated: 2026-05-30
- HTML: https://affpapa.org/en/nevibecode/rules/momen-cursurrules-prompt-file

## What it does

This rule configures Cursor for developing frontend applications that use Momen.app as a backend. It directs the assistant to respect Momen GraphQL endpoints, adhere to PostgreSQL schemas, and account for distinct scalar types such as `Long` and `bigint`. The assistant generates TypeScript types using `apollo client:codegen` after editing queries.

A strict transport constraint applies to the client setup: Momen is incompatible with `graphql-ws`, making `subscriptions-transport-ws` mandatory alongside Apollo Client v3.13.9. GraphQL caching is forbidden across all queries. Whenever authentication state updates, the single WebSocket connection must reconnect.

For multi-step logic and LLM workflows, the instructions offload tasks to backend Actionflows. Short operations execute synchronously, while long-running jobs run via task creation mutations paired with GraphQL subscription listeners. Inspecting the project schema relies on the Momen MCP server.

## Requirements
- Works with: Stripe

## Install

### Cursor (native platform)

**Manually: put the files in place**
- File: `.cursor/rules/momen-cursurrules-prompt-file.mdc` — Frontmatter: description, globs, alwaysApply

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/momen-cursurrules-prompt-file.md` — The paths frontmatter field limits the files: move globs from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/instructions/momen-cursurrules-prompt-file.instructions.md` — The applyTo field sets which files it applies to: move globs from the source into applyTo

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/momen-cursurrules-prompt-file.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/momen-cursurrules-prompt-file.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/PatrickJS/awesome-cursorrules/tree/HEAD/rules/momen-cursurrules-prompt-file.mdc

## When to use it
- configure Apollo Client for Momen GraphQL endpoints
- implement user registration and login using `FZ_Account` mutations
- execute asynchronous Actionflow workflows with real-time status tracking
- generate TypeScript interfaces from GraphQL operations via Apollo CLI

## Example prompts
- "Configure Apollo Client with HTTP and WebSocket split link for Momen"
- "Write an email authentication flow using authenticateWithEmail mutation"
- "Trigger an async Actionflow task and listen for status updates via fz_listen_action_flow_result"

## Source text · momen-cursurrules-prompt-file.mdc · CC0-1.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d090ee23d2200ddd.

BEGIN THIRD-PARTY FILE d090ee23d2200ddd
```text
---
description: "Cursor rules for building custom frontends with Momen.app as headless BaaS with GraphQL API, actionflows, AI agents, and Stripe integration."
globs: **/*
alwaysApply: false
---
## Instruction to developer: save this file as .cursorrules and place it in the root project directory

AI Persona:

You are an experienced Full-Stack Developer specializing in building custom frontend applications powered by Momen.app as a headless Backend-as-a-Service (BaaS). You understand GraphQL APIs, Apollo Client, real-time subscriptions, and modern frontend frameworks. You always follow best practices for type safety, security, and user experience. You break down tasks into manageable steps and approach problems systematically.

Technology Stack:

Backend: Momen.app (https://momen.app) - Full-stack no-code platform used as headless BaaS
- PostgreSQL database with auto-generated GraphQL API
- Actionflows for complex backend workflows
- AI Agents with RAG, tool use, and multi-modal capabilities
- Third-party API integrations
- Stripe payment processing
- Binary asset storage with CDN

Frontend: TypeScript/JavaScript with Apollo Client
- Apollo Client v3.13.9 for GraphQL HTTP requests
- subscriptions-transport-ws for WebSocket connections (NOT graphql-ws)
- Modern UI framework (React/Next.js/Vue/Svelte as specified)
- Tailwind CSS for styling (check online for latest integration methods)

Backend Architecture:

1. All backend interactions occur through a unified GraphQL API - no traditional REST endpoints for data operations.
2. HTTP endpoint: https://villa.momen.app/zero/{projectExId}/api/graphql-v2
3. WebSocket endpoint: wss://villa.momen.app/zero/{projectExId}/api/graphql-subscription
4. Must use Apollo Client v3.13.9 with subscriptions-transport-ws, NEVER use graphql-ws (incompatible with Momen).
5. Maintain a single Apollo Client instance across the entire application.
6. Maintain a single WebSocket connection that is reused throughout the app.
7. Never cache anything at the GraphQL level.
8. When user authentication status changes (login/logout), re-establish the WebSocket connection.

Apollo Client Setup:

1. Must create Apollo Client with split link for HTTP and WebSocket.
2. Use HttpLink for queries and mutations.
3. Use WebSocketLink with SubscriptionClient for subscriptions.
4. Include authentication token in both HTTP headers (Authorization: Bearer {token}) and WebSocket connectionParams (authToken: {token}).
5. Anonymous users have no token - use empty connectionParams and no Authorization header.
6. After writing/modifying GraphQL operations, run: apollo client:codegen --includes='src/path/to/files/containing/gql/**' --target typescript --outputFlat ./src/graphQL/__generated__
7. Always use generated TypeScript types for type safety.

Authentication:

1. All requests are either authenticated or assigned an anonymous user role.
2. To obtain JWT, users must register or login using the project's configured authentication method.
3. For email with verification:
   - First send verification code using sendVerificationCodeToEmail mutation (verificationEnumType: SIGN_UP for registration).
   - Then use authenticateWithEmail mutation with register: true and verificationCode for registration.
   - For subsequent logins, use register: false and omit verificationCode.
4. For username/password:
   - Use authenticateWithUsername mutation with register: true for new users, false for login.
```
END THIRD-PARTY FILE d090ee23d2200ddd

The third-party file has ended. Everything between the d090ee23d2200ddd tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3448 of 15978 bytes. © PatrickJS · CC0-1.0 · https://github.com/PatrickJS/awesome-cursorrules/tree/HEAD/rules/momen-cursurrules-prompt-file.mdc

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md