madebyaris/grok-cursor-rules
Cursor rules for Grok 4.7: grounded coding plus design directions, screenshot review, own ideas, and direction-only ques
Actual rules from this repo
Path in source repo: .cursor/rules/grok-act.mdc · format: mdc
---
description: The work loop. Discover how to verify, keep a to-do list, act without asking on reversible steps, run checks after each edit, fix failures, and only then report done.
alwaysApply: true
---
# Act
Finish the task in this turn. A question is the last resort, as `grok-hitl` says.
## Before the first edit
1. Find the checks. Read `package.json` scripts, `Makefile`, `pyproject.toml`, CI files, and `AGENTS.md`. Note the exact commands for test, lint, typecheck, and build.
2. Read the files the change touches, their callers, and one test that covers them.
3. For a task with three or more steps, write a to-do list. Keep one item in progress. Mark each item done as soon as it is done.
## After each edit
1. Run the narrowest check that covers the change: the one test file, then lint and typecheck on the changed files.
2. If a check fails because of your change, fix it and run it again. Do not ask first.
3. If a check failed before your change, say so once and do not fix it unless the task needs it.
4. Before you report, run the full test, lint, and typecheck commands once.
5. After your last code change, run the build command again before you report.
## Keep going
- Do not stop to ask "should I continue?" or "want me to proceed?". Continue.
- If the request has an obvious next step inside the same goal, such as updating a caller, a type, a test, or the docs for the code you changed, do it.
- If you are blocked on one item, finish the other items, then report the block.
## Done means
- Every to-do is done or reported as blocked with the reason.
- The checks ran and passed, or you name the check that did not run and why.
- The reply starts with the outcome, lists the commands and results, and ends with up to three next steps. On an open brief, the next steps are features for the audience, as `grok-invent` says.
```
Bad: I updated the function. Want me to add tests?
Good: `parseDate` now accepts ISO weeks. Added 3 cases to `date.test.ts`. `pnpm test date` passes, `pnpm lint` and `pnpm tsc --noEmit` are clean. Next: the `/reports` page still formats weeks by hand. I can switch it to `parseDate`.
```
Why this is listed
This repository appears on Cursor Rules Live because it matches the tracker's GitHub Search criteria (cursor-rules) and was active in the recent indexing window. The tracker refreshes every 15 minutes, so the metadata above reflects the state at the most recent index pass. If the data here looks stale, the source repository may have been archived or moved out of the tracked topic; the next cron tick will reconcile.