agentleFS
scheronscheron/Daily/AGENTS.md

Daily

AGENTS.md4 starsChanged 7 days agoMITView on GitHub

Daily ships as a pnpm workspace of six packages: the app (apps/desktop), the sync server (apps/server), and four Electron-free shared packages (packages/core, packages/protocol, packages/std, packages/tools). The app is a local-first macOS task manager — Electron main + Vue 3 renderer, built on packages/core's storage core (packages/core/src/storage/createStorageCore.ts). SQLite is the source of truth; sync is optional and uses one provider at a time (iCloud or a self-hosted server), with Last-Write-Wins. packages/tools holds the one tool set agents (over MCP) and the…

  • Reads credentials
  • Installs packages

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Comments: follow the writing-comments skill.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

AGENTS.md

Daily ships as a pnpm workspace of six packages: the app (apps/desktop), the sync server (apps/server), and four Electron-free shared packages (packages/core, packages/protocol, packages/std, packages/tools). The app is a local-first macOS task manager — Electron main + Vue 3 renderer, built on packages/core's storage core (packages/core/src/storage/createStorageCore.ts). SQLite is the source of truth; sync is optional and uses one provider at a time (iCloud or a self-hosted server), with Last-Write-Wins. packages/tools holds the one tool set agents (over MCP) and the Daily Assistant both run, over packages/core's WorkStorage.

Commands

pnpm dev                              # dev server, hot reload
pnpm --filter @daily/desktop build    # package macOS .dmg
pnpm --filter @daily/server build     # bundle the sync server
node scripts/release.js --status      # what each artifact has pending since its own tag
node scripts/release.js               # survey both, then ask which to release
node scripts/release.js app           # release the app (--dry-run supported)
node scripts/release.js server        # release the server (--dry-run supported)
pnpm typecheck:all       # every package — run before committing
pnpm lint                # ESLint check
pnpm lint:fix            # apply ESLint fixes
pnpm test                # full vitest suite (Electron runtime via evitest)
pnpm check:all           # lint + typecheck:all + circular + test

Environment

Build. pnpm --filter @daily/desktop build — packages the macOS .dmg. pnpm --filter @daily/server build — bundles the sync server. Typecheck. pnpm typecheck:all Lint. pnpm lint (check) or pnpm lint:fix (apply fixes) Tests. pnpm test — vitest under the Electron runtime. Single test file. pnpm evitest run packages/core/tests/storage/sync/convergence.test.ts Dev server. pnpm dev — opens the Electron window, no URL. E2E. none Runtime. The app is driven through its Electron window (pnpm dev). The server runs as the ghcr.io/scheron/daily-server image, or from the package pnpm build:server:package emits — cd apps/server/dist-server && npm install --omit=dev && node index.js start. That install is not optional: the workspace's better-sqlite3 is built for Electron's ABI, so a plain node cannot load the bundle.

bootstrap. pnpm install (apps/desktop's postinstall runs electron-builder install-app-deps) link. .env

Architecture

  • Layers: Model (SQLite CRUD, _rowMappers maps snake_case↔camelCase) → Service (business logic) → Controller (StorageController) → IPC → renderer store → component.
  • Renderer↔main is exclusively window.BridgeIPC (preload + contextBridge). No fs/electron in the renderer.
  • AI (apps/desktop/src/main/ai/): agent loop with Before/AfterToolCall hooks, running @daily/tools' shared tool set plus its own respond and read_url; delete tools suspend for user confirmation; only the respond tool is user-visible.

Conventions (enforced)

  • Public-before-private: public methods/exports first, private/helpers last; constructor after fields.
  • Comments follow the writing-comments skill.
  • Errors live in apps/desktop/src/shared/errors/<domain>/ — one file per Error subclass; inline throws use enum codes there.
  • type over interface (reserve interface for shapes a class implements).
  • Locality: types/constants at the narrowest scope; lift to apps/desktop/src/shared/ only when crossing the process boundary.
  • Motion: app animations currently run independently of OS Reduce Motion. A future app-level animations setting is deferred.
  • CHANGELOG: App Store-style, impersonal (no "you"), type-based sections. See .agents/skills/release-daily/; its optional release-media workflow covers feature previews and approved GitHub Release attachments.

Gotchas

  • Soft deletes only — set deletedAt, never hard-delete. Tasks are always scoped to a project (main always exists).
  • A project is Branch in the code. branchId, BranchModel, branches.store, and branches in the snapshot are all the project — one concept, two names, and the type name is the older one. The canonical word is project (CONTEXT.md); write it that way in anything a person reads. Renaming the type would move the snapshot shape, so it is not a drive-by.
  • Snapshot version: on any change to the sync snapshot shape, bump Snapshot.version in packages/protocol/src/types/sync.ts and handle older versions on read (a newer version aborts sync via SnapshotVersionAheadError).
  • Tailwind stays in devDependencies — as a prod dep it drags Rust natives into the asar.
  • macOS/arm64 only; Node ≥ 24.0.0, pnpm ≥ 10.26.0.

Skills

Project skills live in .agents/skills/, which Codex reads directly. Claude Code discovers the same skills through the .claude/skills symlink to ../.agents/skills. Add new skills under .agents/skills/.

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.