agentleFS
Sign inStart free
yu-iskwyu-iskw/skill-inspector/CLAUDE.md

skill-inspector

CLAUDE.md2 starsChanged 10 months agoApache-2.0View on GitHub

  • Installs packages

The file

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Exports: Prefer named exports over default exports.

    line 29
  2. Very specific:

    Variables: Use const by default, let only when necessary.

    line 30
  3. Very specific:

    Types: Avoid any; use unknown for ambiguous data.

    line 31
  4. Distinctive:

    External Dependencies: Avoid mocks/patches for network, DB, or file system operations.

    line 37
  5. Distinctive:

    Infrastructure: Use "Nullables" or state-tracking for infrastructure testing when necessary.

    line 38
  6. Distinctive:

    Use relative paths for internal imports.

    line 43

≈ “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.md

Project Commands

Build & Run

  • Build: pnpm build
  • Run (dev): pnpm dev
  • Run (dist): pnpm start

Code Quality

  • Lint: pnpm lint
  • Format: pnpm format
  • Test: pnpm test
  • Setup Dev Env: pnpm install && pnpm trunk install

Package Management

  • Install: pnpm install
  • Add Dependency: pnpm add <pkg>
  • Add Dev Dependency: pnpm add -D <pkg>

Coding Standards

TypeScript

  • Naming: UpperCamelCase for classes/interfaces/types, lowerCamelCase for variables/functions.
  • Exports: Prefer named exports over default exports.
  • Variables: Use const by default, let only when necessary. Never use var.
  • Types: Avoid any; use unknown for ambiguous data. Explicitly type API boundaries.
  • Formatting: 2 spaces, semicolons required, 1TBS brace style.

Testing Philosophy

  • Decoupling: Design functions to be "pure" (deterministic inputs/outputs).
  • External Dependencies: Avoid mocks/patches for network, DB, or file system operations.
  • Infrastructure: Use "Nullables" or state-tracking for infrastructure testing when necessary.

Project Structure

  • Organize by feature/domain.
  • Use relative paths for internal imports.
  • File naming: camelCase for utilities, PascalCase for components/classes.

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