agentleFS
jamiebrynes7jamiebrynes7/obsidian-todoist-plugin/CLAUDE.md

obsidian-todoist-plugin

CLAUDE.md1.2k starsChanged 10 months agoMITView on GitHub

Last verified: 2026-03-07 Three npm workspaces: Each workspace has its own package.json and commands. See workspace-specific CLAUDE.md files for details.

Trending

Quiet since May.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the jamiebrynes7/obsidian-todoist-plugin repository that our weekly crawl found: only 4 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No default exports (enforced by Biome noDefaultExport rule)

    line 27
  2. Very specific:

    All user-facing text in the plugin must use i18n (see plugin/CLAUDE.md)

    line 28
  3. Very specific:

    Run lint/format checks from the workspace directory: npm run lint:check / npm run lint:fix

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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

Last verified: 2026-03-07

Monorepo Structure

Three npm workspaces:

  • plugin/ - Obsidian plugin source code (TypeScript, React, Vite)
  • docs/ - Documentation site (Docusaurus)
  • scripts/ - Release and code generation scripts

Each workspace has its own package.json and commands. See workspace-specific CLAUDE.md files for details.

Top-Level Commands

  • npm run gen - Run code generation scripts (delegates to scripts/ workspace)

Shared Tooling

  • Biome (biome.json at root) - Linting and formatting for all TypeScript/React code
  • TypeScript - Shared at root, workspace-specific tsconfig.json files
  • Vite - Build tooling shared at root, configured per workspace

Project-Wide Conventions

  • No default exports (enforced by Biome noDefaultExport rule)
  • All user-facing text in the plugin must use i18n (see plugin/CLAUDE.md)
  • Run lint/format checks from the workspace directory: npm run lint:check / npm run lint:fix

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.