agentleFS
Sign inStart free
AgriciDanielAgriciDaniel/claude-code-essentials-vs-code/CLAUDE.md

claude-code-essentials-vs-code

CLAUDE.md60 starsChanged 8 months agoMITView on GitHub

This repository provides opt-in Windows PowerShell and Bash setup entrypoints, focused guides and optional project templates. - scripts/setup.ps1 and scripts/setup.sh own behavior. - install-extensions entrypoints delegate to setup with the same safety defaults. - Preview is default; selected installs require Apply/--apply. - Never add bulk OS upgrades, hidden installs, automatic authentication, permission bypass aliases or user-profile template writes. - Preserve existing installations. Check exit codes and postconditions. - Test with python tests/test_package.py; fake external processes and disposable storage only. Real…

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never add bulk OS upgrades, hidden installs, automatic authentication, permission bypass aliases or user-profile template writes.

    line 9
  2. Very specific:

    Test with python tests/test_package.py.

    line 12
  3. Very specific:

    Keep docs/validation.md honest about which native OS and installer paths ran.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Claude Code Essentials for VS Code

This repository provides opt-in Windows PowerShell and Bash setup entrypoints, focused guides and optional project templates.

  • scripts/setup.ps1 and scripts/setup.sh own behavior.
  • install-extensions entrypoints delegate to setup with the same safety defaults.
  • Preview is default; selected installs require Apply/--apply.
  • Never add bulk OS upgrades, hidden installs, automatic authentication, permission bypass aliases or user-profile template writes.
  • Preserve existing installations. Check exit codes and postconditions.
  • Test with python tests/test_package.py; fake external processes and disposable storage only. Real installer tests require separately proven confinement.
  • Keep docs/validation.md honest about which native OS and installer paths ran.
  • Source provenance: baseline 8b5575bff5f6cd3f0f964df54010233d9b04c010.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free