> For the complete documentation index, see [llms.txt](https://docs.kinwall.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinwall.family/using-kinwall/chores.md). # Chores ![Chores on the wall iPad, with leaderboard and streaks](https://4251322152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2kP7ksVUPkKNBdqDQdkp%2Fuploads%2Fgit-blob-f9aaea62c9ae2b97ccb387d3544a15eec50b7e55%2Fipad-chores.png?alt=media) The Chores tab shows one column per family member plus **🌟 Anyone**. Each column has a progress ring, a "*N* pts today" total and that day's chore cards. On phones, members with nothing due are listed on one line ("Nothing due: Leo") instead of showing as empty cards. ## Completing chores * **Tap** a card to mark it done (with a check and a small confetti burst). Tap again to undo. * A **date strip** lets you look at 4 days back and 9 days ahead. You can complete chores for any day shown. * Completing a chore credits the chore's assignee. An **Anyone** chore is recorded without a member. * To edit a chore, **press and hold** (half a second), right-click, or tab to it and use its **Edit** button. ## Creating and editing Tap **+** (Add chore). The sheet has: | Field | Notes | | ---------------------------------- | --------------------------------------------------------------------------------------------------------- | | **Title**, **Emoji** | | | **Points** | A whole number. | | **Assign to** | **🌟 Anyone** or one member. | | **Repeat** | **Once**, **Daily** or **Weekly**. | | **On** (Weekly) | Pick weekdays. With none picked, it repeats on the weekday it was created. A new chore pre-selects today. | | **Ends (optional)** (Daily/Weekly) | The last date it's due. It's stored as `UNTIL` in the rule. | | **Due date** (Once) | The day a one-off chore is due. | | **Checklist (optional)** | A list that has to be fully ticked before the chore can be completed. See below. | Chores created through the API or MCP can use any RRULE (for example `FREQ=MONTHLY` or `INTERVAL=2`). The sheet shows those as "Custom schedule (…)" and leaves them alone unless you pick another option. A recurring chore without a due date starts on the day it was created, in the household timezone. **Delete** removes the chore along with its history and points. ## Checklists A chore can carry a **checklist**: one of your [lists](/using-kinwall/lists.md) (any kind, but a **reusable** list is the natural fit — "Bedtime routine: pick out clothes, shower, pajamas, brush teeth"). The chore card shows the progress (`☑ 2/4 Bedtime`), and tapping it while items are still open opens the checklist right there in a sheet instead of completing the chore. Its **Complete** button unlocks once every item is ticked; a reusable checklist then resets to unticked, ready for the next time the chore comes round. Other list kinds are left as they are. **One list, several members.** A chore's checklist is the list's items **assigned to the chore's member, plus the unassigned ones** (a chore for *Anyone* sees the whole list). So one "Bedtime" list can back June's and Maggie's bedtime chores: give each kid their own "Shower" and "Brush teeth" items (the item's owner, in the item sheet), and leave genuinely shared steps like "Turn off the hall light" unassigned. Ticks land on the list itself, so an unassigned item ticked by one child is ticked for the other too; per-child steps stay separate. Completing the chore resets only that member's items and the shared ones. Steps added from the chore's sheet are assigned to its member. **Edit the list** at the bottom of the sheet opens the full list (reorder, notes, sub-steps). Via the API: `listId` on `POST/PATCH /api/chores`, `checklist` progress on `GET /api/chores/day`, and `POST /api/chores/{id}/complete` answers **409** with `remaining` while items are open. MCP: the `list` argument on `create_chore` / `update_chore`. ## Points, late completion credit Points are fixed at the moment you tick a chore off. Changing a chore's points later doesn't rewrite history. * Completed **on its day, or early**: full points. * Completed **for a past day**: `lateCompletionCredit` percent of the points, rounded. The default is **50%** (0–100). * Re-ticking an existing completion (for example, to change who did it) keeps the points it already earned. ## Streaks and grace days A member's 🔥 streak counts consecutive days on which **every chore assigned to them and due that day** was completed. * Days with nothing due are skipped. They don't break the streak. * Today only counts once its chores are done. * `streakGraceDays` (0–3, default **1**): a streak survives that many missed days in any rolling 7 days. Set it to 0 for the strict rule, where any miss ends the streak. * Streaks look back at most 60 days. 🔥*N* shows from 2 days up. ## Leaderboard Above the columns, a leaderboard ranks members by points for **Today**, **Week** or **Month**. The period is remembered per device, and the week follows the household week start. * Ranking is by points, then completions, then name. Members with equal points and completions share a rank. * The leader gets 👑 (bouncing when the lead changes). Members with no activity still appear. * `leaderboardEnabled` (default on): turn it off for families that prefer no competition. Apps then hide the leaderboard and rank badges. The API still answers. ## Points to spend Points are also a currency. A member's **balance** is every point they've ever earned from chores, minus what they've spent in the [sticker shop](/using-kinwall/activities.md#sticker-book). * The leaderboard and the member's today/week points always count what was **earned**. Spending never lowers a rank. * With the sticker shop on, each leaderboard pill also shows the balance, such as "22 to spend". * Spending is recorded in a points ledger. `GET /api/members/{id}/points` returns `{ balance, earnedTotal, spentTotal, entries }`, with the last 50 ledger entries. The member list (`GET /api/members`) includes `balance` too. * Unticking a completed chore takes its points back out of the balance. So does deleting a chore, since its completion history goes with it. A balance can end up below zero that way. New purchases then wait until it's back up. * **Settings → Family → Chores** has **Sticker shop** (on/off) and **Sticker prices** (Free, 50%, 100% or 150%). ## Setting these options `lateCompletionCredit`, `streakGraceDays`, `leaderboardEnabled`, `stickersEnabled` and `stickerPriceScale` are household settings. Change them with `PATCH /api/settings`: ```bash curl -X PATCH https://kinwall.example/api/settings -H "Authorization: Bearer $KEY" \ -H "Content-Type: application/json" -d '{"lateCompletionCredit":100,"streakGraceDays":0,"leaderboardEnabled":false}' ``` They're included in [export and import](/your-data/export-import.md). ## Notifications A per-device **Chore reminder** at a set time lists chores still open today for the members that device follows. See [Notifications](/using-kinwall/notifications.md). ## API and MCP * `GET /api/chores/day?date=YYYY-MM-DD`, `POST /api/chores/{id}/complete {date, memberId?}`, `DELETE /api/chores/{id}/complete?date=` * `GET /api/leaderboard?period=today|week|month` * `GET /api/members/{id}/points` * MCP: `list_chores`, `create_chore`, `update_chore`, `complete_chore`, `uncomplete_chore`, `get_leaderboard`, `get_points` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kinwall.family/using-kinwall/chores.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.