Esposter

Esposter TypeScript conventions — banned patterns (Omit over Except, forEach, parameter properties, the void operator), as unknown as treated like any (model the type instead; the rare mock and library-seam exceptions), declare over ! on class fields, arrow functions and overloads, neverthrow promise style, InvalidOperationError, guard clauses, exhaustive switch guards, enum naming/refs/values arrays, discriminant-keyed maps for polymorphic dispatch, and the string "" sentinel with the null-vs-undefined rules. Apply when writing any TypeScript in this project.

Esposter vue-phaserjs integration patterns — component inventory, markRaw for Phaser objects in Pinia stores, configuration Pick pattern, all-configuration-keys-present-at-setup. Apply when writing Phaser game objects, stores, or vue-phaserjs components.

Esposter git workflow conventions — commit message format, safety rules, and branch hygiene. Apply when running git operations or advising on source control workflows.

Esposter pnpm script reference — packages/app scripts (lint, typecheck, test, format, dev, build) and the root scripts (test, coverage, depcruise:graph, outdated:dependencies). Apply whenever running or recommending package scripts.

Esposter Vitest testing conventions — describe with function refs, canonical test values, takeOne for unsafe index access, destructuring from stores/composables, mock session patterns (getMockSession/mockSessionOnce/replayMockSession), mock cleanup by creation style, toThrowErrorMatchingInlineSnapshot as the only error assertion, the node-default test environment (nuxt only via per-file directive; stub window for client/server paths), bundle-size snapshot tests, and type-level conventions for .test-d.ts files. Apply when writing .test.ts or .test-d.ts files.

Esposter responsive/mobile UI conventions — command bars collapse into a single overflow dropdown of icon+text list items on narrow viewports, which controls never collapse, and when flex-wrap is the allowed exception. Apply when adding or editing any toolbar, action row, or button group that must work on mobile.

Esposter Vue 3 component architecture — the shared Styled/App shell primitives, same level of abstraction, the wrapper + pure-child pattern for async data, generic SFCs, per-variant type correctness, is-prefixed boolean props typed as the non-default literal, present-tense emit names, component folder naming and Nuxt auto-import name collapse, defineSlots and conditional slot forwarding, slot extraction, array + v-for over hardcoded list items, shared list-item shells with action slots, permission-filtered action items, one affordance per action, singleton dialogs over per-item dialogs, page decomposition, and maximal component granularity. Apply when designing, decomposing, naming, or refactoring Vue components.

Esposter Vuetify 4 conventions — StyledButton for primary actions, :to for plain navigation with @click navigateTo for logic-then-navigate, v-prefixed auto-imported composables (useVDisplay/useVTheme), global defaults never repeated, v-btn tooltips, mergeProps for nested activators, typed SelectItemCategoryDefinition for selects/lists/menus (clearable banned), enum-value-as-display-title, dialog form validity (StyledFormDialog vs StyledEditFormDialog), StyledList, useVRules form validation, StyledAvatar, CSS custom properties over SASS variables, and scrollspy sub-nav. Apply when writing or reviewing Vuetify components, dialogs, selects, forms, or lists.

Esposter routing conventions — declarative links via NuxtLink/NuxtInvisibleLink or Vuetify :to (raw <a> lint-banned), navigateTo for imperative navigation (always awaited or returned — never a floating statement), useRouter for reactive route reads, route-synced tabs with useEnumRouteQuery, and definePageMeta validate + key for optional/nested segments. Apply when adding links, navigating in code, reading route params/query, syncing tabs to the URL, or writing pages with dynamic or optional route segments.

Esposter Pinia store conventions — full store name, destructure with storeToRefs, store-to-store dot-access for refs (methods may be destructured), per-service dialog stores, blade-scoped store state torn down on unmount, never redirecting store functions through wrappers, selection state in the store, useDataMap vs a plain Map, cursor pagination helpers, tRPC mutation placement via useMutation with optimistic rollback, createOperationData CRUD verbs and store* subscription handlers, CRUD/parameter naming, full tRPC input objects, minimal-input actions, reusing existing store maps, reactive Map mutations, markRaw for class instances, and session auth in stores. Apply when writing or reviewing any Pinia store, or deciding whether logic belongs in a store.

Esposter messaging feature (esbabbler) conventions — Discord parity rule, display name/nickname resolution, push notification titles, store-mutation pattern (subscriptions as source of truth), online-subscribable watch sources, and scheduled-message jobs. Apply when working on the messaging module (packages/app/app/…/message/, server/trpc/routers/message/, userToRoom, roles, members, rooms). Calls/voice internals live in the esbabbler-call skill.

Esposter model-delegation conventions — the main session does all thinking (specs, proposals, architecture, review); mechanical implementation is delegated to background subagents with self-contained prompts. Apply when deciding whether to implement in-session or delegate, and when writing a delegation prompt.

Esposter dependency update process — all versions in pnpm-workspace.yaml catalog, caret prefix rules, exact-pinned packages (drizzle-kit/drizzle-orm RCs), version-capped packages (h3), and tracked open issues. Apply when updating package versions.

