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

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

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, 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. Very specific:

    All commands run from this plugin/ directory:

    line 7
  2. Distinctive:

    Always use translations for user-facing text: - never hardcode strings in UI components

    line 38
  3. Very specific:

    Import translations with import { t } from "@/i18n" and use const i18n = t().section

    line 39

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

Plugin CLAUDE.md

Last verified: 2026-03-07

Commands

All commands run from this plugin/ directory:

  • npm run dev - Development build with type checking
  • npm run build - Production build
  • npm run check - TypeScript type checking only
  • npm run test - Run all tests (Vitest)
  • npm run test ./src/utils - Run tests for specific directory/file
  • npm 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 commands
  • src/api/ - Todoist REST API client and domain models
  • src/data/ - Repository pattern for caching API data with sync
  • src/query/ - Custom query language parser and todoist code block renderer
  • src/ui/ - React components (React 19 + React Aria Components + Framer Motion)
  • src/services/ - Business logic (token management, modal orchestration)
  • src/commands/ - Obsidian command definitions
  • src/i18n/ - Internationalization (interface in translation.ts, implementations in langs/)
  • 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 use const i18n = t().section
  • For simple text: define as string in translation interface and return string value
  • For text with interpolation: define as (param: Type) => string function 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 in translation.ts and implementations in langs/

Testing

  • Vitest with jsdom environment for React component testing
  • Mocked Obsidian API (src/mocks/obsidian.ts)

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.