Skip to content
Skills Library
Security · Building & coding

security-basics

/security-basics

Build it so the people using it are safe, on any stack: what could go wrong for whom, where secrets live, what personal data leaves the device, sign-in and payments done the safe way. Use when someone says "keep my users' data safe", "where do I put the API key", "add sign-in", "add login", "take payments", "add a subscription", "store their emails", "send this to a server", "is this safe to build", or when a change touches sign-in, payments, personal data, secrets or what leaves the device. To check a finished project ("is it secure?"), `review` runs its security lens.

Repository
solid-vibes ↗
Licence
MIT
Last repository change
05.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build it so the people using it are safe, on any stack: what could go wrong for whom, where secrets live, what personal data leaves the device, sign-in and payments done the safe way. Use when someone says "keep my users' data safe", "where do I put the API key", "add sign-in", "add login", "take payments", "add a subscription", "store their emails", "send this to a server", "is this safe to build", or when a change touches sign-in, payments, personal data, secrets or what leaves the device. To check a finished project ("is it secure?"), `review` runs its security lens.

Triggers from the description

keep my userswhere do I put the API keyadd sign-inadd logintake paymentsadd a subscriptionstore their emailssend this to a server
Original author description

Build it so the people using it are safe, on any stack: what could go wrong for whom, where secrets live, what personal data leaves the device, sign-in and payments done the safe way. Use when someone says "keep my users' data safe", "where do I put the API key", "add sign-in", "add login", "take payments", "add a subscription", "store their emails", "send this to a server", "is this safe to build", or when a change touches sign-in, payments, personal data, secrets or what leaves the device. To check a finished project ("is it secure?"), `review` runs its security lens.

How it works

  1. Step 1 — Who could be hurt, and how
  2. The basics
  3. While building
  4. Visuals
Original SKILL.md headings · 39 lines, 713 words
SKILL.md preview
---
name: security-basics
description: Build it so the people using it are safe, on any stack: what could go wrong for whom, where secrets live, what personal data leaves the device, sign-in and payments done the safe way. Use when someone says "keep my users' data safe", "where do I put the API key", "add sign-in", "add login", "take payments", "add a subscription", "store their emails", "send this to a server", "is this safe to build", or when a change touches sign-in, payments, personal data, secrets or what leaves the device. To check a finished project ("is it secure?"), `review` runs its security lens.
---

# Security

The basics of building something safe, on any stack. This skill is for **while you build**: the questions to answer and the rules to follow before and during a change. Checking afterwards is the `review` skill's security lens, which starts from the basics below and goes deeper; the basics are written here once.

Used by `plan`, `brief` and `go` whenever a change touches sign-in, payments, personal data, secrets or what leaves the device.

How you talk to the user:
- Talk about people, not attacks: "If someone got this list, they would have every customer's phone number."
- Decide the safe way yourself from `docs/stack.md`; explain it in one plain sentence when it changes what they see ("You'll sign in with a code sent by email, so there's no password to steal").
- A change that touches a contract `risk` area is shown to them first, with a visual and that one sentence.

## Step 1 — Who could be hurt, and how

Before the change, write three to five lines in the plan's `## Constraints` or the brief's **Risk**: what this stores or sends, who it belongs to, and what would happen to them if it leaked, was changed by someone else, or was lost. Use the people from `docs/intent.md` and its never list. Each line gets the basic below that prevents it.

## The basics

1. **Secrets live outside the code.** Keys, tokens and passwords come from the environment or the platform's secret store, never a committed file, never the app or web bundle. A key the app must carry is a public one, limited to what a stranger may do with it. Secret files are listed in `.gitignore` before they exist.
2. **Know what leaves the device.** List every place personal data goes (your server, each outside service, logs, crash reports, analytics) and why. Send the least that does the job. Analytics and tracking only after people say yes, when the intent's values or the law ask for it.
3. **Nothing personal in logs.** No personal data, tokens or message content in logs, error messages or crash reports, in debug builds too. Errors shown to people never include internals.
4. **Sign-in is borrowed, not built.** Use the stack's sign-in provider (email codes, magic links, Apple or Google). Never store passwords yourself. Sessions sit in the platform's secure storage. Signing out ends the session on the server too.
5. **Every request checks who is asking.** The server decides what each person may read and change, on every table and endpoint, the same way. Never trust the app to hide what someone may not see.
6. **Payments go through the provider.** Card details never touch your code: use the provider's hosted checkout or the app store. Access is granted only by the server after the provider confirms payment (a verified webhook or receipt), and removed when it ends.
7. **Check what comes in.** Input from people, links, files and other services is checked where it enters: type, size, allowed values. Queries are parameterised; nothing from outside goes into a shell, a query or HTML unescaped.
8. **People can leave.** Someone can delete their account and data, and the never list in `docs/intent.md` holds for backups and outside services too.

## While building

- Follow every basic the change touches; record any you can't meet, and why, in the plan's `## Decisions` (mine, after showing the owner).
- Name the contract `risk` area the change touches in the brief or plan. It gets a human reviewer before release.
- Never print a secret, even to show where it is; name the file and line only.

With Pro: the `security` pack adds stack rules and checklists (secret scanning, secure storage, consent before analytics, wiping data on sign-out, signing keys, web security headers), and the `supabase` pack checks the database's access rules.

## Visuals

"Show a visual" means: make the page with the `visual` skill and show it as `.solidvibes/agents.md` says for the agent in use. If that file is missing, write a local HTML file and tell the user where it is. Step 1 is drawn as a picture of the real things (phone, server, each outside service) with what personal data travels along each arrow, and the basic that protects it.

Versions

RepositoryScoreLicence
This page · solidvibes/solid-vibes90MIT
adilkalam/orca100MIT
lukashouthoofd/cenekathon96MIT

Database snapshot: 13.11.2026 · package version d8756435e70a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100secure-change
    Build or review code that handles login, permissions, user input, files, secrets, payments or personal data. Use this whenever a change adds an endpoint, a form, an upload, a query built from input, a webhook, a token or an admin action, even if security was not mentioned.
  • 100lidtight-check
    Use when the user is about to launch, publish or share a web app, asks whether their app is secure or safe to go live, has added sign-in, payments, a database, file uploads or an AI feature, or wants a security review of a deployed web app, including apps built with Lovable,…
  • 100together-security-basics
    Secure Together AI integrations with project-scoped keys, environment isolation, prompt/output data controls, bounded model behavior, safe logging, rotation, and incident response. Use when threat-modeling or hardening Together usage. Trigger with "Together security", "protect…
  • 100security-review-gate
    Security review for changes that cross a sensitive boundary. Use when a change or pull request adds or alters authentication, authorization, permissions, sharing or tenancy, private or personal data, secrets, untrusted input, payments, or file and network access, and before merging it.
  • 100exa-security-basics
    Apply Exa security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing Exa security configuration. Trigger with phrases like "exa security", "exa secrets", "secure exa", "exa API key security".
  • 100windsurf-security-basics
    Apply Windsurf security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing Windsurf security configuration. Trigger with phrases like "windsurf security", "windsurf secrets", "secure windsurf", "windsurf API key security".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.