hooks Cursor ruleA
hooks from chihebnabil/lovable-boilerplate is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add chihebnabil/lovable-boilerplate/.cursor/rules/hooks.mdc@git:20250727.a15289dPins git:20250727.a15289d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- chihebnabil/lovable-boilerplate
- Path
.cursor/rules/hooks.mdc- Versions recorded
- 1
- Latest version
- git:20250727.a15289d, committed Jul 27, 2025
- Size
- 2,755 bytes
- Repository stars
- 66
- License
- MIT
Custom hooks patterns for data fetching, forms, and UI state management.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Custom Hooks Rules
## Hook Organization Patterns
### Data Fetching Hooks
```tsx
// hooks/useUsers.ts
export const useUsers = () => {
return useQuery({
queryKey: ['users'],
queryFn: () => userService.getAllUsers(),
staleTime: 5 * 60 * 1000, // 5 minutes
})
}
export const useUser = (id: string) => {
return useQuery({
queryKey: ['users', id],
queryFn: () => userService.getUser(id),
enabled: !!id,
})
}
```
### Form Hooks
```tsx
// hooks/useUserForm.ts
export const useUserForm = (initialData?: Partial<User>) => {
const form = useForm<UserFormData>({
resolver: zodResolver(userSchema),
defaultValues: initialData || {},
})
const { mutate: saveUser, isPending } = useMutation({
mutationFn: userService.updateUser,
onSuccess: () => toast.success('User saved'),
onError: (error) => toast.error(error.message),
})
return { form, saveUser, isPending }
}
```
### UI State Hooks
```tsx
// hooks/useDisclosure.ts
export const useDisclosure = (initialState = false) => {
const [isOpen, setIsOpen] = useState(initialState)
const open = useCallback(() => setIsOpen(true), [])
const close = useCallback(() => setIsOpen(false), [])
…Read the whole file at its exact version.
How to install
mdr add chihebnabil/lovable-boilerplate/.cursor/rules/hooks.mdc@sha256:49170e5cd1e163d0The line at the top of this page pins the label git:20250727.a15289d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3wwcpa4qa32fs7cp)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in chihebnabil/lovable-boilerplate/.cursor/rules/hooks.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of hooks.mdc from somewhere else? Ask it: where did my hooks.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jul 27, 2025.
Watch this file (sign in, one email per new version)
Installed this file, say at hooks.mdc? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2755 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chihebnabil/lovable-boilerplate · 66 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3wwcpa4qa32fs7cp GET https://markdownregistry.com/api/v1/resolve?ref=chihebnabil/lovable-boilerplate/.cursor/rules/hooks.mdc GET https://markdownregistry.com/api/v1/blob/49170e5cd1e163d06961c552b82b793c2103ccdb80d42f2c4650d1e7270ea7c3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.
More from chihebnabil/lovable-boilerplate
Every file in chihebnabil/lovable-boilerplate