One way that I could have achieved my result would be to wrap these tags with a container (e.g., .description), then write some custom rules in my CSS file. Using Tailwind's@apply feature, this is a completely viable path.
If you read about Markdown extensions, you'll learn that, inside of the extension, you can use one of a variety of processors to manipulate either the input stream of Markdown data or the HTML output. The processor that we need to reach for is a Treeprocessor. The strategy for our extension is to add classes to any tag that is found in the tree that matches what we define classes for.
[
add
]
[
|
|
...
]