Skip to content

CLAUDE.md

Latest commit

 

History

History
43 lines (30 loc) · 2.37 KB

CLAUDE.md

File metadata and controls

43 lines (30 loc) · 2.37 KB

Project Rules: dev-tool-configs

This repository provides privacy-focused, best-effort configurations for AI coding tools. These rules apply to all contributions -- human or AI-assisted.

Language and Liability

  • Never use absolute claims about privacy, security, or data protection. Use hedging language: "reduces", "aims to", "best-effort", "helps prevent", "opts out of".
  • Never use "privacy-hardened" -- use "privacy-focused" instead.
  • Never state vendor behaviour as guaranteed fact -- always qualify with "(per vendor policy)", "(per their stated terms as of YYYY-MM)", or similar.
  • Never remove or weaken disclaimers. The root README disclaimer and the disclaimer footers in each tool README must remain intact. If updating them, only strengthen -- never soften.
  • Any new tool README must include the standard disclaimer footer linking back to ../README.md#disclaimer.

Content Safety

  • No personal data in any committed file: no real names, email addresses, account IDs, or user-specific file paths.
  • No secrets -- no API keys, tokens, credentials, or realistic-looking examples of them.
  • Config files must be generic -- use ~ or <placeholder> notation, never hardcoded user paths.
  • Use "Recommended" for non-default settings, never "Ours", "My", or "Mine".

Accuracy

  • When citing vendor defaults, settings, or data practices, verify against current official documentation.
  • If a setting or vendor behaviour cannot be independently verified, note it as unconfirmed.
  • Do not fabricate vendor documentation links. Only link to URLs you can verify exist.

Example Config Naming (OpenCode)

  • Name by strategy or goal, never by a single model (models change, strategies don't).
  • Maintainer configs: {strategy}.json (e.g., frontier-mix.json, budget-zdr.json).
  • Community configs: community/{handle}-{strategy}.json.
  • Never use guarantee-implying terms in filenames (privacy, secure). Use factual alternatives (zdr, open-weight, direct).

Structure

  • Follow the existing pattern: clean config file + annotated companion + README per tool.
  • Keep config files copy-pasteable and working as-is.
  • One tool per PR when adding new sections.

Testing

  • Verify config settings work with the relevant tool before submitting.
  • Run opencode models for OpenCode example configs.
  • Check JSON validity for all config files.