MannyFlussMannyFluss/claude-skills/new-plasmoid/SKILL.md

new-plasmoid

Skill0 starsChanged 7 months agoMITView on GitHub

Scaffolds and builds KDE Plasma 6 widgets (plasmoids) for Manny's desktop. Handles pure QML widgets, WebEngineView visualizations, HTTP daemon widgets, and WebSocket wrappers. Use when the user asks to create a new widget, plasmoid, or desktop visualizer, or wants to add something to the KDE desktop.

In this repository28 other files it gives its agents.
- bootstrapSkill
- build-alignmentSkill
- decompose-issueSkill
- deploySkill
- design-an-interfaceSkill
- draft-a-godot-frontend-sceneSkill
- edit-articleSkill
- explore-realitySkill
- git-guardrails-claude-codeSkill
- grill-meSkill
- implement-issueSkill
- improve-codebase-architectureSkill
- insightSkill
- integrate-godot-frontend-sceneSkill
- learn-itSkill
- migrate-to-shoehornSkill
- obsidian-vaultSkill
- prd-to-godot-frontendSkill
- prd-to-issuesSkill
- prd-to-planSkill
- request-refactor-planSkill
- scaffold-exercisesSkill
- setup-pre-commitSkill
- tddSkill
- triage-issueSkill
- ubiquitous-languageSkill
- write-a-prdSkill
- write-a-skillSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Always create these files:
line 29
Distinctive:
If it crashes with no output, the most common causes are:
line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

New Plasmoid

Key paths

Plasmoids: ~/.local/share/plasma/plasmoids/
Base library: ~/.local/share/plasma/plasmoids/com.manny.base/
Base scripts: ~/.local/share/plasma/plasmoids/com.manny.base/scripts/
Projects: ~/projects/
Test command: plasmawindowed com.manny.<name>
Reload all: kquitapp6 plasmashell && kstart6 plasmashell
Naming: always com.manny.<name>

Step 1 — Pick the widget type

Situation	Type
Shows text/data, polls every few seconds	Pure QML
Needs shell commands to get data	Pure QML + P5Support
Needs GPU rendering, animations, Canvas2D/WebGL	WebEngineView
Needs >30fps live data (audio, sensors)	HTTP daemon + WebEngineView
Wraps an existing app with a WebSocket server	WebEngineView → ws://localhost

Step 2 — Scaffold

Always create these files:

~/.local/share/plasma/plasmoids/com.manny.<name>/
  metadata.json
  contents/
    ui/
      main.qml
    config/              ← only if widget has settings
      main.xml
    ui/
      ConfigForm.qml     ← only if widget has settings

See REFERENCE.md for every template.

Step 3 — Critical Plasma 6 rules (never skip)

Root of main.qml must be PlasmoidItem — not Item, not Rectangle
Always import org.kde.plasma.plasmoid 2.0
Shell commands use P5Support.DataSource — PlasmaCore.DataSource was removed in Plasma 6
~ does not expand in shell commands — always use /home/manny/
metadata.json uses "KPackageStructure": "Plasma/Applet" — not ServiceTypes
Style/BaseWidget imports use relative path "../../../com.manny.base/contents/ui" — needs qmldir in base folder to work as singleton

Step 4 — Test

plasmawindowed com.manny.<name>

If it crashes with no output, the most common causes are:

Wrong root type (not PlasmoidItem)
Bad metadata.json format
Import path wrong

Strip to bare minimum Rectangle first, then add imports back one at a time.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free