Riddy21 / Riddy21/Friday_Budgeting_Pro
[Future] UI parity for every MCP action
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Long-term goal: every MCP tool we have should be doable from the UI as well, so the system is fully usable without an LLM if the user prefers click-and-type.
Scope (post-v0.1):
- Sync button on dashboard \u2192 calls
sync() - Manual transaction routing UI (list of pending review, drop-down + split UI)
- Hint management (CRUD page for classification hints)
- Routing rule management (view/edit/delete auto-promoted rules)
- Excel export trigger button
- Sandbox-vs-production indicator + switcher (admin only)
- Audit log viewer for auto-promoted rules
Why later: v0.1 keeps the UI minimal (Linked Accounts, Ledgers, Profile, Dashboard placeholder). Once those land and we know the patterns, scaling up is cheap.
Depends on: v0.1 UI (#14, #37, #46\u2013#49)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the v0.1 UI work in issues #14, #37, and #46–#49 first, since this work depends on those patterns. Use the listed MCP actions as the scope: sync, transaction routing, hint and rule management, Excel export, environment switching, and audit logs. Done means each action is available through the UI, including the stated admin-only restriction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100