Aider Security Configuration

A security-hardened Aider AI configuration template that enforces credential protection, sensitive file tracking prevention, and automated security audits before code commits.

What This Skill Does

This skill configures Aider AI with security-first rules to prevent common vulnerabilities in static site development. It establishes mandatory pre-commit checks that block commits containing credentials, sensitive files, or personal information until security requirements are met.

Instructions

When implementing this security configuration:

1. **Create the security rules file**

- Create `.ai/SECURITY_RULES.md` in your project root

- Document complete security requirements:

- Credential detection patterns

- Sensitive file patterns to exclude from git

- Personal information handling guidelines

- Security audit checklist

2. **Configure Aider to enforce security checks**

- Add the security rules reference to your Aider configuration

- Configure pre-commit hooks that verify:

- No hardcoded credentials (API keys, tokens, passwords)

- No sensitive files tracked in git (`.env`, private keys, certificates)

- No personal information in documentation

- Security audit completion

3. **Implement pre-commit validation**

- Set up automated checks that run before each commit

- Block commits that fail any security requirement

- Provide clear error messages directing to `.ai/SECURITY_RULES.md`

4. **Document security requirements**

- List all credential patterns to avoid (API keys, OAuth tokens, database passwords)

- Define sensitive file patterns (`.env*`, `*.pem`, `*.key`, `credentials.*`)

- Specify personal info to redact (emails, phone numbers, addresses)

- Create security audit checklist (dependency scanning, file permission review)

5. **Configure for static site context**

- Ensure build artifacts are excluded from security scans

- Add static site-specific patterns (dist/, build/, public/ generated files)

- Configure environment variable handling for build processes

Example Usage

When Aider attempts to commit code, it will:

1. Read and apply rules from `.ai/SECURITY_RULES.md`

2. Scan staged files for credentials using pattern matching

3. Check git tracking for sensitive files

4. Verify no personal information exists in documentation

5. Confirm security audit completion

6. Block commit if any check fails, with specific remediation guidance

Constraints