personal-finance / rules
Cursor rule1 starsChanged todayMITView on GitHub
TypeScript testing: Vitest, Testing Library by user-visible behaviour, Playwright for flows, test-first
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 repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/angular-coding-style.mdcCursor rule
- .cursor/rules/angular-patterns.mdcCursor rule
- .cursor/rules/angular-security.mdcCursor rule
- .cursor/rules/angular-testing.mdcCursor rule
- .cursor/rules/common-code-review.mdcCursor rule
- .cursor/rules/common-coding-style.mdcCursor rule
- .cursor/rules/common-development-workflow.mdcCursor rule
- .cursor/rules/common-security.mdcCursor rule
- .cursor/rules/common-testing.mdcCursor rule
- .cursor/rules/csharp-coding-style.mdcCursor rule
- .cursor/rules/csharp-data-access.mdcCursor rule
- .cursor/rules/csharp-patterns.mdcCursor rule
- .cursor/rules/csharp-security.mdcCursor rule
- .cursor/rules/csharp-testing.mdcCursor rule
- .cursor/rules/design-design-system.mdcCursor rule
- .cursor/rules/project-backend.mdcCursor rule
- .cursor/rules/project-security.mdcCursor rule
- .cursor/rules/project-testing.mdcCursor rule
- .cursor/rules/project-web.mdcCursor rule
- .cursor/rules/typescript-coding-style.mdcCursor rule
- .cursor/rules/typescript-patterns.mdcCursor rule
- .cursor/rules/typescript-security.mdcCursor rule
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- ui-ux-pro-maxSkill
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- The first 60 shown.
The file
We split this typescript-testing.mdc into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 18
Never: delete, skip (.skip, .only, xit) or weaken a test to make the gate pass.
- Distinctive: line 19
Test data is synthetic: no real names, emails, accounts or customer data in fixtures.
≈ “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.
Files
--- description: "TypeScript testing: Vitest, Testing Library by user-visible behaviour, Playwright for flows, test-first" globs: **/*.test.ts,**/*.test.tsx,**/*.spec.ts,**/*.spec.tsx,**/__tests__/**,**/e2e/**,**/vitest.config.*,**/playwright.config.* alwaysApply: false --- <!-- Generated by armature from stack-typescript/rules/typescript/testing.md. Edit the source rule, not this file. --> # TypeScript testing - **Test-first.** A behaviour change starts with a failing test taken from the acceptance criteria. - **Runner:** Vitest for unit and component tests (Jest only where the repo already uses it). One runner per repo. - **Components:** Testing Library, tested by what the user sees and does. Query by role and accessible name first, then label, then text; `data-testid` only as a last resort. `userEvent` (awaited) instead of `fireEvent`. - **Async:** `findBy*` or `waitFor`, never a `setTimeout` followed by an assertion. - **Network:** mock at the network boundary (MSW or a fake server), not by mocking the fetch wrapper. - **No snapshot tests of rendered components**; they get rubber-stamped. Use real assertions, and screenshots in Playwright for visual regressions. - **End to end:** Playwright for the critical user flows, against a running app with synthetic data. - **Never** delete, skip (`.skip`, `.only`, `xit`) or weaken a test to make the gate pass. - Test data is synthetic: no real names, emails, accounts or customer data in fixtures. <!-- Adapted from affaan-m/ECC rules/typescript/testing.md and rules/react/testing.md (MIT) at d2ef268; merged with the owner's conventions (ordo-frontend AGENTS.md: Vitest + Testing Library by behaviour, Playwright for flows; personal-finance-sdd: test-first, synthetic data). -->
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.

