Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/golid-ai/golid/write-tests-frontend-workflowgit clone --depth 1 https://github.com/golid-ai/golidWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/golid-ai/golid/write-tests-frontend-workflow)<a href="https://agentmods.dev/rules/golid-ai/golid/write-tests-frontend-workflow"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/write-tests-frontend-workflow.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00608 |
| Opus 5 | $0.00000 | $0.00304 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
write-tests-frontend-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Test Workflow
Thesis: Ratchet coverage, keep tests in sync with public interfaces, and verify types before push — workflow discipline prevents silent CI failures.
Coverage Thresholds
After writing tests, update vitest.config.ts thresholds to 5% below the new actual coverage. This prevents regression without blocking future work. Ratchet up as coverage grows.
Current thresholds: statements: 75, branches: 54, functions: 78, lines: 75 (included files; recalibrated 2026-06-07). CI fails if coverage drops below these. Codecov project gate (target: 80%) is documented in docs/plans/archive/6-7-26/coverage-and-eslint.md.
Keep Tests In Sync With Code
Any commit that changes a component's public interface must include test updates in the same commit. Public interface means:
- Placeholder text, labels, or rendered copy
- Toast/snackbar message strings (title, subtitle)
- Component swaps (checkbox → button, outline → neutral)
- Props that tests assert on (variant, size, disabled state)
- API mock shapes (new fields, changed signatures)
- Route changes or navigation targets
Search for affected tests before committing. Use rg "the old text" across *.test.tsx, *.test.ts, and tests/e2e/*.spec.ts. If a test references something you changed, fix it in the same commit.
E2E tests (tests/e2e/) use browser selectors that match rendered HTML — placeholder changes, button text changes, and form restructuring all break them silently until CI runs. See write-tests-e2e for browser-test patterns.
Pre-Push Checklist
Before pushing any test file changes, run both:
cd frontend && npx vitest run # runtime tests
cd frontend && npx tsc --noEmit # type checking
TypeScript catches import errors (non-existent exports, using types as values) that JavaScript silently ignores at runtime. CI runs npm run typecheck and will reject type errors even when all tests pass.
Running Tests
# Frontend unit + component tests
cd frontend && npm test
# Frontend type check (run before pushing — catches import errors tests miss)
cd frontend && npx tsc --noEmit
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 58 lines · 0 tokens per session scan A 1ee2986fe040
write-tests-frontend-workflow is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 608 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
core
Core token-efficiency and response discipline rules. Always active.