Remove a Wireplumber preference rule — by filename, by matched device name, or by description. Restarts Wireplumber so the change takes effect immediately. Use when a rule is no longer wanted or is causing wrong-device routing.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-pipewire-skillsThis skill uses the workspace's default tool permissions.
Cleanly remove a previously-installed Wireplumber rule.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Share bugs, ideas, or general feedback.
Cleanly remove a previously-installed Wireplumber rule.
list-preference-rules if the user hasn't named a specific file.rm ~/.config/wireplumber/wireplumber.conf.d/<file>.conf
systemctl --user restart wireplumber
wpctl status — the previously-pinned device should no longer be forced default.rm -rf the whole wireplumber.conf.d/ directory./etc/wireplumber/ files without an explicit confirm — those are system-level and may have been installed by a package.dpkg -S <path> (Debian/Ubuntu) — if it's owned by a package, leave it alone and tell the user.If the user might want the rule back, rename rather than remove:
mv ~/.config/wireplumber/wireplumber.conf.d/<file>.conf{,.disabled}
Wireplumber only loads .conf files, so the .disabled suffix shelves it without losing the content.