PaperFit / rules
Cursor rule338 starsChanged 36 days agoMITView on GitHub
PaperFit project rule for LaTeX visual typesetting optimization
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,181 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- consistency-polisherSkill
- float-optimizerSkill
- overflow-repairSkill
- paperfitSkill
- space-util-fixerSkill
- taxonomy-vtoSkill
- template-migratorSkill
- visual-inspectorSkill
- writing-polishSkill
The file
Show its rules and text
We split this paperfit.mdc into the rules it gives an agent
14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use PaperFit when working on a LaTeX paper that needs visual typesetting optimization.
- Very specific: line 15
Treat PaperFit as a natural-language agent system, not a CLI-first workflow.
- Very specific: line 21
Use the paperfit CLI, runtime, and scripts as the internal execution layer.
- Very specific: line 22
Prefer paperfit runtime --state data/state.json run-round main.tex --template <TEMPLATE> --target-pages <N> for the main closed loop.
- Very specific: line 23
Use paperfit render and paperfit run scripts/...
- Very specific: line 24
Do not require the user to manually type internal PaperFit commands in the normal product path.
- Distinctive: line 26
Prefer self-recovery in recoverable failures.
- Distinctive: line 27
Keep user-facing explanations centered on results, visual defects, repair strategy, and residual risks.
- Very specific: line 31
Do not use \resizebox or \scalebox as brute-force table shrinking.
- Distinctive: line 32
Prefer full-width or full-column table layouts that preserve readability and alignment.
- Distinctive: line 33
Do not change the template font packages or the visual font appearance of body text and tables during repair.
- Distinctive: line 35
Treat visual results as the primary acceptance signal.
- Distinctive: line 36
Keep semantic edits minimal and do not alter academic claims, results, or citations.
- Distinctive: line 37
Do not silently delete figures, tables, captions, or labels to improve layout.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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.
Files
--- description: PaperFit project rule for LaTeX visual typesetting optimization globs: - "**/*.tex" alwaysApply: false --- # PaperFit Rule Use PaperFit when working on a LaTeX paper that needs visual typesetting optimization. ## Product Rules - Work from the paper project root. - Treat PaperFit as a natural-language agent system, not a CLI-first workflow. - Users should describe goals directly, such as layout analysis, full repair, template migration, page-budget adjustment, or visual-only inspection. - Automatically infer the closest PaperFit workflow from the user's request before asking them for low-level PaperFit command syntax. ## Execution Rules - Use the `paperfit` CLI, runtime, and scripts as the internal execution layer. - Prefer `paperfit runtime --state data/state.json run-round main.tex --template <TEMPLATE> --target-pages <N>` for the main closed loop. - Use `paperfit render` and `paperfit run scripts/...` only for targeted debugging, staged execution, or recovery. - Do not require the user to manually type internal PaperFit commands in the normal product path. - During long PaperFit runs, report progress proactively instead of staying silent. - Prefer self-recovery in recoverable failures; only ask the user to act when environment, permission, or ambiguity issues block execution. - Keep user-facing explanations centered on results, visual defects, repair strategy, and residual risks. ## Layout Rules - Do not use `\resizebox` or `\scalebox` as brute-force table shrinking. - Prefer full-width or full-column table layouts that preserve readability and alignment. - Do not change the template font packages or the visual font appearance of body text and tables during repair. - Confirm fixes against rendered page images, not source-only inspection. - Treat visual results as the primary acceptance signal; logs and source are supporting evidence. - Keep semantic edits minimal and do not alter academic claims, results, or citations. - Do not silently delete figures, tables, captions, or labels to improve layout. ## Installed Assets - Global PaperFit skills live under `~/.cursor/skills/paperfit/`. - This rule file is project-local and should live at `.cursor/rules/paperfit.mdc` inside the paper repository.
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
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.