agentleFS
langwatchlangwatch/scenario/.cursor/rules/react-tsx.mdc

scenario / rules

Cursor rule1k starsChanged 11 months agoApache-2.0View on GitHub

React and TSX component development guidelines

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 react-tsx.mdc into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create smaller, focused components.

    line 10
  2. Distinctive:

    When prototyping, keep small components in the same file, but mark to be removed:

    line 13
  3. Distinctive:

    If a hook can be self-contained, it should be self-contained and should be in a separate file.

    line 31
  4. Distinctive:

    Keep hooks in the same file as their components.

    line 34
  5. Distinctive:

    Keep related code together.

    line 39
  6. Distinctive:

    When creating shared templates or reusable components:

    line 44
  7. Very specific:

    Compose via children: - Use children for flexible composition.

    line 52
  8. Distinctive:

    Place public methods first.

    line 81
  9. Distinctive:

    Place private methods at the bottom of the class.

    line 82
  10. Distinctive:

    Use clear method names that describe their purpose.

    line 84

≈ “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
react-tsx.mdc
---
description: React and TSX component development guidelines
globs: *.tsx
alwaysApply: false
---

# Components

- One component per file.
- Create smaller, focused components.
- Compose larger components from smaller ones.
- Logical groupings of components should form a new custom component and moved to a separate file.
- When prototyping, keep small components in the same file, but mark to be removed:

```tsx
/**
 * ExampleComponent
 * Responsibilities:
 * To be an example component
 *
 * TODO: Move to a separate file
 */
function ExampleComponent() {
  return <div>ExampleComponent</div>;
}
```

# Hooks

- Complex hooks should be broken down into smaller, composable hooks.
- If a hook can be self-contained, it should be self-contained and should be in a separate file.
- Break complex logic into smaller hooks.
- Compose hooks when it makes sense.
- Keep hooks in the same file as their components.

# Code Separation

- Separate business logic from UI rendering.
- Keep related code together.
- Maintain clear boundaries between concerns.

# Composable Component Pattern

When creating shared templates or reusable components:

1. **Use compound component pattern** - Attach subcomponents as static properties (e.g., `Template.Header`, `Template.Content`) instead of prop drilling.

2. **Templates are pure UI** - Templates should only handle layout/structure. Pages control conditional logic, data fetching, and business logic.

3. **Subcomponents take their own props** - Each subcomponent (Header, Content, Footer, etc.) should accept its own typed props rather than the parent managing them.

4. **Compose via children** - Use `children` for flexible composition. Pages decide what to render in each slot.

**Example:**
```tsx
// Template
const EditDraftTemplate = ({ children, isLoading }) => {
  if (isLoading) return <Spinner />;
  return <Layout>{children}</Layout>;
};

EditDraftTemplate.Header = ({ title, children }) => (
  <header>{title || children}</header>
);

EditDraftTemplate.Content = ({ content, isStreaming }) => (
  <div className={isStreaming ? "opacity-50" : ""}>{content}</div>
);

// Usage
<EditDraftTemplate isLoading={isLoading}>
  <EditDraftTemplate.Header title="Title" />
  <EditDraftTemplate.Content content={story} isStreaming={streaming} />
</EditDraftTemplate>
```

**Avoid:** Prop drilling, templates with business logic, tightly coupled props.

# Class Organization

- Place public methods first.
- Place private methods at the bottom of the class.
- Group related methods together.
- Use clear method names that describe their purpose.

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.