agentleFS
simeydotmesimeydotme/hover-tilt/.cursor/rules/llms-txt-maintenance.mdc

hover-tilt / rules

Cursor rule165 starsChanged 11 months agoMITView on GitHub

Maintain llms.txt file when documentation changes are made

We split this llms-txt-maintenance.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When modifying documentation files in this project, ensure the apps/docs/public/llms.txt file stays synchronized with the documentation …

    line 14
  2. Very specific:

    Update the llms.txt file when you:

    line 22
  3. Very specific:

    When modifying props in HoverTilt.svelte or types/index.ts:

    line 72
  4. Distinctive:

    Adding a prop: Add a new row to the appropriate table (Interaction Props or Aesthetic Props)

    line 74
  5. Distinctive:

    Removing a prop: Remove the corresponding row from the table

    line 75
  6. Distinctive:

    Changing a prop: Update the Type, Default, or Description as needed

    line 76
  7. Distinctive:

    Renaming a prop: Update the prop name and ensure both Svelte (camelCase) and Web Component (kebab-case) formats are correct

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
llms-txt-maintenance.mdc
---
description: Maintain llms.txt file when documentation changes are made
globs:
  - 'apps/docs/src/content/docs/**/*.mdx'
  - 'apps/docs/src/content/docs/**/*.md'
  - 'apps/docs/astro.config.mjs'
  - 'packages/hover-tilt/src/lib/components/HoverTilt.svelte'
  - 'packages/hover-tilt/src/lib/types/index.ts'
alwaysApply: false
---

# llms.txt Maintenance Rule

When modifying documentation files in this project, ensure the `apps/docs/public/llms.txt` file stays synchronized with the documentation structure.

## What is llms.txt?

The `llms.txt` file (located at `apps/docs/public/llms.txt`) follows the [llmstxt.org specification](https://llmstxt.org/) and helps Large Language Models understand this project's documentation. It provides a curated, LLM-friendly overview of the Hover Tilt component library.

## When to Update llms.txt

Update the `llms.txt` file when you:

1. **Add a new documentation page** — Add a corresponding entry in the appropriate section (Docs, Examples, or Optional)
2. **Remove a documentation page** — Remove the corresponding link from llms.txt
3. **Rename a page or change its URL/slug** — Update the URL in llms.txt
4. **Significantly change a page's content or purpose** — Update the description for that link
5. **Add new major features or props** — Update the "Key Technical Details" or "Quick Start" sections if needed
6. **Change the sidebar structure in astro.config.mjs** — Reflect structural changes in llms.txt sections
7. **Modify the component's public API** — When props are added, removed, or changed in `HoverTilt.svelte` or `types/index.ts`, update the "Component Props Reference" section in llms.txt

## llms.txt Structure

The file follows this structure:

```markdown
# Hover Tilt

> Brief summary of what the project is

## Key Technical Details
- Package info, import paths, key concepts

## Quick Start
- Installation and basic usage code examples

## Component Props Reference
- Tables of all props with Type, Default, and Description
- Interaction Props (tiltFactor, scaleFactor, springOptions, etc.)
- Aesthetic Props (shadow, glareIntensity, glareMask, etc.)
- Common Prop Combinations (practical usage examples)

## Docs
- [Page Title](URL): Brief description of what the page covers

## Examples  
- [Example Title](URL): What the example demonstrates

## Optional
- [Advanced Topic](URL): Secondary resources that can be skipped for basic understanding
```

## Section Guidelines

- **Docs section**: Core documentation essential for using the component (Getting Started, Usage, API Reference)
- **Examples section**: Live demos and code examples
- **Optional section**: Advanced topics, bespoke demos, and supplementary content
- **Component Props Reference**: Complete props API in table format (synced with `HoverTilt.svelte` and `types/index.ts`)

## Updating the Component Props Reference

When modifying props in `HoverTilt.svelte` or `types/index.ts`:

1. **Adding a prop**: Add a new row to the appropriate table (Interaction Props or Aesthetic Props)
2. **Removing a prop**: Remove the corresponding row from the table
3. **Changing a prop**: Update the Type, Default, or Description as needed
4. **Renaming a prop**: Update the prop name and ensure both Svelte (camelCase) and Web Component (kebab-case) formats are correct

Props table format:
```markdown
| Prop | Type | Default | Description |
|------|------|---------|-------------|
| `propName` | `type` | `default` | Brief description of what it does. |
```

Source files for props:
- `packages/hover-tilt/src/lib/components/HoverTilt.svelte` — Props destructured from `$props()` and `<svelte:options>` attribute mappings
- `packages/hover-tilt/src/lib/types/index.ts` — `HoverTiltProps` interface with JSDoc comments

## Link Format

Each link entry should follow this format:
```markdown
- [Human-readable title](https://hover-tilt.simey.me/path/): Concise description explaining what the page covers
```

The site URL is `https://hover-tilt.simey.me`.

## Current Documentation Structure

Reference for the current docs structure (from astro.config.mjs sidebar):

- Getting Started: `/getting-started/`, `/usage/`
- Options: `/options/props/`, `/options/css/`
- Examples: `/examples/web-component/`, `/examples/props/`
- Advanced: `/advanced/shadows/`, `/advanced/custom-shadow/`, `/advanced/custom-gradient/`, `/advanced/glare-masks/`
- Bespoke: `/bespoke/credit-cards/`, `/bespoke/pokemon-cards/`, `/bespoke/stacked-3d/`

Download now (ZIP)

  • 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 3,978 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.

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.