obsidian-todoist-plugin / plugin
CLAUDE.md1.2k starsChanged 10 months agoMITView on GitHub
Last verified: 2026-03-07 All commands run from this plugin/ directory:
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.
- CLAUDE.mdCLAUDE.md
- docs/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, 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
- Very specific: line 7
All commands run from this plugin/ directory:
- Distinctive: line 38
Always use translations for user-facing text: - never hardcode strings in UI components
- Very specific: line 39
Import translations with import { t } from "@/i18n" and use const i18n = t().section
≈ “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
Plugin CLAUDE.md
Last verified: 2026-03-07
Commands
All commands run from this plugin/ directory:
npm run dev- Development build with type checkingnpm run build- Production buildnpm run check- TypeScript type checking onlynpm run test- Run all tests (Vitest)npm run test ./src/utils- Run tests for specific directory/filenpm run lint:check- Check formatting and linting (BiomeJS)npm run lint:fix- Auto-fix formatting and linting issues
Project Structure
src/index.ts- Plugin entry point; initializes services, registers commandssrc/api/- Todoist REST API client and domain modelssrc/data/- Repository pattern for caching API data with syncsrc/query/- Custom query language parser andtodoistcode block renderersrc/ui/- React components (React 19 + React Aria Components + Framer Motion)src/services/- Business logic (token management, modal orchestration)src/commands/- Obsidian command definitionssrc/i18n/- Internationalization (interface intranslation.ts, implementations inlangs/)src/utils/- Shared utilities
Key Design Decisions
- Repository pattern (
src/data/repository.ts): Generic caching layer that decouples UI from API fetch timing. All Todoist data flows through repositories. - Zustand for settings (
src/settings.ts): Reactive state management for plugin configuration, avoids prop drilling. - React Aria Components: Accessibility-first UI primitives. Prefer these over custom interactive elements.
- SCSS with component-scoped styles: Each component has co-located
.scss; supports Obsidian light/dark themes.
Internationalization
- Always use translations for user-facing text - never hardcode strings in UI components
- Import translations with
import { t } from "@/i18n"and useconst i18n = t().section - For simple text: define as
stringin translation interface and return string value - For text with interpolation: define as
(param: Type) => stringfunction in translation interface Example with interpolation:
// translation.ts deleteNotice: (itemName: string) => string; // en.ts deleteNotice: ((itemName: string) => `Item "${itemName}" was deleted`, // component.tsx new Notice(i18n.deleteNotice(item.name)));- Translation files are in
src/i18n/with interface intranslation.tsand implementations inlangs/
Testing
- Vitest with jsdom environment for React component testing
- Mocked Obsidian API (
src/mocks/obsidian.ts)
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.

