「service」の検索結果

Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model, MemoryClient/MemorySettings, the memory MCP server, or any of the framework integrations (LangChain, PydanticAI, CrewAI, AWS Strands, Google ADK, Microsoft Agent Framework, OpenAI Agents, LlamaIndex). Also use when the user mentions the hosted service at memory.neo4jlabs.com, NAMS, the Neo4j Agent Memory Service, the `nams_` API key prefix, or the hosted MCP endpoint. Also use when writing documentation, blog posts, tutorials, PRDs, or code samples for the project, when comparing agent memory approaches, or when positioning graph-native memory against vector-only approaches — even if the user doesn't explicitly name the package.

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

Generate complete service-level Terraform infrastructure with modules, environments, and CI/CD. Use when adding Terraform to a new service or bootstrapping infrastructure from scratch.

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

Design a service-learning project connecting genuine community need with embedded curriculum learning. Use when planning community projects, civic engagement, or social action units.

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

Scans a codebase and generates a self-contained HTML service-design journey map — NN/g combined customer journey + service blueprint format. Use when the user wants to map user journeys, create journey maps, build service blueprints, or understand user flows from code. Prompts for codebase path if not supplied. Works with any tech stack.

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

Reference for Android VPN/proxy service lifecycle: runtime coordinators, status/telemetry flow, where to make changes. Use when touching service start/stop, handover, or coordinator code.

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

Drafts professional services agreements for healthcare providers and clients, covering HIPAA/HITECH compliance, BAA requirements, Anti-Kickback and Stark Law guardrails, credentialing warranties, malpractice insurance mandates, and patient care continuity on termination. Use when drafting healthcare provider contracts, medical services agreements, physician independent contractor agreements, or healthcare consulting engagements.

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

Drafts a U.S. Consulting Services Agreement covering scope, compensation (hourly, fixed, retainer, hybrid), independent contractor classification, IP ownership, confidentiality, indemnification, liability caps, insurance, and dispute resolution. Use when drafting consulting contracts, professional services agreements, or independent contractor agreements.

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

Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".

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

Audit existing service mesh configuration — find mTLS gaps, traffic policy issues, and observability holes. Use when asked to "audit our service mesh", "find mTLS gaps", or "review traffic policy issues".

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

Network reachability and pivoting after an operator already has a foothold. Use to make previously unreachable hosts, subnets, services or listener directions reachable via Ligolo-ng, Chisel, GOST v3, SSH/native forwarding, socat/netsh, Microsoft Dev Tunnels, DNS/HTTP/QUIC fallback transports, and multi-hop routing. This module does not exploit services, obtain credentials, or own C2/persistence. Its success condition is changed reachability: the operator can route/connect to the intended internal network/service through the selected foothold.

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

Backend development patterns for services, error handling, logging, caching. Use when building backend services, APIs, or microservices.

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

Use to evaluate a service or feature against Downe's 15 principles of good services.

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

Evaluates OFS sector investments with rig count sensitivity, day rate analysis, and technology adoption curves. Use when analyzing oilfield services, evaluating service company economics, or assessing technology uptake.

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

Defines the structure and implementation of service classes, enforcing the use of interfaces, ServiceImpl classes, DTOs for data transfer, and transactional management.

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

Configure reverse proxy patterns across multiple tools including Nginx, Traefik, and ShinyProxy. Covers WebSocket proxying, path-based and host-based routing, SSL termination, and Docker label auto-discovery. Use when routing multiple services behind a single entry point, proxying WebSocket connections (Shiny, Socket.IO), auto-discovering Docker services with Traefik labels, or adding SSL termination to services that don't handle TLS natively.

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

Deploy and configure an API gateway (Kong or Traefik) to handle API traffic management, authentication, rate limiting, request/response transformation, and routing. Covers plugin configuration, upstream services, consumer management, and integration with existing infrastructure. Use when multiple backend services need a unified API endpoint, when centralized authentication or rate limiting is required, when implementing API versioning, or when needing detailed analytics and load balancing for microservices.

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

NestJS testing patterns: Test.createTestingModule for unit/integration, mocking providers, e2e tests with INestApplication + supertest, ORM mocking (TypeORM/Prisma/Mongoose), test fixtures. Use this skill to: - Write unit tests for services with mocked dependencies. - Write integration tests with real DI but mocked external services. - Write e2e tests for HTTP endpoints via supertest. - Mock repositories/Prisma client correctly. - Cover services and controllers to ≥80%. Do NOT use this skill for: - Test framework setup (Jest/Vitest config — usually already in place). - Frontend tests. - Load testing (out of QA scope).

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

State management for Angular 18-21: signals (signal/computed/effect), services-as-state, NgRx Store + Effects + Selectors, NgRx Component Store, NgRx Signals (newer signal-based store). RxJS essentials — operators, async pipe, takeUntilDestroyed, signal/observable interop. Use this skill to: - Pick the right state tool (signals / services / NgRx variant / vue-query equivalent). - Use signals correctly (signal/computed/effect — when each). - Build a Pinia-style service-as-state singleton. - Set up NgRx Store + Effects + Selectors. - Use RxJS without leaking subscriptions (async pipe, takeUntilDestroyed, Subject patterns). - Bridge signals ↔ observables via toSignal / toObservable. Do NOT use this skill for: - General Angular conventions (see angular-conventions). - Routing state (see angular-routing). - Form state (see angular-forms). - Testing state (see angular-testing).

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

GraphQL, WebSockets, and microservices patterns for NestJS. Apply only when the relevant package is in dependencies (`@nestjs/graphql`, `@nestjs/websockets`, `@nestjs/microservices`). Each section is orientation, not exhaustive — defer to NestJS docs for deep dives. Use this skill to: - Wire a GraphQL resolver (code-first) with class-validator inputs. - Build a WebSocket gateway with auth and room management. - Set up a microservice transport (TCP/RabbitMQ/NATS/Redis/Kafka) and message handlers. Do NOT use this skill for: - REST controllers (see nest-conventions + decorator-patterns). - ORM (see nest-data-layer). - Auth strategies (see security-analyst phase guidance).

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

Connect to and query ClickHouse (a local server or a ClickHouse Cloud service) from the terminal. For ClickHouse Cloud analytics, use the configured direct ClickHouse Query API endpoint with per-user CH_API_KEY and CH_API_SECRET credentials; do not use clickhousectl cloud service query. For local or host/port servers, use clickhousectl local client. Use when the user wants to run SQL against ClickHouse, explore schemas and tables, inspect Cloud services, or authenticate. For building a local dev environment or deploying to Cloud, defer to the official ClickHouse skills (see Scope).

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

Design AI customer service systems with handoff. TRIGGERS - Use when user needs help with ai-customer-service related tasks.

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

Package agency services. TRIGGERS - Use when user needs help with agency-service-packaging related tasks.

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

Plan advisory services for accounting firms. TRIGGERS - Use when user needs help with advisory-services-plan related tasks.

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

Post-deploy observability for production services — structured logging, RED metrics + Prometheus, Grafana dashboards, SLO-based alerting. Use when setting up monitoring or instrumenting a live service. Trigger on "add logging", "metrics", "dashboard", "alerting", "observability", "monitor this service".

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