4.1천건 · 관련도순
Troubleshoot and debug LiveAvatar integration issues. Use when the user's LiveAvatar integration isn't working, the avatar is silent, audio is garbled, sessions fail to start, events aren't received, or they're getting API errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "最小再現環境を作って", "再現環境を構築して", "問題を切り分けたい", "パッケージの不具合か確認したい", "create a minimal reproduction", "isolate the issue", "build a repro environment", "reproduce this bug", "narrow down the cause", "is this a package bug or my code", "このPRの問題を再現して", "this commit broke something", or wants to determine whether a bug is caused by a package, the environment, or application code. Accepts PR URLs, commit hashes, or branch names as input.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of membership (medlemskap) domain in melosys-api. Use when: (1) Understanding pliktig vs frivillig membership determination, (2) Debugging medlemskapsperiode creation and updates, (3) Understanding trygdedekning combinations and rules, (4) Investigating MEDL synchronization issues, (5) Understanding membership status transitions and innvilgelsesresultat, (6) Working with UtledMedlemskapsperioder for proposal generation, (7) Understanding the relationship between bestemmelse, medlemskapstype, and trygdedekning. Triggers: medlemskapsperiode, pliktig, frivillig, trygdedekning, MEDL, innvilgelsesresultat, medlPeriodeID, bestemmelse.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of A1 statistics publishing to data warehouse in melosys-api. Use when: (1) Understanding utstedt A1 Kafka publishing, (2) Debugging UtstedtA1Service or Kafka producer issues, (3) Understanding DVH/data warehouse integration, (4) Investigating A1 statistics message format and schema.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Person data integration (PDL) in melosys-api. Use when: (1) Working with person data from PDL (Person Data Lake), (2) Understanding identity types (fnr, aktørID, NPID), (3) Working with addresses, family relations, or citizenship, (4) Debugging person data lookup issues, (5) Understanding the mapping between PDL and domain models.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Journalføring (document archiving) in melosys-api. Use when: (1) Creating/updating journalposts (Joark API), (2) Retrieving documents from SAF (GraphQL), (3) Understanding document workflows, (4) Debugging journalpost issues, (5) Mapping document types and categories. Triggers: "journalpost", "journalføring", "Joark", "dokarkiv", "SAF", "dokumentoversikt", "hentDokument", "ferdigstill journalpost", "Variantformat".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of SED/EESSI integration in melosys-api. Use when: (1) Understanding SED document types (A001, A003, H-series, X008), (2) Debugging SED sending/receiving flows and RINA integration, (3) Working with BUC (Business Use Case) creation and management, (4) Understanding saga steps for SED handling (SEND_VEDTAK_UTLAND, SED_MOTTAK_RUTING), (5) Troubleshooting mottakerinstitusjoner (recipient institutions) issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Kafka event streaming patterns in melosys-api. Use when: (1) Understanding Kafka producers and consumers, (2) Debugging Kafka message processing issues, (3) Understanding topic configuration and message schemas, (4) Investigating SkippableKafkaErrorHandler and error handling, (5) Understanding Aiven Kafka setup and security configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Brev (letter generation) in melosys-api. Use when: (1) Producing letters and decision documents (vedtaksbrev), (2) Understanding Dokgen templates and mapping, (3) Configuring letter recipients and distribution, (4) Debugging letter generation issues, (5) Adding new letter types or templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Employer/Employment integration (EREG/AAREG) in melosys-api. Use when: (1) Working with organization data from EREG (Enhetsregisteret), (2) Working with employment data from AAREG (Arbeidsforhold), (3) Understanding employer/organization lookup, (4) Debugging employer or employment issues, (5) Understanding the mapping between register data and domain models. Triggers: orgnummer, arbeidsforhold, EREG, AAREG, Enhetsregisteret, registeropplysninger, ansettelsesperiode, saksopplysning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Altinn A1 application processing for posted workers in melosys-api. Use when: (1) Understanding Altinn søknad/skjema processing, (2) Debugging MedlemskapArbeidEOS form mapping, (3) Understanding SoeknadMapper transformations, (4) Investigating posted worker application issues, (5) Understanding the MOTTAK_SOKNAD_ALTINN saga flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Behandling (case treatment) domain in melosys-api. Use when: (1) Understanding the behandling lifecycle and status transitions, (2) Debugging issues with behandling creation, status changes, or closure, (3) Understanding relationships between Fagsak, Behandling, and Behandlingsresultat, (4) Investigating why a behandling is stuck or has wrong status, (5) Understanding Behandlingstyper, Behandlingstema, Behandlingsstatus enums, (6) Debugging journalføring or SED-triggered behandling creation, (7) Understanding behandling creation via saksflyt sagas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of the melosys-api Oracle database schema. Use when: (1) Writing SQL queries against the melosys database, (2) Understanding table relationships and foreign keys, (3) Debugging data issues by querying the database, (4) Understanding what data is stored where, (5) Creating or modifying Flyway migrations, (6) Mapping domain entities to database tables. Triggers: SQL against melosys DB, table/column lookup, FK relationships, "where is X stored", "what column stores X", "why is data missing", beh_resultat_id, behandlingsresultat_id, saksnummer, schema.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug and troubleshoot WorkOS AuthKit authentication issues with Convex. Use when authentication fails, JWT validation errors occur, user identity returns null, email claims are missing, admin access checks fail, or sign in button does not work. Supports Netlify deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other frontends.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes bounded context boundaries in DDD projects. Detects cross-context coupling, shared kernel violations, context mapping issues, and ubiquitous language inconsistencies. Generates context map diagrams and boundary recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.