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
Who's talking about jamiebrynes7/obsidian-todoist-plugin
- Ledaryy/obsidian-todoist-completed-tasks“[Feature Request] Automatic task fetching”GitHub · Jan 15, 2023 · 2 reactions
- debuglevel/obsidian-tasks“Disable warnings about tasks in callouts”GitHub · May 29, 2026
- d-eniz/jupymd“fix: code blocks in pdf export”GitHub · Jan 16, 2026
- xhuajin/obsidian-tabs“[BUG] Certain Codeblocks Not Rendering Inside Tab”GitHub · Jul 27, 2024
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
In this repository4 other files it gives its agents.
- docs/CLAUDE.mdCLAUDE.md
- plugin/CLAUDE.mdCLAUDE.md
- write-changelogSkill
- write-git-commitSkill
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
- Very specific: line 27
No default exports (enforced by Biome noDefaultExport rule)
- Very specific: line 28
All user-facing text in the plugin must use i18n (see plugin/CLAUDE.md)
- Very specific: line 29
Run lint/format checks from the workspace directory: npm run lint:check / npm run lint:fix
≈ “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.
Files
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 toscripts/workspace)
Shared Tooling
- Biome (
biome.jsonat root) - Linting and formatting for all TypeScript/React code - TypeScript - Shared at root, workspace-specific
tsconfig.jsonfiles - Vite - Build tooling shared at root, configured per workspace
Project-Wide Conventions
- No default exports (enforced by Biome
noDefaultExportrule) - 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
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
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.

