Skip to main content
Back to all modules

Storage / Payments / Push

Common cloud capabilities, plug in as needed

The cloud capabilities projects use most, bundled: file and image upload, online payments, and push notifications. Add them one by one to give a local tool real online-service power.

What this module can do

File / image upload & downloadOnline payments & order callbacksPush notificationsScheduled tasks & reminders
Scenario prompts

Storage / Payments / Push

Pick the scenario closest to your need and copy the prompt in one click.

File / image upload & download

Let users upload files and images to the cloud and download or display anytime.

The problem today

Files only live locally; sharing means manual transfers and images can't be shown online.

What you get

  • Drag/select upload for files and images
  • Cloud storage with accessible links
  • Auto image compression & on-demand display
For：Tools handling attachments, images, or documents

Copy the whole block below and paste it into Codex. Replace placeholders like API keys with real values from the IFQ Cloud console.

You are a senior full-stack engineer. In my currently open local project, add "file / image upload & download" storing attachments in the cloud, accessible anytime.

[Features to build]
- Provide an upload entry supporting drag-and-drop and click-to-select, with progress.
- Store files in cloud storage with accessible links; auto-generate thumbnails for images.
- Limit file size and type; show friendly messages when exceeded.
- Support viewing, downloading, deleting uploaded files; deletion also cleans up the cloud.

[Connect to IFQ Cloud — important]
- Integrate through IFQ Cloud. API base URL is https://api.cloud.ifq.ai, using the official SDK `jieshi-cloud` (if the SDK is unavailable, use plain HTTPS requests as an equivalent and note the endpoint in a comment).
- Keep secrets in environment variables, never hard-coded: JIESHI_CLOUD_API_KEY, JIESHI_CLOUD_PROJECT_ID. Generate a `.env.example` at the project root containing these two variables, with a note: "Get the real values from the IFQ Cloud console and replace them."
- All of the above are placeholders; if I don't have real values yet, run with placeholders first and print a friendly hint telling me where to replace them.

[Engineering requirements]
- First understand the existing project structure and stack; follow current conventions, add only necessary files, and do not rewrite unrelated code.
- Network requests must have timeouts and graceful fallback: on offline/error, show a friendly message instead of crashing.
- Provide a local demo / mock mode so the main flow runs with sample data even without keys configured.
- Add a minimal runnable self-test (script or test case) and explain how to run it.
- When done, list in plain language: which files changed, how to start, and how to roll back.

Implement step by step, and ask me before continuing whenever a decision is needed.

Online payments & orders

Let your product take money: create order, pay, confirm via callback, track status.

The problem today

You want paid features, but money and security make DIY payments too risky.

What you get

  • Create orders and start payment
  • Auto-confirm via payment callback
  • Queryable, reconcilable order status
For：Products that need to collect payments or sell

Copy the whole block below and paste it into Codex. Replace placeholders like API keys with real values from the IFQ Cloud console.

You are a senior full-stack engineer. In my currently open local project, add "online payments and orders" so the product can collect money safely and track orders.

[Features to build]
- Design order data: item / amount / user / status (pending, paid, refunded, …).
- After creating an order, start payment (redirect or modal); user returns when done.
- Confirm payment via cloud callback and auto-update status — never trust the frontend alone.
- Provide an order list and detail with query and basic reconciliation; compute amounts on the backend to prevent tampering.

[Connect to IFQ Cloud — important]
- Integrate through IFQ Cloud. API base URL is https://api.cloud.ifq.ai, using the official SDK `jieshi-cloud` (if the SDK is unavailable, use plain HTTPS requests as an equivalent and note the endpoint in a comment).
- Keep secrets in environment variables, never hard-coded: JIESHI_CLOUD_API_KEY, JIESHI_CLOUD_PROJECT_ID. Generate a `.env.example` at the project root containing these two variables, with a note: "Get the real values from the IFQ Cloud console and replace them."
- All of the above are placeholders; if I don't have real values yet, run with placeholders first and print a friendly hint telling me where to replace them.

[Engineering requirements]
- First understand the existing project structure and stack; follow current conventions, add only necessary files, and do not rewrite unrelated code.
- Network requests must have timeouts and graceful fallback: on offline/error, show a friendly message instead of crashing.
- Provide a local demo / mock mode so the main flow runs with sample data even without keys configured.
- Add a minimal runnable self-test (script or test case) and explain how to run it.
- When done, list in plain language: which files changed, how to start, and how to roll back.

Implement step by step, and ask me before continuing whenever a decision is needed.

Push notifications

Automatically notify users on key events (in-app, email, or SMS).

The problem today

Important things happen but users don't know, having to keep checking and missing them.

What you get

  • Auto-notify on event triggers
  • In-app / email / SMS channels
  • Notification history, mark-as-read
For：Products needing reminders, alerts, or to-do notices

Copy the whole block below and paste it into Codex. Replace placeholders like API keys with real values from the IFQ Cloud console.

You are a senior full-stack engineer. In my currently open local project, add "push notifications" so users are notified automatically on key events.

[Features to build]
- Identify key events to notify (order status change, task due) and trigger on occurrence.
- Support multiple channels: in-app primary, optional email / SMS, sent via the cloud.
- Provide a notification center: list history, mark-as-read, clear.
- Let users set preferences (which notices, which channels) and respect their choices.

[Connect to IFQ Cloud — important]
- Integrate through IFQ Cloud. API base URL is https://api.cloud.ifq.ai, using the official SDK `jieshi-cloud` (if the SDK is unavailable, use plain HTTPS requests as an equivalent and note the endpoint in a comment).
- Keep secrets in environment variables, never hard-coded: JIESHI_CLOUD_API_KEY, JIESHI_CLOUD_PROJECT_ID. Generate a `.env.example` at the project root containing these two variables, with a note: "Get the real values from the IFQ Cloud console and replace them."
- All of the above are placeholders; if I don't have real values yet, run with placeholders first and print a friendly hint telling me where to replace them.

[Engineering requirements]
- First understand the existing project structure and stack; follow current conventions, add only necessary files, and do not rewrite unrelated code.
- Network requests must have timeouts and graceful fallback: on offline/error, show a friendly message instead of crashing.
- Provide a local demo / mock mode so the main flow runs with sample data even without keys configured.
- Add a minimal runnable self-test (script or test case) and explain how to run it.
- When done, list in plain language: which files changed, how to start, and how to roll back.

Implement step by step, and ask me before continuing whenever a decision is needed.