agentleFS
sm-wankosm-wanko/Human-on-exception/.cursor/rules/01-audit-ui-persistence.mdc

Human-on-exception / rules

Cursor rule1 starsChanged 46 days agoMITView on GitHub

Audit and SIT requirements for DB writes from UI / member-facing APIs

The file

Files
01-audit-ui-persistence.mdc
---
description: Audit and SIT requirements for DB writes from UI / member-facing APIs
globs: apps/backend/app/**/*.php
alwaysApply: false
---

# Audit for Member-Facing Persistence

For changes matching `globs`, apply this rule when the change adds or modifies create/update/delete-equivalent behavior reachable from UI or authenticated API.

**Source of truth**: [`docs/rules/audit-ui-persistence.md`](../../docs/rules/audit-ui-persistence.md)

Summary: Controller passes authenticated user/member ID into Service. Service constructs the project's existing audit context/value. Repository writes bind those audit values. Positive-path SIT asserts persisted DB audit values.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.