Skip to content
TrustedSkillsbeta
Back to all skills

Converting Html Css To Wpf Xaml

Checked
christian289·vlatest·frontend·MIT

Transforms HTML/CSS web designs into functional WPF XAML code for Windows applications.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add christian289/dotnet-with-claudecode --skill converting-html-css-to-wpf-xaml -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

christian289

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned christian289/dotnet-with-claudecode at 0ac6c06f0c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
8 files, 1,050 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill converts HTML and CSS code into WPF XAML. It allows for the translation of web-based designs into a Windows Presentation Foundation (WPF) application interface. The conversion aims to replicate the visual appearance and layout defined in the original HTML/CSS.

When to use it

  • You have an existing website design you want to integrate into a WPF desktop application.
  • You need to quickly prototype a WPF user interface based on established web designs.
  • You're migrating a web-based project to a Windows desktop environment and require UI conversion.
  • You are creating custom controls for a WPF application that mirror the styling of existing HTML/CSS components.

Key capabilities

  • HTML to XAML conversion
  • CSS to XAML style translation
  • Replication of visual appearance and layout
  • WPF application interface generation

Example prompts

  • "Convert this HTML and CSS into WPF XAML: [paste HTML and CSS code]"
  • "Translate the following web design (HTML/CSS) into a WPF user interface."
  • “Create a WPF control based on this HTML structure and CSS styling.”

Tips & gotchas

  • The conversion may require manual adjustments to ensure perfect fidelity due to differences between web technologies and WPF.
  • Complex CSS features or advanced JavaScript interactions might not translate directly and need custom implementation in XAML/C#.