theodorecreatesco/vibe-coding-rules-starter

Free AI coding rules starter: AGENTS.md, Cursor rule, CLAUDE.md and a security checklist that keep AI agents planning fi

Stars 0 Language — Last updated 2026-10-31 Source on GitHub @theodorecreatesco

Actual rules from this repo

Path in source repo: .cursor/rules/security.mdc · format: mdc

---
description: Rule priority and security guardrails that apply to every task
alwaysApply: true
---

# Always-on rules (free starter)

Always on, in every task and file, even without AGENTS.md.

## Rule priority

When rules clash, follow the higher one and say which you followed:

1. **Security guardrails** (below): never broken, even if I ask. Explain the risk in one line and do the safe version.
2. **The task I asked for**, within the guardrails. List anything I should confirm under "Needs your OK".
3. **Stack conventions** already used in this repo.
4. **Working style.**

For changes touching more than 2 files, start with a short numbered plan and wait for my OK before editing.

## Security guardrails

- Secrets (API keys, tokens, passwords, service-role keys, webhook secrets) live only in server-side environment variables. Never hard-code, log or repeat them, or write one into any file, even if I paste it into chat.
- Never put a secret behind a public prefix (`NEXT_PUBLIC_`, `VITE_`, `EXPO_PUBLIC_`, `PUBLIC_`). `.env` and `.env.*` stay git-ignored, `.env.example` tracked with names only. A committed secret must be rotated, not just deleted.
- Anything touching private data checks the caller (401), that they may touch this record (404 if not theirs) and the role for admin actions (403), on the server. Hiding a button isn't security.
- Validate all input on the server. Parameterised queries only; never build SQL or shell commands from strings. User-facing errors never show stack traces, SQL, paths or secrets.
- Rate-limit sign-in, sign-up, password reset, public forms and paid calls. Webhooks verify signatures. CORS is an allowlist, never `*` with auth.
- Never, unless I ask for that exact action: destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, dropping tables), changing a production database, or disabling or loosening tests, lint rules or type checks to get a pass. No new dependencies without my OK.

View raw on GitHub

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.

Similar in this tracker

Explore by category