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

obsidian-todoist-plugin

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

Last verified: 2026-03-07 All commands run from this docs/ directory: The site supports versioned documentation with past versions stored in:

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    All commands run from this docs/ directory:

    line 7
  2. Very specific:

    Create markdown files in the docs/ directory

    line 53
  3. Very specific:

    Update sidebars.ts to include new pages in navigation

    line 54
  4. Distinctive:

    Use MDX format for pages requiring React components

    line 55
  5. Distinctive:

    Only cut new documentation versions for minor/major releases

    line 59

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

Docs CLAUDE.md

Last verified: 2026-03-07

Commands

All commands run from this docs/ directory:

  • npm start - Start local development server
  • npm run build - Build documentation site for production
  • npm run serve - Serve built site locally
  • npm run clear - Clear Docusaurus cache
  • npm run bump-version -- ${VERSION} - Create new versioned docs (e.g., npm run bump-version -- 2.2.0)
  • npm run write-translations - Extract translatable strings
  • npm run write-heading-ids - Add heading IDs to markdown files
  • npm run typecheck - TypeScript type checking

Documentation Structure

  • docs/ - Current documentation (markdown/MDX)
  • docs/commands/ - Command-specific docs
  • docs/contributing/ - Developer and contributor guides
  • sidebars.ts - Navigation structure (update when adding new pages)

Versioned Documentation

The site supports versioned documentation with past versions stored in:

  • versioned_docs/version-X.Y.Z/ - Snapshot of docs for each version
  • versioned_sidebars/ - Sidebar configuration for each version
  • versions.json - List of available versions

Site Configuration

Docusaurus Config (docusaurus.config.ts)

  • Site metadata and URL configuration
  • GitHub Pages deployment settings
  • Theme and navigation configuration
  • Versioning setup

Customization

  • src/css/custom.css - Site-wide styling overrides
  • src/components/ - Custom React components
  • src/pages/ - Custom pages (like the homepage)
  • static/img/ - Static assets and images

Development Notes

Adding New Documentation

  1. Create markdown files in the docs/ directory
  2. Update sidebars.ts to include new pages in navigation
  3. Use MDX format for pages requiring React components

Managing Versions

  • Only cut new documentation versions for minor/major releases
  • Version bumping copies current docs to versioned storage

Translation Support

  • Site is configured for internationalization but currently English-only
  • Translation status tracking in translation-status.json
  • Custom TranslationStatus component for displaying translation progress

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.