# Require LLM-generated themes & plugins to be tagged as such

**URL:** https://meta.discourse.org/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871
**Category:** Site feedback
**Created:** [September 20, 2026, 7:27pm UTC](https://meta.discourse.org/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871 "2026-09-20T19:27:15Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [September 20, 2026, 7:48pm UTC](https://meta.discourse.org/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871/2 "2026-09-20T19:48:18Z")

</div>

> [@darkpixlz](#):
>
> low-quality plugin with many performance/optimization/UX problems that LLM plugins have

I disagree with the notion that an LLM-generated plugin is inherently low-quality or necessarily suffers from performance, optimization, or UX issues. The quality of the result depends heavily on the person guiding the LLM and reviewing its output.

I’ve taken pride in the software I’ve developed over the past 40 years, and incorporating LLMs into my workflow has improved the quality of my work, not diminished it.

Conversely, I’ve seen plenty of hand-written plugins riddled with security vulnerabilities, performance issues, and poor design decisions, where I genuinely wished the author had used an LLM. Ultimately, it’s the quality of the developer and the resulting code that matters, not whether an LLM was involved in writing it.

---

_[View the full topic](https://meta.discourse.org/t/require-llm-generated-themes-plugins-to-be-tagged-as-such/412871)._