Simply Family Budget

View saved version →

---
name: sfb-get-started
description: Set up Simply Family Budget after installation or when a user asks to get started, by checking existing data and guiding them through one real wallet and one real transaction.
---

Use this skill for the Simply Family Budget setup/onboarding flow.

The goal is to get the user to one useful, real result with as little setup friction as possible. Do not give a feature tour and do not ask the user to configure their whole budget.

## Start by checking the account

1. Call `get_household_overview` to learn the family's currency and timezone.
2. Call `list_wallets` for active wallets.

If active wallets already exist:
- Do not create a duplicate wallet.
- Briefly confirm that Simply Family Budget is connected and ready.
- If the user is clearly already active, do not restart onboarding.
- Offer one immediate next action, preferably adding a recent transaction or reviewing upcoming bills and projected balance.
- Keep the response short.

If there are no active wallets, continue with the new-user flow below.

## New-user flow

Explain this once, in one short sentence:

"Simply Family Budget doesn't connect to your bank or import transactions automatically — you stay in control by adding them here or in the app."

Then guide the user one question at a time.

### 1. Choose the first wallet

Ask which account they use most often:
- chequing
- credit card
- savings
- cash
- other

Then ask what they want to call it.

Then ask for its current balance.

For a credit card, distinguish the current balance from available credit or credit limit. If the user's wording could map to more than one balance value, clarify before writing. Do not ask for a credit limit during onboarding unless the user volunteers it or the tool requires it.

Once the required values are known, call `create_wallet`.

Do not invent a wallet name, balance, type, credit limit, or any other financial value.

### 2. Add one real transaction

After the wallet is created, say that the basic account is ready and ask for one recent real purchase.

A compact prompt is enough, for example:
"Tell me one recent purchase — amount, merchant or note, and the date. For example: $34 at IGA today."

For an expense:
1. Use `list_categories` with `type=expense` to resolve an appropriate existing category.
2. Prefer an obvious matching existing category when the user's wording makes the category clear.
3. If more than one category is plausible, ask the user to choose.
4. If no suitable category exists, ask whether they want to create one before calling `create_category`.
5. Use the wallet ID returned by discovery/creation; never invent IDs.
6. Call `create_transaction`.

When the user gives only a date and not a time, do not burden them with a time question. Use a reasonable local time on that date in the family's timezone so the intended local date is preserved.

Never invent an amount, merchant, date, category, or transaction.

### 3. Finish after the first success

After the first transaction is created, confirm that setup is complete. Keep the closing message short and give no more than three concrete examples of what they can do next:

- "Add $18 at Tim Hortons from Visa."
- "Show our upcoming bills and tell me if the balance looks safe."
- "How much did we spend on groceries this month?"

Do not continue into budgets, recurrences, tags, or full household configuration unless the user asks.

## Important boundaries

- Never imply that Simply Family Budget connects to a bank, imports bank transactions automatically, or moves real money.
- Never create demo or fake financial records during onboarding.
- Never overwrite or delete existing data as part of setup.
- If the user already has wallets, do not repeat the first-wallet flow.
- Ask for clarification before a write when the user's financial intent is ambiguous.
- Follow host confirmation requirements for write tools.
- If authentication is missing or expired, explain that the user needs to reconnect Simply Family Budget, then stop the write flow.

Referenced files: 1 — file references are metadata, not package contents.