Skip to content

πŸ“¨ The ultimate agentic social media scheduling tool πŸ€–

docs(claude): add a rule on credentials and sensitive fields in responses

Gilad Resisi2407718ec5bf
diff --git a/CLAUDE.md b/CLAUDE.md
index a13a751a9..ac91bf6dc 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -75,4 +75,5 @@ const useCommunity = () => {
- Code must always be generic, there can't be a way that a specific logic, let's say facebook or instagram, appear in a file that use a generic logic, instead, we need to edit the interface of the provider, add another function, and then generically call it from the generic code, and then implement the specific logic in the provider implementation. we can't have something like if(facebookProvider) {} inside a non facebook provider file.
- Before adding a field to a shared repository/service `select` or changing a shared method's return shape, grep for all its consumers (frontend, public API, MCP/agent tools, orchestrator, webhooks) and confirm the change is intended for each.
- Exposing a stored field to a new external surface (public API, MCP, webhooks) is a data-exposure decision β€” ask first, and check what existing production rows hold for that column before shipping it.
-- Never silently change the meaning or format of a value persisted in an existing DB column; that affects every reader and all historical rows, so ask first.
\ No newline at end of file
+- Never silently change the meaning or format of a value persisted in an existing DB column; that affects every reader and all historical rows, so ask first.
+- Never return a raw Prisma row from a model that holds credentials (`Integration`, `User` and similar) in a controller response. Repository writes on those models must use a `select` with only the fields the caller needs (like `setTimes` with `select: { id: true }`), or the controller returns nothing. This applies even where nearby code looks different.
\ No newline at end of file