The single entry point for every code review — working diff, branch, or PR number. Always runs the project opus-pinned workflow script; never an inline/local review, never the review skill, never the built-in workflow by name. Apply on any review request.

Esposter CodeRabbit review conventions — retrieving review feedback across all three endpoints (nitpicks live in the review body, not inline comments; the bot login is coderabbitai[bot]), replying to findings, checking review state before pushing (never push into a running review), .coderabbit.yaml is read from the PR base branch (normally develop), per-file path_filters for mechanical renames, and the standardized exclude/re-enable commit pair. Apply when fetching, addressing, or replying to CodeRabbit comments or nitpicks, before any git push to a branch with an open PR, when a PR is too large for review, when excluding files from CodeRabbit, or when the user says "remove the exclusions".

Esposter Drizzle ORM conventions — bare column builders (camelCase applied by the pgTable wrapper), pgTable wrapper for metadata, schema placement, select patterns, relational vs SQL-style API preference, and v2 relation definitions (defineRelationsPart, optional:false, naming). Apply when writing or modifying DB schema files in packages/db-schema or tRPC routers.

Esposter oxlint + ESLint linting conventions — the explicit correctness category rule in .oxlintrc.json (eslint-plugin-oxlint replaces default categories), method-signature-style exceptions (built-in augmentations, third-party .d.ts), prefer-named-capture-group naming patterns, and when to use disable directives. Apply when fixing lint errors, editing .oxlintrc.json, investigating slow ESLint rules, or adding regexes/interface declarations.

Esposter UnoCSS Attributify Mode styling conventions — prop-based attributes for all static styles, class only for scoped CSS refs / dynamic bindings / third-party selectors, layout dimensions (no magic rem on regions; Vuetify grid, flex-1), full-page surface layout (v-sheet over bg-surface) and borders drawn exactly once, slash/fraction utilities, theme colours and text-info links, arbitrary values and CSS variables, abbreviated utilities (op-, b-, rd-), gap directionality, the parent owning spacing (gap/padding over child margins), rem over px, and style-block rules. Apply when writing or reviewing styles in .vue or .scss files, or laying out a page, panel, sidebar, or border.

Esposter Vue 3 SFC conventions — macro ordering, script-setup declaration order, template patterns and attribute ordering, inline handlers, v-model vs split bindings (never normalizeString in Vue), refs/computed/template refs, the watch decision tree and watch aliases, auth session call forms, browser globals, SSR guards via getIsServer, and upsert form mode. Apply when writing or reviewing .vue files.

Esposter file and folder organisation — the alias imports (shared/root/app-source, never relative), one export per file, no export{} syntax, models vs services vs utils vs constants, the sole-consumer subfolder rule, extracting duplication to one primitive, constant maps with as-const-satisfies, the LocalStorageKey registry, generic Vue components, command pattern field ordering, symlinks via PowerShell, creating a new workspace package (tsconfig/rolldown/eslint/peerDependencies), renaming without re-export aliases, and file length. Apply when creating, moving, renaming, or organising any file, export, constant, or package.

Esposter messaging calls (esbabbler) implementation — call session architecture, standalone vs room calls, random id generation, call lifecycle/leave boundaries, client call stores, participant Map design, RoomPermission bits, AdminActionType, and the knock/admit lobby. Apply when working on calls (store/message/room/call/, liveKit.ts, callSession routers, /calls pages).

Esposter Vue 3 composable and form patterns — cursor pagination (store + useRead* composable + StyledWaypoint), server search-as-you-type (useAutoSearch/useCursorSearcher, hand-rolling banned), MaybeRefOrGetter vs plain args, the three validation-rule layers (global alias / composable / Ajv keyword), extracting mutation blocks with builder args, permission-gated settings tabs, schema-controlling selectors in the prepend-form slot, type-driven state reset via create maps, toRawDeep, resource cleanup, useOnline, SSR-safe watches, dirty-check saves with useSave, async sequencing primitives (getConcurrentFunction for reads, getSequentialFunction for writes, getSynchronizedFunction/useQuery — hand-rolling stale guards banned), dialog data loading, capturing the instance before await, use*Subscribables, and the offline IndexedDB pagination cache. Apply when writing or reviewing a composable, form dialog, paginated list, search input, offline cache, or browser-aware reactive code.

Esposter Azure Table Storage patterns — key constants, partition/row key design, reverse-ticked timestamps, batch write/pagination, and bounded counting after capped reads. Apply when reading or writing Azure Table Storage data (messages, moderation logs) in server code.

Esposter skill-writing conventions for .claude/skills — frontmatter that drives selection, one owner per topic, capturing session learnings into skills in the same session (and empirically verifying + fixing stale skill claims instead of obeying them), don't restate what an enforcer already checks, generic placeholders over identifiers from one change, magnitudes over incident numbers, and declaration layout. Apply when creating, editing, splitting, merging, or reviewing any SKILL.md, when a session discovers or corrects a convention, or when deciding which skill a new rule belongs in.

