I completely understand the struggle. Gaining traction on GitHub is rarely just about writing great code; it's about how easily others can adopt, understand, and trust your work.

Here are a few practical strategies that actually move the needle, breaking it down by usefulness, quality, and visibility:

1. Frictionless Onboarding (Usefulness & Quality)
   The biggest hurdle isn't getting people to your repository; it's getting them to stay once they land there.

The README is your landing page: It needs to explain exactly what problem it solves in the first two sentences. Include a GIF, a clear architecture diagram, or a terminal recording of it in action.

One-Command Setup: If someone has to spend 20 minutes configuring dependencies or troubleshooting your stack, they will leave. Providing a docker-compose.yml file, a ready-to-use containerized version, or a quick automation script makes a massive difference. Make it so they can spin it up and test it with a single command.

CI/CD & Reliability Signals: Having active workflow badges (like GitHub Actions for passing builds or tests) signals to visitors that the project is stable, actively maintained, and ready for real-world use.

2. Strategic Visibility (Beyond standard promotion)
   Community Integration: Instead of just dropping links on social media, find where the people who actually need your tool hang out. Share the story of why you built it on specific subreddits, Discord communities, or developer forums. Lead with the headache you were trying to solve, rather than just asking for stars.

The "Awesome" Ecosystem: Find an awesome-* list on GitHub that fits your project's specific niche (e.g., awesome-selfhosted, awesome-sysadmin) and submit a pull request to add your tool. This drives consistent, high-intent traffic from developers looking for exactly what you built.

3. Open the Door for Contributors
   People who contribute will naturally star and share your project.

Create a solid CONTRIBUTING.md file.

Leave a few easy, well-documented bugs or feature requests open and tag them as good first issue or help wanted.