Scratch Workspace Manager FAQs

Question 1

Will my scratch files be accidentally committed to Git?

Accepted Answer

No, the skill includes a setup checklist and automated commands to ensure that the .claude/.scratch directory is properly added to your .gitignore file.

Question 2

Can I store sensitive credentials in the scratch folder?

Accepted Answer

While the folder is gitignored, it is still stored on your local disk. You should follow standard security protocols and avoid placing sensitive data in any directory that isn't encrypted.

Question 3

What is the purpose of the scratch workspace?

Accepted Answer

It provides a designated, gitignored directory (.claude/.scratch/) for temporary files, drafts, and experiments that should not be part of your project's version control history.

Question 4

Is the scratch directory structure customizable?

Accepted Answer

Yes, while the skill recommends subdirectories like /drafts, /experiments, and /notes for organization, you can create any structure within .claude/.scratch that fits your workflow.

Question 5

How do I move code from the scratch area to my main project?

Accepted Answer

The skill follows a 'Promote' workflow: review the scratch code, move it to the appropriate project location, delete the scratch version, and then commit the finalized code.

Scratch Workspace Manager

Key Features

Use Cases

Scratch Workspace Manager

Key Features

Use Cases