Userscripts Workspace

This repo is the working source of truth for your browser userscripts.

Goal

Keep scripts:

• easy to review and refine
• easy to install in Tampermonkey
• consistent across multiple browsers and machines

Layout

• scripts/ active userscripts, one file per script
• templates/ starter templates and reusable header patterns
• docs/ notes for install, sync, and migration decisions
• archive/ retired or superseded scripts

Naming

Use:

• script-name.user.js for Tampermonkey-ready files

Example:

• scripts/youtube-cleanup.user.js

Working Rules

• Keep each script self-contained unless there is a strong reason not to.
• Prefer explicit metadata headers and clear version bumps.
• Use stable selectors and defensive guards to reduce breakage.
• Avoid site-specific hacks without a short comment explaining why.
• Preserve Tampermonkey compatibility first; optimize second.

Multi-Browser / Multi-Machine Workflow

Recommended baseline:

1. Keep this repo in Git.
2. Sync it through GitHub, a private Git remote, or a synced folder service.
3. Install scripts in Tampermonkey from the files in scripts/.
4. When a script changes, update the file here first, then reinstall or update it in each browser.

If you want, I can later set this up for one of these models:

• local-file workflow
• GitHub-hosted raw script workflow with @downloadURL and @updateURL
• cloud-synced folder workflow

The GitHub-hosted raw script workflow is usually the cleanest for multiple browsers and devices.

Process Here

When you give me a .js file, I will help with:

• cleanup and refactoring
• metadata normalization
• Tampermonkey compatibility
• readability and maintainability
• reducing breakage from DOM changes
• consolidating overlapping scripts

Next Step

Drop one or more .js files into scripts/ or paste them here, and I will normalize them into Tampermonkey-ready *.user.js files where needed.