collecting-wpf-dev-pack-feedback

Solid

Analyzes the current WPF working session and produces an accumulable wpf-dev-pack improvement-feedback markdown file in the current directory. Use when, after doing WPF work with wpf-dev-pack skills/scaffolders in a project OUTSIDE the dotnet-with-claudecode repo, you want to capture anti-patterns you hand-fixed, missing or outdated skill guidance, mistaken or missed triggers, and scaffolder gaps — without editing wpf-dev-pack directly. The output md is meant to be contributed to dotnet-with-claudecode/FeedbackDocs via a pull request.

Data & Documents 40 stars 6 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
40
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Collecting wpf-dev-pack Feedback This skill turns lessons learned in the current WPF session into a structured improvement-feedback document for the `wpf-dev-pack` plugin. It does NOT modify `wpf-dev-pack` and does NOT touch git — it only writes one markdown file to the current working directory, which the user later contributes via pull request. ## Why this exists WPF work happens in projects OUTSIDE the `dotnet-with-claudecode` repository, and that repo's local clone path differs per machine. Editing `wpf-dev-pack` from a foreign session is infeasible, so improvements are captured as an accumulable md and contributed separately (see the repo CONTRIBUTING guide). ## Anonymity policy (MANDATORY) The feedback document is a reusable artifact contributed across projects. It must describe the technical phenomenon and its causal chain only. The following content is PROHIBITED in any feedback document produced by this skill: - Project, solution, repository, product, or codename - Team, developer, or user name; email; account handle - Date or time of when the issue was encountered - Absolute or repo-relative file paths from the originating codebase - Class, namespace, or member names that are unique to the originating project (use generic placeholders such as `XxxView`, `XxxViewModel`, `XxxService`) - Any other detail that can identify the originating project or person Public framework / library / API names (e.g., `HelixToolkit`, `ScottPlot`, `CommunityToolkit.Mvvm`, `Pri...

Details

Author
christian289
Repository
christian289/dotnet-with-claudecode
Created
7 months ago
Last Updated
6 days ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category