agentleFS
langwatchlangwatch/scenario/.cursor/rules/typescript.mdc

scenario / rules

Cursor rule1k starsChanged 11 months agoApache-2.0View on GitHub

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about langwatch/scenario

The biggest 5 of 47 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 47

Talked about on GitHub and Hacker News (47 times).

On GitHub · 45

40 more on GitHub

On Hacker News · 2

The file

We split this typescript.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add TSDoc style documentation when writing functions, methods and components.

    line 10
  2. Distinctive:

    Always use named imports for React components and hooks.

    line 18
  3. Very specific:

    Never use non-destructured imports, such as React.useMemo or React.useCallback.

    line 19
  4. Very specific:

    Never use the any type.

    line 22

≈ “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
typescript.mdc
---
description:
globs: *.tsx
alwaysApply: false
---

## Typescript Development Guidelines:

### Documentation
   - Add TSDoc style documentation when writing functions, methods and components.

### Single Responsibility
    - SRP is a core principle of our codebase and should be followed in all functions, methods and components.
     => if the function, method or component is more than one responsibility, suggest how to break it down into smaller functions, methods or components. Encourage the user to use the "Single Responsibility" principle
     and explain the benefits of doing so in this case.

### Imports
   - Always use named imports for React components and hooks.
   - Never use non-destructured imports, such as `React.useMemo` or `React.useCallback`.

### Type Safety
   - Never use the `any` type.

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.