cursor / cursor/plugins

Feature request: content/writing quality plugins beyond Developer Tools

Open
#107 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8.2k
Forks
751
Avg merge
12h 1m
Merged PRs (30d)
43

Description

The current plugins are all excellent developer-tools-focused ones (code review, CLI design, continual learning, etc.).

One category that seems missing: content and writing quality. A lot of Cursor users write docs, blog posts, release notes, and marketing copy — not just code — and AI-generated prose has its own quality problems.

Two examples of what this could look like:

  1. Anti-slop writing — catching AI tells in prose (filler phrases, predictable structures, throat-clearing openers). The English-language stop-slop skill (7k+ stars) is a good reference for the concept.

  2. Non-English content quality — this is especially underserved. Chinese AI writing, for instance, has completely different tells from English (different filler phrases, punctuation habits like overusing colons and em-dashes, numbered-list addiction). I built a skill for this: https://github.com/pencil20388-eng/stop-slop-zh

Would the team be open to a "Writing" or "Content" category in the plugin spec? Happy to adapt stop-slop-zh into the Cursor plugin format as a reference implementation if that's useful.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the plugin specification and existing developer-tools-focused plugins first, then compare the stop-slop and stop-slop-zh references. Done means the team has defined whether a Writing or Content category belongs in the spec and agreed on the scope of any reference implementation.

Written by the indexing model from the issue text.

Assessment

Domain
content, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.