Secure Coding

Use when adding API providers, environment variables, external services, logs, deployment configs, or documentation that may expose secrets.

lennney 8a250f1 451 B Updated

File contents

Secure Coding

Rules:

  1. Never hardcode API keys, tokens, or secrets.
  2. Use environment variables or local untracked config.
  3. Provide .env.example only.
  4. Do not print secrets in logs.
  5. Do not include secrets in README, tests, screenshots, or committed files.

lennney/ticketpilot/tree/main/.claude/skills/secure-coding commit 8a250f1201

Frequently asked questions

npx skillmds@latest add lennney/secure-coding