Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

dayotter-overview

Sterne25

Forks5

Aktualisiert16. Juli 2026 um 11:31

Orientation for the DayOtter monorepo - layout, the single sources of truth (availability engine, sync worker), the load-bearing invariants (timezone discipline, confirm-first AI, encryption, SSRF-safe egress, single runtime), and how to build/test/verify. Load this first when starting work anywhere in the repo.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Dayotter

Dayotter/dayotter

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	dayotter-overview
description	Orientation for the DayOtter monorepo - layout, the single sources of truth (availability engine, sync worker), the load-bearing invariants (timezone discipline, confirm-first AI, encryption, SSRF-safe egress, single runtime), and how to build/test/verify. Load this first when starting work anywhere in the repo.

DayOtter overview

Open-core, AI-native team scheduling. Turborepo + pnpm. AGPLv3 - the whole product, including AI, self-hosts for free. Cloud-only infra lives in apps/web/lib/ee/, inert unless DAYOTTER_CLOUD=1.

Where code lives (API-first: domain logic in packages, never only in apps/web)

packages/core - crypto (AES-256-GCM), logger, SSRF safeFetch, and the availability engine (availability/engine.ts, pure + unit-tested).
packages/db - Drizzle schema split by domain + migrations (drizzle/).
packages/calendar - provider adapters (Google / Microsoft / CalDAV).
packages/integrations - adapterForConnection, CRM (Salesforce/HubSpot).
packages/jobs - BullMQ queue names + Redis connection.
packages/{notifications,emails,auth,plugin-host,plugin-sdk,plugins}.
apps/web - Next.js 15 App Router: (marketing) + (app) + (auth) route groups and the REST API under app/api. Domain helpers in apps/web/lib/*.
apps/worker - BullMQ workers: sync, reminders, briefings, webhooks, CRM sync.

Two single sources of truth everything else reads from:

Availability engine - computes bookable slots from schedule + busy cache.
Sync worker - projects provider calendars into the busy_blocks cache the engine reads. The engine never calls a provider directly.

Invariants (enforced in review - see docs/DECISIONS.md)

Timezone discipline. UTC instants in the DB; wall-clock always carries an IANA zone, resolved through Luxon. Engine returns absolute instants; booker tz is presentation-only. DST is unit-tested - keep engine.test.ts green.
Confirm-first AI, scheduling-scoped. AI drafts an editable proposal; never silently mutates the calendar. No general assistant/email/task features.
Encryption at rest. OAuth tokens, phone numbers, channel configs via @dayotter/core crypto + ENCRYPTION_KEY. Plaintext never hits DB or logs.
SSRF-safe egress. All untrusted outbound HTTP uses safeFetch (HTTPS-only, resolved-IP pinned, no redirects).
Single runtime. I/O-bound stack, native crypto - audited: no Go/Rust.

Verify before "done"

pnpm turbo typecheck
pnpm --filter @dayotter/core test   # 30, incl. DST
pnpm --filter @dayotter/web test    # ~85
npx biome check --write <files>     # biome - NOT prettier/eslint

Migrations: Drizzle, in packages/db/drizzle (numbered). Add schema in packages/db/src/schema/*, generate a migration, don't hand-edit applied ones.

Related skills

editions-and-billing, calendar-availability, plugins-extensibility, analytics, frontend-conventions. Human docs: docs/ARCHITECTURE.md, docs/DECISIONS.md.

Mehr aus diesem Repository

gleiches Repository

analytics

Dayotter/dayotter

DayOtter's optional client analytics module (Mixpanel + Google Analytics 4 + PostHog) in apps/web/lib/analytics.ts. Two independent switches - per-provider env config (deployer) and a per-browser opt-out (end user). Load this when adding tracking, wiring a new provider, or changing consent behavior.

2026-07-1625

calendar-availability

Dayotter/dayotter

How scheduling actually works in DayOtter - the pure availability engine (DST-correct, integer-ms slot math), the busy_blocks cache the sync worker maintains, provider adapters, best-effort push subscriptions, and the booking lifecycle fan-out. Load this when touching availability, calendar sync, busy caching, bookings, or the sync/reminder workers.

2026-07-1625

editions-and-billing

Dayotter/dayotter

How DayOtter's self-hosted vs cloud editions work, gated by the DAYOTTER_CLOUD deploy flag and lib/billing/edition.ts. Load this when touching billing, CRM, messaging, managed AI, the ee/ layer, or any feature that should behave differently on the hosted product - or when a "self-hosted / not configured" message shows up where cloud behavior was expected.

2026-07-1625

frontend-conventions

Dayotter/dayotter

apps/web UI conventions - theme tokens and class-based dark mode, the marketing/docs/blog width tiers, brand typography (Geist, no serif), illustration gotchas (baked light frames cause dark-mode edges), reveal animations, and the Card system. Load this when doing marketing or app UI work so new pages match the rest of the site.

2026-07-1625

plugins-extensibility

Dayotter/dayotter

DayOtter's plugin/extension system - in-process, config-listed plugins that extend the product without forking (notes, scribing, custom integrations, booking hooks). Covers the plugin-sdk/plugin-host packages, plugin_data storage, the host context (safeHttp via safeFetch), and the trust model. Load this when adding an extension point, writing a plugin, or touching the plugin host.

2026-07-1625

name	dayotter-overview
description	Orientation for the DayOtter monorepo - layout, the single sources of truth (availability engine, sync worker), the load-bearing invariants (timezone discipline, confirm-first AI, encryption, SSRF-safe egress, single runtime), and how to build/test/verify. Load this first when starting work anywhere in the repo.

DayOtter overview

Open-core, AI-native team scheduling. Turborepo + pnpm. AGPLv3 - the whole product, including AI, self-hosts for free. Cloud-only infra lives in apps/web/lib/ee/, inert unless DAYOTTER_CLOUD=1.

Where code lives (API-first: domain logic in packages, never only in apps/web)

packages/core - crypto (AES-256-GCM), logger, SSRF safeFetch, and the availability engine (availability/engine.ts, pure + unit-tested).
packages/db - Drizzle schema split by domain + migrations (drizzle/).
packages/calendar - provider adapters (Google / Microsoft / CalDAV).
packages/integrations - adapterForConnection, CRM (Salesforce/HubSpot).
packages/jobs - BullMQ queue names + Redis connection.
packages/{notifications,emails,auth,plugin-host,plugin-sdk,plugins}.
apps/web - Next.js 15 App Router: (marketing) + (app) + (auth) route groups and the REST API under app/api. Domain helpers in apps/web/lib/*.
apps/worker - BullMQ workers: sync, reminders, briefings, webhooks, CRM sync.

Two single sources of truth everything else reads from:

Availability engine - computes bookable slots from schedule + busy cache.
Sync worker - projects provider calendars into the busy_blocks cache the engine reads. The engine never calls a provider directly.

Invariants (enforced in review - see docs/DECISIONS.md)

Timezone discipline. UTC instants in the DB; wall-clock always carries an IANA zone, resolved through Luxon. Engine returns absolute instants; booker tz is presentation-only. DST is unit-tested - keep engine.test.ts green.
Confirm-first AI, scheduling-scoped. AI drafts an editable proposal; never silently mutates the calendar. No general assistant/email/task features.
Encryption at rest. OAuth tokens, phone numbers, channel configs via @dayotter/core crypto + ENCRYPTION_KEY. Plaintext never hits DB or logs.
SSRF-safe egress. All untrusted outbound HTTP uses safeFetch (HTTPS-only, resolved-IP pinned, no redirects).
Single runtime. I/O-bound stack, native crypto - audited: no Go/Rust.

Verify before "done"

pnpm turbo typecheck
pnpm --filter @dayotter/core test   # 30, incl. DST
pnpm --filter @dayotter/web test    # ~85
npx biome check --write <files>     # biome - NOT prettier/eslint

Migrations: Drizzle, in packages/db/drizzle (numbered). Add schema in packages/db/src/schema/*, generate a migration, don't hand-edit applied ones.

Related skills

editions-and-billing, calendar-availability, plugins-extensibility, analytics, frontend-conventions. Human docs: docs/ARCHITECTURE.md, docs/DECISIONS.md.