Esposter context and turn efficiency — delegate wide reads and keep the dumps out of the session, never tail a subagent's transcript, batch verification into one pass at the end, poll for a condition instead of sleeping, and diff against a clean tree before chasing errors in files you never touched. Apply when a task spans many files, when choosing how to wait on something, or when deciding what to pull into the session.

Esposter — how to launch the app and drive it in a real browser to verify UI changes: the dev server's port fallback and client-bundle warmup, seeding a better-auth session for auth-gated routes, driving headless Chrome over CDP with no extra dependencies, and the two traps (temp files under packages/app corrupt the dev build; async components resolve long after the document is complete). Apply when verifying a UI change visually, screenshotting a page, or reproducing something that only shows up in the running app.

Esposter GrapesJS editor conventions — useGrapesJsEditor init composable, the resource-backed storage adapter, the FileAssets upload adapter, block-category re-sync via setBlocks, save-time HTML/CSS capture for the published views, and merge-field/survey-invite blocks. Apply when working on Resource/Email/Editor.vue, Resource/Webpage/Editor.vue, their View.vue renders, the emailEditor/webpageEditor stores, or any GrapesJS-backed feature.

Esposter Claude Code permission-rule conventions for the allow-only .claude/settings.local.json — the shipped file is the standard (every rule is the trailing space-star form, colon sub-scripts get their own rule), mirroring rules across Bash and PowerShell, and sorting. Generic harness semantics live in the update-config skill. Apply when editing settings.local.json or debugging why a command still prompts.

Esposter benchmarking conventions — colocated *.bench.ts files, vitest bench, the BenchmarkMarkdownReporter that writes colocated per-file *.bench.{json,md} beside each source, the StableBenchmarkRunner, the dormant CodSpeed wiring, and where bench tooling lives (@esposter/shared-node). Apply when adding or editing benchmarks.

Esposter rolldown build conventions — shared rolldown configs, external list rules, and self-contained bundle packages. Apply when adding packages or editing rolldown configs.

Esposter documentation conventions for packages/app/content/docs (the in-app /docs section rendered by @nuxt/content) — the Mermaid diagram mandate parse-validated by content/docs.test.ts (a syntax error fails pnpm test; no semicolons in labels), location-carries-status (area vs proposals vs deferred/rejected), plain .md with GFM only, the two-field frontmatter, feature-page template, registering pages in index.md and DocsSectionGroupsMap.ts, repo-wide standards belong in architecture/, and one-area-at-a-time working. Apply when creating, updating, or referencing any documentation page, proposal, roadmap, or deferred/rejected idea.

Esposter Error Handling Conventions — neverthrow getResult/getResultAsync (try/catch banned), chaining patterns, finalizers, tRPC backend guards, and Azure Functions logging/retry (context.error, logAndRethrow, fatal vs best-effort). Apply when handling errors or logging in components, composables, stores, server routes, tRPC routers, or Azure Functions handlers.

Esposter code formatting — blank-line placement around consts/returns/blocks, the test-file exception, and comment attachment/content rules (comment only exceptional behaviour, describe the present never the history, keep error-text quotes). Apply when writing or editing any file's whitespace or comments.

Esposter naming conventions — booleans (is*/has*/show*), functions (get*/read*/store*/on*), variables (no abbreviations, Ms suffix, userId), numbers/time, import aliases, interfaces/classes (A prefix, no With prefix), regex (_REGEX). Apply when naming any identifier. Framework-specific naming lives in the vue/pinia/trpc skills.

Esposter Pulumi infrastructure conventions for packages/infra — Azure Native resources, import migration, generated ctix entrypoint, one resource per file, and generated output safety.

Esposter README conventions — the anchor+emoji heading template, the published-vs-private split that drives both badges and the docs link target, when Getting Started is omitted, the 14-package summary table, and GitHub blob/tree URL rules. Apply when creating or updating any README.md in this monorepo, including the root one.

Esposter slash command conventions — parameter definitions, execution modes, the chip-based parameter UI and its safeParse/setErrors validation, message formatting, and adding new commands. Apply when writing or modifying slash commands, useExecuteSlashCommand, SlashCommandDefinitionMap, or the SlashCommandParameters components.

Esposter string normalization and HTML sanitization conventions — normalizeString is the default trim in app code and in base Zod schemas (never in Vue — the vue skill owns that); sanitizeTextHtml is declared at the Zod boundary in base db-schema schemas (never manual frontend calls). Exceptions — user-facing transformation actions, standalone packages, and localStorage drafts.

Esposter Tiptap/ProseMirror conventions — suggestion extensions, plugin key uniqueness, VueRenderer v-show rule, and SuggestionTrigger enum. Apply when writing or modifying Tiptap extensions, suggestion lists, or editor composables.

Esposter tRPC conventions — procedure typing with generics, router structure, error handling, and router test patterns. Apply when writing tRPC routers, procedures, or router tests.