EllaLiu0401
- 16 skills
- 0 followers
- 8 hours ago last updated
- ▌ Task Completion Check · ellaliu0401Verify whether a coding task is complete by checking plan todos, file changes, TypeScript compilation, and linter errors. Use when the user asks to check if a task is done, verify completion, review progress, or validate implementation against the plan.
- ▌ Backend DB Conventions · ellaliu0401Backend database conventions for Aetheron Connect V2. Covers migration patterns, column type choices, and schema design rules. Use when writing migrations, adding new tables or columns, choosing column types, or reviewing database schema changes.
- ▌ Composio Org Sync Impl · ellaliu0401Implement the org-level Composio connection unification & sync plan (planning/engine/org-level-composio-sync.md, PR #891). Covers the entity switch (userId → orgId), the sync-write afterExecute hook, lazy reconcile as drift detector, webhook dispatch for expired events, Terraform subscription update, and the tenancy/rollout gotchas the review caught. Use when implementing any §4.1–4.6 section of that plan, touching composio-service.ts / tool-resolver.ts / webhooks/composio.ts / managed-app-repository.ts, or landing the org-level Composio entity flip.
- ▌ Frontend Error Handling · ellaliu0401Global frontend error-handling patterns for Aetheron Connect V2 (apps/web): classifying errors before defaulting to unknown, narrowing transient network detection (TypeError / DOMException), toast cooldown for simultaneous failures, and threading server-resolved feature flags through client Providers. Use when: (a) editing `QueryProvider.tsx`, any `useActionErrorHandler`-style hook, React Query `MutationCache.onError` / `QueryCache.onError` wiring, or global toast handlers; (b) adding `isTransientNetworkError` / network-error detection logic, toast deduplication, or server→client feature-flag context plumbing; (c) the user pastes a runtime error stack trace, a "Failed to fetch" / "Load failed" / "TypeError" / "Network connection failed" report, or a reproduction of unexpected toast spam; (d) investigating "why is the user seeing five identical toasts", "real bug got swallowed as a generic toast", or "client and server defaults diverged" questions.
- ▌ Pr Review · ellaliu0401 bundlePerform comprehensive GitHub PR review: analyze changes, check compliance with project rules (AGENTS.md, planning docs, design system), cross-reference existing reviewer comments, and post inline review comments via gh CLI. Use when the user shares a PR URL, asks to review a pull request, says "check this PR", "code review", "review #123", or "look at my changes".
- ▌ Ds Pr Review · ellaliu0401Review pull requests for the Aetheron Design System (aetheron-design-system). Checks component code, DaisyUI usage, TypeScript patterns, Storybook stories, a11y compliance, and theming correctness. Use when reviewing a PR in the design system repo, or when the user shares a DS PR URL and asks to review it.
- ▌
- ▌ Plain Language · ellaliu0401Explains technical work to a non-technical Chinese-speaking user in plain language. Translates jargon into "人话" with concrete examples, keeps replies short and non-repetitive, and uses a fixed two-part structure (一段话讲清楚是干嘛的 + 一小段技术架构). Use whenever explaining code, architecture, a bug, a PR, a plan, or any technical concept to this user; when the user says "听不懂 / 看不懂 / 太复杂 / 说人话 / 举个例子 / 太技术了"; or before sending any technical explanation in Chinese.
- ▌ Rbac Role Access · ellaliu0401Implement and modify role-based access control for Aetheron Connect V2. Covers backend route guards, frontend tab/section visibility, integration test patterns, and role hierarchy. Use when changing who can access a feature, adding role restrictions, reviewing RBAC, or when the user mentions roles, permissions, admin-only, superuser-only, or access control.
- ▌ Copy Staging Data · ellaliu0401Copy data from the Aetheron Connect staging database and S3 to the local development environment for testing. Use when the user wants to copy staging call records, interactions, or any feature data to their local DB for testing, says "copy from staging", "pull staging data", "test with staging data", provides a staging URL with a record ID, or mentions needing real data locally to test a Jira task or feature.
- ▌ Ds Code Authoring · ellaliu0401Conventions for writing component code in the Aetheron Design System (aetheron-design-system/packages/ui). Covers TypeScript prop patterns, DaisyUI class pitfalls, Storybook story patterns, and common review feedback. Use when creating or editing components, stories, or hooks inside the design system repo, or when the user mentions DS components, ChatComposer, DaisyUI classes, or Storybook stories.
- ▌ Slack Status Update · ellaliu0401Draft and send Slack status update messages for engineering work. Use when the user asks to write a Slack message, draft a status update, send a message to a teammate or channel about bugs, issues, investigation results, PRs, or asks for support/help via Slack.
- ▌ Frontend Code Checks · ellaliu0401Pre-submission checks for Aetheron Connect V2 frontend code in apps/web. Captures recurring reviewer feedback (HTML semantics, img hygiene, silent catch, utility reuse, DS prop conventions, visual state single-source-of-truth, React Query retry/staleTime/suppressGlobalError defaults, timezone-safe date rendering, status-enum forward-compat, mutation error three-thing rule, single-record API lookup over listX(limit:100), shared hook test coverage) so the agent surfaces these issues before the PR is opened. Use whenever writing or editing code under apps/web, adding a useQuery/useMutation, rendering a date-only string, branching on a backend status enum, looking up a single entity by id, extracting a shared hook, or before marking a frontend task complete.
- ▌ Sentry Observability · ellaliu0401Sentry SDK + replay + structured-logger patterns for Aetheron Connect V2. Covers `beforeSend` vs `ignoreErrors`, canary sampling, tag-aware bypass, engine-agnostic regex naming, replay-coupling semantics, the `logger.warn` → Sentry capture threshold, and structured error-payload conventions. Use when: (a) editing `sentry.client.config.ts` / `sentry.server.config.ts` / `apps/api/src/sentry.ts`; (b) adding or filtering `Sentry.captureException` / `captureMessage` sites, configuring replays or sampling rates, or routing structured logger errors into Sentry; (c) the user pastes a Sentry issue URL — e.g. `https://aetheron.sentry.io/issues/<id>/?project=...&query=...`, any `*.sentry.io/issues/` link, or a `sentry.io` issue/event/replay link — and asks to triage, debug, classify, decide whether to filter, or root-cause the error; (d) investigating "why didn't this error reach Sentry", "Sentry noise spike", "should I suppress this error", or "is this a real bug or expected noise" questions; (e) reviewing PRs that tou
- ▌ Update Ds Dependency · ellaliu0401Update design system dependencies. Covers two workflows - (A) modify a dependency INSIDE the local DS package (aetheron-design-system/packages/ui), and (B) upgrade @aetheronhq/ui to a published version in the consumer app (apps/web). Use when the user wants to update/add/remove a package in the design system, OR bump @aetheronhq/ui to a new version like "ui-v3.24.0".
- ▌ Pr Fix · ellaliu0401Fix PR review comments from GitHub: fetch all comments, analyze each one (bug vs nitpick vs informational), present a summary, ask for confirmation before making code changes, add test coverage when requested, and verify nothing breaks. Use when the user shares a PR URL and asks to fix, address, or resolve review comments/feedback.