---
spec_name: "Cursor Stack Audit & Safeguard Spec"
version: 1.0
author: "Mike Kwal"
description: "A spec for Claude Code to help a user audit their projects for Cursor usage and implement a .cursorignore file to protect sensitive data following the SpaceX acquisition."
---

# Task: Audit project directories and deploy `.cursorignore` safeguard

Your goal is to help me secure my codebases in light of the news that Cursor session data will be used to train SpaceX's Grok model. 

We will perform two main tasks:
1.  **Audit:** You will help me identify projects that may contain sensitive files.
2.  **Safeguard:** You will provide the standard `.cursorignore` file and help me place it in the correct directories.

## Step 1: Project Audit

First, I need to know where my potential exposure is. Please write a shell command I can run from my main `~/dev/` directory to list all subdirectories that are git repositories and do NOT contain a `.cursorignore` file.

## Step 2: The `.cursorignore` Asset

This is the standard `.cursorignore` file content. Present this to me in a copy-pasteable block. I will use this as the safeguard.

```
# .cursorignore
# Lines starting with # are comments.
# This file works like .gitignore.

# Ignore node modules and build outputs
node_modules/
dist/
build/

# Ignore environment variables and local configs
.env
.env.*
!/.env.example

# Ignore secrets and keys
*.key
*.pem
secrets.json
wp-config.php

# Ignore client-specific sensitive directories
/client-data/
/private/

# Ignore logs and temporary files
npm-debug.log*
yarn-debug.log*
yarn-error.log*
```

## Step 3: Deployment

After I've identified the at-risk repositories from Step 1, I will `cd` into each one. My final request for you will be to create the `.cursorignore` file with the content from Step 2 in my current working directory.

Let's start with Step 1. Please provide the shell command.