Ulas
1122bd269b
Replace all — with - in all source files (JS, CSS, HTML, JSON, Markdown) for consistency and readability. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
47 lines
1.0 KiB
Markdown
47 lines
1.0 KiB
Markdown
---
|
|
name: Feature Request
|
|
about: Suggest a new feature or improvement
|
|
title: "[Feature] "
|
|
labels: enhancement
|
|
assignees: ''
|
|
---
|
|
|
|
## Problem
|
|
|
|
What problem does this solve? Describe the use case from a family member's perspective.
|
|
|
|
## Proposed Solution
|
|
|
|
How do you envision this working? Be as specific as you like - UI sketch, API shape, interaction flow.
|
|
|
|
## Alternatives Considered
|
|
|
|
Have you considered other approaches? Why is this one better?
|
|
|
|
## Scope
|
|
|
|
Does this fit within an existing module, or would it require a new one?
|
|
|
|
- [ ] Dashboard
|
|
- [ ] Tasks
|
|
- [ ] Shopping
|
|
- [ ] Meals
|
|
- [ ] Calendar
|
|
- [ ] Notes
|
|
- [ ] Contacts
|
|
- [ ] Budget
|
|
- [ ] Settings
|
|
- [ ] New module
|
|
|
|
## Constraints Check
|
|
|
|
Please confirm your proposal is compatible with the project's architecture:
|
|
|
|
- [ ] No frontend framework required (vanilla JS, Web Components)
|
|
- [ ] No build step required
|
|
- [ ] No new frontend dependencies (backend deps evaluated case-by-case)
|
|
|
|
## Additional Context
|
|
|
|
Mockups, screenshots from other apps, or anything else that helps illustrate the idea.
|