From mobazha
Complete the first-time setup wizard for a new Mobazha store. Use after deployment to configure admin password, store name, currencies, and profile.
npx claudepluginhub mobazha/mobazha-skillsThis skill uses the workspace's default tool permissions.
Complete the first-time setup of your Mobazha store after deployment. This skill covers the Setup Wizard and onboarding flow for all store modes.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Complete the first-time setup of your Mobazha store after deployment. This skill covers the Setup Wizard and onboarding flow for all store modes.
| Mode | How You Got Here | What Happens Next |
|---|---|---|
| SaaS | Signed up at app.mobazha.org | UI-guided wizard after first login |
| VPS Standalone | Deployed via standalone-setup skill | Setup Wizard at https://<domain>/admin |
| NAT / Local | Installed via native-install skill | Setup Wizard at http://localhost/admin |
For a full comparison of access URLs, auth methods, and MCP connections across all modes, see references/access-modes.md.
For stores on the hosted platform at app.mobazha.org:
Go to app.mobazha.org and sign in with Google, GitHub, or email. No local password is needed.
After first login, the dashboard shows a guided wizard:
The wizard can be skipped and dismissed. It reappears until the store has products.
SaaS onboarding is UI-driven. Guide the user through the web interface rather than calling APIs directly. The SaaS platform uses OAuth authentication, which differs from the standalone API flow below.
After onboarding, to connect an AI agent for ongoing management, see the store-mcp-connect skill (SaaS section).
For self-hosted stores deployed on a VPS with Docker.
https://shop.example.com/adminhttp://<VPS-IP>/adminOn first visit, the system detects setup is incomplete and shows the Setup Wizard.
Check whether onboarding is complete:
GET /v1/system/setup
Response:
{
"setupComplete": false,
"completedSteps": {
"password": false,
"profile": false,
"preferences": false,
"payment": false
}
}
The first and most critical step. Until a password is set, the store is unsecured.
Via the UI: The wizard prompts for a password automatically.
Via API (AI agents can automate this):
POST /v1/system/setup
Content-Type: application/json
{
"password": "<strong-password>"
}
This endpoint is public (no auth required) and can only be called once. After the password is set, all endpoints require authentication.
Generate a strong password: at least 12 characters, mixed case, numbers, and symbols.
After setting the password, obtain a Bearer token for subsequent API calls:
POST /platform/v1/auth/tokens
Content-Type: application/json
{
"username": "admin",
"password": "<your-password>"
}
Use the returned token for all subsequent requests:
Authorization: Bearer <token>
Set your store's identity — name, description, and avatar.
PUT /v1/profiles
Content-Type: application/json
Authorization: Bearer <token>
{
"name": "My Store",
"shortDescription": "A brief tagline for your store",
"about": "Longer description about what you sell and your story",
"avatarHashes": {
"small": "<image-hash>",
"medium": "<image-hash>"
},
"vendor": true
}
To upload an avatar image first:
POST /v1/media
Content-Type: application/json
Authorization: Bearer <token>
[{ "image": "<base64-image-data>", "filename": "avatar.jpg" }]
Set your country and display currency for pricing.
PUT /v1/settings
Content-Type: application/json
Authorization: Bearer <token>
{
"country": "US",
"localCurrency": "USD"
}
Common country/currency pairs:
| Country | Code | Currency |
|---|---|---|
| United States | US | USD |
| United Kingdom | GB | GBP |
| European Union | DE/FR/etc. | EUR |
| Japan | JP | JPY |
| China | CN | CNY |
| Canada | CA | CAD |
| Australia | AU | AUD |
After completing steps 1-3, GET /v1/system/setup will return setupComplete: true. The dashboard is now accessible.
Recommended next steps (tell the user about these):
/admin/settings/payments to enable crypto wallets and/or fiat providers (Stripe, PayPal)/admin/products/new to create a listing/admin/settings/storefront to adjust theme and brandingsubdomain-bot-config skillstore-mcp-connect skill to let your AI agent manage the store directlyFor stores running on your local machine (native binary or Docker without a public IP).
http://localhost/adminhttp://<your-local-ip>/admin (e.g., http://192.168.1.100/admin)If using the native binary with a custom gateway port:
http://localhost:5102 (default for native)http://localhost (default port 80)The Setup Wizard is identical to VPS Standalone mode (Steps 1-4 above). The only differences:
localhost or LAN IPhttp://localhost:5102/platform/v1/mcp/ssetor-browsing skill for .onion accessThe password was already set. Use your existing credentials to obtain a Bearer token and proceed with profile and settings.
For Docker standalone stores:
cd /opt/mobazha
docker compose exec mobazha mobazha reset-password
For native binary:
mobazha reset-password
Verify all required steps via GET /v1/system/setup. The profile step requires a non-empty store name. Check that the profile was saved successfully.
localhost (check with ip addr or ifconfig)mobazha status or docker compose ps)