Menu
Use when you need to convert / rewrite existing HTML (from a file or url) into Jaspr code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | jaspr-convert-html |
| description | Use when you need to convert / rewrite existing HTML (from a file or url) into Jaspr code. |
| metadata | {"jaspr_version":"0.23.1"} |
Converting existing HTML into Jaspr component syntax by hand is prone to errors and wastes time.
jaspr convert-html command to convert existing HTML.To convert HTML to Jaspr code, run one of the following commands in the terminal depending on your source:
From a local file:
jaspr convert-html --file some/path/to/file.html
From a URL:
jaspr convert-html --url https://example.com
The resulting Jaspr code is printed directly to the console. You can then copy this code directly into your component's build method.
If you only need a portion of the HTML, you MUST use the --query option with a CSS selector to target specific elements rather than converting the whole file and deleting pieces manually.
jaspr convert-html --file some/path/to/file.html --query "#my-id"
This will only convert and output the element with the id my-id.
Tip: To convert everything inside the <body> tag but exclude the <body> tag itself, use:
jaspr convert-html --file some/path/to/file.html --query "body > *"
Highly optimized Flutter UI bindings and GPU rendering for reactive signals.
Comprehensive hook utility functions integrating reactive signals seamlessly with flutter_hooks.
Comprehensive reactive state hooks for integration with flutter_hooks.
Standardized compiler diagnostics, static analysis lints, and automated IDE quick-fixes.
Use when working in a Jaspr project, on Jaspr components, or other Jaspr-related tasks. Contains fundamentals of writing Jaspr components and using HTML components.
Effectively integrate with Javascript when building Jaspr web applications. Use this skill when wrapping an existing JS library, accessing browser-native APIs, or bridging code safely across environments.