Stat box number format respected 🌍🔢

.claude/skills/github-issue-fixy/SKILL.md

@@ -151,25 +151,32 @@ This skill guides you through solving GitHub issues for the Home Assistant devic
 
 3. **Release notes content**:
    - **Bug fixes**: "Fixed [description] - fixes #[issue-number]"
-   - **New features**: "Added [feature name] - thanks @[username] - fixes #[issue-number]"
+   - **New features**: "Added [feature name] - fixes #[issue-number]" (or equivalent plain-language lead)
    - **Enhancements**: "Improved [description] - fixes #[issue-number]"
    - **Breaking changes**: Clearly mark with "⚠️ BREAKING CHANGE:" prefix
+   - **Do not thank contributors in release notes** — appreciation belongs in the README roadmap (Step 7), not in `RELEASE_NOTES.md`.
 
-4. **Example format**:
+4. **Tone and links**:
+   - Prefer short, user-facing copy; avoid deep technical detail (file names, internal APIs) unless necessary for migration.
+   - **Link where it helps**: [Home Assistant documentation](https://www.home-assistant.io/docs/), relevant integration pages, or this repo’s published docs (e.g. GitHub Pages) so users can go further.
+
+5. **Example format**:
 
    ```markdown
    # Hidden Entity Filtering & Dark Mode!🎉✨
 
    ## 🔍 Hidden Entity Filtering
 
-   Hidden entities are now automatically filtered out from device cards, matching Home Assistant's more-info popup behavior - thanks @warmfire540 - fixes #43
+   Hidden entities are now filtered out to match Home Assistant’s more-info behavior - fixes #43
 
    ## 🌙 Dark Mode Support
 
-   Added dark mode theme option for better visibility in low-light environments - thanks @username - fixes #123
+   Dark mode option for low-light dashboards - fixes #123
+
+   See [Home Assistant themes](https://www.home-assistant.io/integrations/frontend/) for related settings.
    ```
 
-5. **Home Assistant user-friendly language**:
+6. **Home Assistant user-friendly language**:
    - Write in clear, non-technical language
    - Focus on what users can do or what problems are solved
    - Avoid internal implementation details
@@ -231,7 +238,7 @@ Provide a summary of:
 - Ensure backward compatibility unless it's a breaking change
 - Consider Home Assistant version compatibility
 - Test with multiple browsers if UI changes are involved
-- Keep release notes user-friendly and focused on user benefits
+- **Release notes** (`RELEASE_NOTES.md`): user-facing, no contributor thanks (those go in the README roadmap); include links to Home Assistant or project docs where relevant; avoid unnecessary technical detail
 
 ## Plan Presentation Format
 
@@ -275,7 +282,7 @@ When presenting the plan, use this structure:
 ```markdown
 ## [Emoji] [Feature/Bug Name]
 
-Brief description, yaml example, doc links, etc.
+Brief description, optional YAML example, links to HA or project docs; no contributor thanks; fixes issue when applicable.
 ```
 ````
 
@@ -297,7 +304,7 @@ Brief description, yaml example, doc links, etc.
    - Files to modify: `src/cards/device-card/styles.ts`, `src/cards/device-card/types.ts`, `src/cards/device-card/editor.ts`
    - Tests: Update existing test in `test/cards/device-card/card.spec.ts` to include dark mode scenarios (prefer updating over creating new tests)
    - Documentation: Update README.md Features section, add config option to table
-   - Release notes draft: "## Dark Mode Support\n\nAdded dark mode theme option"
+   - Release notes draft: "## Dark Mode Support\n\nAdded dark mode theme option - fixes #123" (no thanks; link to HA docs if useful)
    - Roadmap draft: "- [ ] **`Dark mode support`**: Add dark mode theme option - thanks @username"
 4. **PRESENT PLAN TO USER** - Wait for approval
 5. **ONLY AFTER APPROVAL**: Implement code changes

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,109 @@
+name: Bug report
+description: Report unexpected behavior, errors, or visual problems with this custom card
+title: '[Bug] '
+type: bug
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting. **Minimal YAML** and **version info** help a lot for Lovelace cards.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What went wrong in one or two sentences?
+      placeholder: e.g. The card shows "Unknown" for entities that exist in Developer Tools.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect?
+      description: What should happen instead?
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: How can someone else see the same issue? Include dashboard/editor steps if relevant.
+      placeholder: |
+        1. Add the card with …
+        2. Open the dashboard on …
+        3. …
+    validations:
+      required: true
+
+  - type: textarea
+    id: yaml-config
+    attributes:
+      label: Card YAML (minimal)
+      description: Paste the smallest configuration that still reproduces the issue. Redact tokens, passwords, and private hostnames.
+      render: yaml
+    validations:
+      required: true
+
+  - type: input
+    id: ha-version
+    attributes:
+      label: Home Assistant version
+      description: e.g. 2029.3.1 — find in **Settings → About**.
+      placeholder: '2029.3.1'
+    validations:
+      required: true
+
+  - type: input
+    id: card-version
+    attributes:
+      label: Card / release version
+      description: Version from HACS, GitHub Releases, or your build (e.g. tag or `package.json`).
+      placeholder: e.g. 1.2.3 or commit SHA
+    validations:
+      required: true
+
+  - type: dropdown
+    id: install-source
+    attributes:
+      label: How is the card installed?
+      options:
+        - HACS
+        - Manual (GitHub release asset)
+        - Manual (built from source)
+        - Other / not sure
+    validations:
+      required: true
+
+  - type: input
+    id: browsers
+    attributes:
+      label: Browser(s) and version(s)
+      description: e.g. Safari 17, Chrome 122 — or **Home Assistant Companion app** (note OS version).
+      placeholder: Chrome 131 on macOS
+    validations:
+      required: true
+
+  - type: textarea
+    id: console
+    attributes:
+      label: Browser console / logs (optional)
+      description: Errors from **Developer Tools → Console** when the issue occurs. For the mobile app, note if only reproducible in browser.
+      render: shell
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots or screen recording (optional)
+      description: Drag images into this field or describe what you see.
+
+  - type: checkboxes
+    id: duplicates
+    attributes:
+      label: Checklist
+      options:
+        - label: I searched existing issues (open and closed) for duplicates
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Home Assistant community
+    url: https://community.home-assistant.io/
+    about: General Home Assistant help, automations, and integrations (not specific to this repository).
+  - name: Home Assistant documentation
+    url: https://www.home-assistant.io/docs/
+    about: Official docs for dashboards, Lovelace, and core concepts.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,50 @@
+name: Feature request
+description: Suggest an improvement or new capability for this custom card
+title: '[Feature] '
+type: feature
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Share the **problem or goal** first; concrete UI ideas are welcome but optional.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem or use case
+      description: What are you trying to achieve on your dashboard? What is awkward or missing today?
+      placeholder: e.g. I want to show … without maintaining a long entity list by hand.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: How could this card support that? Configuration shape, UI behavior, or integration with Home Assistant (areas, entities, etc.) — whatever helps.
+    validations:
+      required: false
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you've considered
+      description: Other cards, templates, automations, or workarounds — helps scope the request.
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: HA version if relevant, theme, mobile vs desktop, links to HA docs or related discussions.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I searched existing issues for similar requests
+          required: true

.github/ISSUE_TEMPLATE/other.yml

@@ -0,0 +1,38 @@
+name: Other
+description: Questions, documentation, releases, or anything that is not clearly a bug or feature
+title: '[Question] '
+labels:
+  - question
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this for **general questions**, **documentation**, **installation**, or **meta** topics. For **defects**, use **Bug report**; for **new behavior**, use **Feature request**.
+
+  - type: dropdown
+    id: topic
+    attributes:
+      label: Topic
+      options:
+        - Question / how-to
+        - Documentation
+        - Installation or HACS
+        - Release or versioning
+        - Contributing / development
+        - Something else
+    validations:
+      required: true
+
+  - type: textarea
+    id: details
+    attributes:
+      label: Details
+      description: What do you need? Include Home Assistant version and how you installed the card if it helps.
+    validations:
+      required: true
+
+  - type: textarea
+    id: extra
+    attributes:
+      label: Links or references (optional)
+      description: URLs to docs, forum threads, or screenshots.