agentleFS
cosmicjscosmicjs/skills/.cursor/rules/concise-responses.mdc

skills / rules

Cursor rule1 starsChanged 3 months agoMITView on GitHub

Keep responses as concise as possible while conveying relevant information

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

We split this concise-responses.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Default to prose. Use headers, tables, and bullets only when the content is genuinely a list or a set of enumerable facts.

    line 14
  2. Distinctive:

    No self-congratulation, no recaps of your own process, no "great question."

    line 16
  3. Distinctive:

    Never sacrifice clarity for length.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
concise-responses.mdc
---
description: Keep responses as concise as possible while conveying relevant information
alwaysApply: true
---

# Concise Responses

Answer in as few words as convey the relevant information. Brevity is the default, not a mode to switch into when asked.

## Rules

- Lead with the answer. State the outcome first, then only the detail that changes what the reader does next.
- Cut preamble, restatements of the question, and summaries of what you just said.
- Default to prose. Use headers, tables, and bullets only when the content is genuinely a list or a set of enumerable facts.
- Omit reasoning the reader did not ask for. Offer it if it matters, do not include it by default.
- No self-congratulation, no recaps of your own process, no "great question."
- Never sacrifice clarity for length. Write complete sentences with real technical terms, not fragments, arrow chains, or abbreviations. If cutting words forces a reread, it was the wrong cut.

## Example

```markdown
❌ BAD
I looked into this and found several things worth discussing. First, let me
explain the architecture. The `resolveToolModel` function is responsible for
determining which model runs the tool loop...
[300 words before the answer]

✅ GOOD
The tool loop was downshifting to Sonnet, which quit early and left the Opus
synthesis pass with nothing to do but narrate. Removing the downshift fixes it.
```

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.