You are building an app for the PMC Apps marketplace. Read every requirement before writing any code. These are platform rules — not suggestions. WHAT YOU ARE BUILDING After reading this prompt, describe your app. Name the specific PM workflow it solves, which PMS it connects to (Appley, Rentvine, or Column Bank), and what a property manager does manually today that your app will handle automatically. The more specific the better. PLATFORM Your app runs as a Node.js / Express service on Railway. It connects to the PMC platform-api for auth, credentials, and file storage. You will receive all connection details as environment variables. REQUIRED ENVIRONMENT VARIABLES These will be provided by PMC when your app is deployed. Add all of them to your .env.example file: PLATFORM_API_URL — base URL of the PMC platform-api JWT_SECRET — shared signing secret TENANT_ID — UUID of the tenant this app serves PLATFORM_SERVICE_TOKEN — static token for service-to-service calls PORT — default 3000 PROJECT STRUCTURE server/index.js — main entry point, must start with: node server/index.js package.json — all dependencies listed, start script set to node server/index.js .env.example — every required env variable listed with a description README.md — see README requirements below AUTH Every protected route must verify the JWT sent by the browser using JWT_SECRET and HS256. Verify locally — do not call platform-api on every request. Return 401 if verification fails. THIRD-PARTY CREDENTIALS Never hardcode API keys or ask users to paste them into your UI. All PMS credentials are stored in the PMC platform-api. Fetch them at app startup like this: GET {PLATFORM_API_URL}/accounts?provider={your_provider} Authorization: Bearer {PLATFORM_SERVICE_TOKEN} Cache the result in memory. If the account is missing or the call fails, show a clear setup screen explaining which account needs to be connected in PMC settings. Do not crash. FILE UPLOADS If your app handles file uploads, send them here — do not write to disk: POST {PLATFORM_API_URL}/storage/upload (multipart/form-data) Authorization: Bearer {PLATFORM_SERVICE_TOKEN} ERROR HANDLING — REQUIRED Every fetch or API call must be wrapped in try/catch. Rules: - Never show a blank screen under any error condition - If a call fails show a banner: what failed + a Retry button - Handle: API down, bad credentials, empty data, request timeout - Financial or destructive actions must show a confirmation step before executing WORKFLOW REQUIREMENT Your app must complete a full PM workflow end-to-end. The user should never have to leave your app, open another tool, or copy-paste data to finish the job. Incomplete workflows are rejected in QA. MOBILE Your app must work at 375px viewport width. Use flexbox or CSS grid with wrapping. No fixed widths wider than 100vw. All buttons and inputs at least 44px tall. AI DISCLOSURE If your app uses AI or automated decision-making, all AI-generated output must be clearly labeled. Never present AI output as authoritative fact. UI — YOUR CHOICE Design your app however you want. Use your own colors, fonts, and layout. The only UI requirements are: mobile responsive, financial confirmations before executing, no hardcoded external image URLs that could break. README REQUIREMENTS Your README.md must cover: 1. One sentence: what does this app do 2. Which PMS it connects to 3. What API permissions it needs from platform-api connected_accounts 4. All required environment variables with descriptions 5. How to run locally: npm install then node server/index.js ZIP REQUIREMENTS When submitting, compress your project folder. Include everything except: - node_modules/ - .env (your actual env file with real credentials) - Any large test data or media files Do include: all source code, package.json, README.md, .env.example

Copy prompt Open in Claude Open builder hub