Getting Started with AI Development

Get your AI tool connected to Eclipse in two steps, then run a few prompts to confirm everything is working before you start building.

Prerequisites: sandbox credentials from the Eclipse onboarding team. See Sandbox Environment if you don't have these yet.

---

Step 1 — Connect the Eclipse MCP Server

The MCP server gives your AI tool live access to Eclipse API documentation and platform context. Follow the one-time setup for your tool here: MCP Setup →

---

Step 2 — Load the Eclipse Skills

Paste this prompt into your AI tool at the start of any Eclipse development session. Fill in your sandbox credentials before sending.

Before we start, fetch each URL below and save it as a named skill file in the project's AI assistant commands directory, formatted as markdown, so it is persistent and reusable across sessions without re-fetching:
- Authentication: https://developer.eftcorp.com/docs/aiauthentication
- Customer Management: https://developer.eftcorp.com/docs/customer-management
- Wallet Management: https://developer.eftcorp.com/docs/wallet-management
- Card Management: https://developer.eftcorp.com/docs/card-management
- OpenAPI usage guide: https://developer.eftcorp.com/docs/openapi
- Admin Portal Portlets: https://developer.eftcorp.com/docs/portlets

Also load this API Reference:
https://eclipse-java-sandbox.ukheshe.rocks/openapi

My Eclipse sandbox details:
- Base URL: https://eclipse-java-sandbox.ukheshe.rocks/eclipse-conductor/
- Tenant ID: {tenantId}
- Login: {identity}
- Password: {password}

Confirm when you have loaded everything and are ready to help me build on Eclipse.

---

Test 1 — Basic: Check what's on my tenant

A simple question to confirm the MCP server is connected and returning live data.

What wallet types are available on my tenant? For each one, tell me the name,
currency, and whether it supports card issuance.

You should get a list drawn from your live tenant configuration. If the AI makes something up or says it can't access that information, check your MCP connection.

---

Test 2 — Intermediate: Look something up in the API

Confirms the OpenAPI spec is loaded and the AI is reading real field definitions rather than guessing.

I want to create a new customer via the API. What fields do I need to include in
the request body? Which ones are required, and what format does the phone number
have to be in?

The response should include the exact field names from the spec (firstName, lastName, phone1, nationalIdentityNumber, etc.) and the phone format rule (digits only, no + prefix). Any invented field names mean the spec isn't loaded.

---

Test 3 — Advanced: Build something real

Confirms the AI is generating code that will actually work against the Eclipse APIs.

Build me a standalone HTML page — single file, no build step required — that lets
me log in to my Eclipse sandbox and then shows a live list of all customers on my
tenant with their wallet balances.

Design requirements: this should look like it came out of Lovable or Linear —
premium SaaS quality. Use Inter or a similar clean sans-serif, a dark navy header,
card-based layout with subtle shadows, status badges with colour coding, and smooth
hover states throughout. No Bootstrap, no basic tables — think modern fintech dashboard.

Open the file in a browser, enter your sandbox credentials, and you should see your real customer data. This is the full loop working: MCP context + OpenAPI field names + Authentication skill + live API calls.

---

Go Further — Full Customer Onboarding Application

Once the tests pass, use this prompt to generate a complete onboarding application.

Using the Eclipse skills and OpenAPI spec you've already loaded, build a complete
standalone customer onboarding application as a single HTML file.

The application should have three sections:

1. LOGIN SCREEN
   Fields for base URL, tenant ID, identity and password.
   Authenticates with Eclipse and stores the JWT for subsequent calls.

2. CUSTOMER DASHBOARD
   A card-based grid showing all customers on the tenant.
   Each card shows the customer's name, phone, email, status, and total wallet balance.
   An "Add Customer" button opens the onboarding wizard.

3. ONBOARDING WIZARD — 4 steps with a progress bar
   Step 1: Customer details — first name, last name, phone (digits only, no +),
           email, national identity number
   Step 2: Documents — selfie photo and identity document, uploaded to Eclipse
   Step 3: KYC — automatically run identity verification when the user reaches
           this step. Show a spinner while it's in progress. If it passes, show
           a clear green success state and let the user continue. If it fails,
           show which specific checks didn't pass and block progression — the
           user cannot proceed to wallet setup until KYC is approved.
   Step 4: Wallet — show all wallet types available on the tenant as selectable
           cards. Types the customer is not eligible for are displayed but greyed
           out with a "not available" label so the user understands their options.
           The user picks an eligible type and confirms. The app creates the
           wallet and shows a success screen with the new wallet details.

Design requirements — this must look like a premium fintech product, not a tutorial:
- Inter font, dark navy (#050C43) header bar with a subtle logo mark
- Full-height sidebar layout with smooth section transitions
- Customer cards with soft shadows, avatar initials, and colour-coded status pills
- Wizard progress bar with animated step indicators and smooth slide transitions
  between steps
- Inputs with floating labels or clean labelled fields, focus rings in blue (#007AFF)
- All buttons have hover lift animations; destructive actions require a confirmation
- Skeleton loading placeholders while API calls are in flight
- Error messages surface the Eclipse traceId in a styled alert banner, not an alert()
- The overall aesthetic should match what you'd expect from Lovable, Linear, or Stripe —
  clean whitespace, precise typography, intentional colour use
All API calls go directly from the browser using the JWT. No frameworks, no build step.

Expected: a single .html file ready to open in a browser. Point it at your sandbox and it will create real customer records.

---

Something Not Working?

If the generated code doesn't behave as expected, just tell the AI what went wrong and ask it to fix it.

For example:

• "The login isn't working — I'm getting a 401 error. Fix it."
• "The customer list isn't loading. The console shows a CORS error."
• "The wallet balance is showing as undefined. Fix the display."
• "Step 3 of the wizard isn't progressing after KYC passes. Debug and fix."

---

Next Steps