開発のスキル

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 REST endpoint patterns in melosys-api's frontend-api module. Use when: (1) Creating new REST endpoints for melosys-web, (2) Understanding controller patterns and Swagger documentation, (3) Working with DTOs and request/response objects, (4) Understanding exception handling and HTTP status codes, (5) Adding access control to endpoints. Triggers: "new endpoint", "REST controller", "@RestController", "add a DTO", "ResponseEntity", "Aksesskontroll", "access control on endpoint", "Swagger/@Operation", "return 404/403/401/400", "@Protected", "frontend-api", "search endpoint", "/sok".

日本語の概要は準備中です。原文の説明を表示しています。

Expert knowledge of Fagsak (case) domain in melosys-api. Use when: (1) Understanding the fagsak lifecycle and status transitions, (2) Working with actors (aktører) - citizens, employers, authorities, (3) Debugging case creation, closure, or type/theme changes, (4) Understanding relationship between fagsak and behandling, (5) Working with EU/EEA authorities or bilateral treaty authorities. Triggers: "fagsak", "saksnummer", "MEL-", "aktør", "sakstype", "sakstema", "avslutt sak".

日本語の概要は準備中です。原文の説明を表示しています。

Modular monolith architecture overview for melosys-api. Use when needing to understand module structure, dependencies between modules, where to place new code, or when changes in one module might affect others. Triggers: "architecture", "module dependencies", "where should I put", "which modules", "dependency graph".

日本語の概要は準備中です。原文の説明を表示しています。

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 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.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a Spark implementation needs an evidence-based review for correctness, ownership, compatibility, failure handling, maintainability, and unnecessary complexity.

日本語の概要は準備中です。原文の説明を表示しています。

Vets third-party skills, plugins, MCP servers, GitHub Actions and model weights before install, with a verdict (PASS, CONDITIONAL, HOLD, FAIL) and install terms. Trigger on any should-I-install question, even with its files or hooks pasted in or a scan already clean; is this skill safe, vet this MCP server, check this GitHub Action, is this checkpoint safe or commercially usable, what does this installer write, a licence check before a fold-in, what changed in a plugin update; or say /rw-trustwarden (vet, revet, terms, refresh). Uses skillspector, zizmor, pinact and Scorecard when present; lists files no scanner read. Runtime permissions are gatewarden's; secrets shieldwarden's; your own skills skillwright's; sandboxing a download hypervrunner's.

日本語の概要は準備中です。原文の説明を表示しています。

Use psamvault MCP server: credential vault, browser login, API key injection, .env secret protection. MCP tools keep secrets out of the agent's context window.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Creates or adds Convex to an app. Use for new Convex projects, npm create convex@latest, frontend setup, env vars, or the first npx convex dev run.

日本語の概要は準備中です。原文の説明を表示しています。

Patterns for scaling read-heavy Convex apps to millions of users. Use when optimizing bandwidth, reducing query costs, fixing slow queries, creating digest tables, replacing reactive subscriptions with one-shot fetches, adding compound indexes, debouncing writes, rate-controlling backfills, or running npx convex insights. Trigger when users mention "scale", "bandwidth", "performance", "optimize", "slow queries", "expensive queries", "digest table", "denormalize", or "thundering herd" in the context of Convex.

日本語の概要は準備中です。原文の説明を表示しています。

Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.

日本語の概要は準備中です。原文の説明を表示しています。

Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app.

日本語の概要は準備中です。原文の説明を表示しています。

Watch for the next dev/prod error or request in a Convex app and react to it.

日本語の概要は準備中です。原文の説明を表示しています。

Create Convex queries, mutations, and actions with proper validation, authentication, and error handling. Use when implementing new API endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

Convex backend specialist. Use this agent for any code inside a `convex/` directory — function definitions, schemas, indexes, queries, mutations, actions, HTTP endpoints, cron jobs, file storage, auth wiring, and component installation. Knows the object-form function syntax, validator patterns, resource limits, and component ecosystem that generic Claude routinely gets wrong.

日本語の概要は準備中です。原文の説明を表示しています。

Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.

日本語の概要は準備中です。原文の説明を表示しています。

Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.

日本語の概要は準備中です。原文の説明を表示しています。

Initialize a new Convex project from scratch or add Convex to an existing app. Use when starting a new project with Convex, scaffolding a Convex app, or integrating Convex into an existing frontend.

日本語の概要は準備中です。原文の説明を表示しています。

Pull version-current Convex docs for the version this project uses — pin the installed version, fetch page-as-markdown or check node_modules types, freshness hierarchy — instead of writing a possibly-stale API from memory.

日本語の概要は準備中です。原文の説明を表示しています。

Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.

日本語の概要は準備中です。原文の説明を表示しています。

Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.

日本語の概要は準備中です。原文の説明を表示しています。

Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.

日本語の概要は準備中です。原文の説明を表示しています。