'software' 검색 결과

Reconstructed reference notes on EASA acceptable means of compliance for airborne software and airborne electronic hardware, built from AMC 20-115D (ED Decision 2017/020/R, AMC-20 Amendment 14, consolidated in Amendment 23) and AMC 20-152A (ED Decision 2020/010/R, AMC-20 Amendment 19, consolidated in Amendment 23), read from the Easy Access Rules AMC-20 compilation (Amendment 23, June 2023) and pinned 2026-09-26. Use for EASA software means of compliance, EASA AEH means of compliance, AltMoC, ETSO software, and the joint software and hardware certification workflow. SCOPE LIMITS: the two AMC sections only; no FAA content (use faa-8110-49); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, or supplement clause text (use avionics-signpost to name them); no Part-21 body; no bulk AMC-20; AMC 20-193 and AMC 20-189 are name-only; reflects Amendment 23 as consolidated in the June 2023 EAR, not a later AMC-20 amendment; synthesized reference notes, not legal advice and not the official AMC. LICENCE: per-document (EASA site reproduction-with-acknowledgement grant, qualified by ED Decision all-rights-reserved footers); pack-level commercial use is not granted.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit required bioinformatics command-line tools against Lmod or Environment Modules on Linux HPC clusters, resolve executable and version requirements, and reproducibly deploy missing software through a site-approved EasyBuild, Spack, Bioconda/micromamba, Apptainer, binary, or source-build workflow. Use when Codex must inspect module availability, diagnose a missing or wrong-version bioinformatics tool, install scientific software on Slurm/PBS clusters, publish or validate modulefiles, or produce an auditable and rollback-ready cluster software deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit required bioinformatics command-line tools against Lmod or Environment Modules on Linux HPC clusters, resolve executable and version requirements, and reproducibly deploy missing software through a site-approved EasyBuild, Spack, Bioconda/micromamba, Apptainer, binary, or source-build workflow. Use when Codex must inspect module availability, diagnose a missing or wrong-version bioinformatics tool, install scientific software on Slurm/PBS clusters, publish or validate modulefiles, or produce an auditable and rollback-ready cluster software deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coordinate software investigations, implementation, code reviews, and testing through Codex tasks in desktop, remote, or cloud environments. Inspect pull requests and automated checks, follow up on authorized fixes, and report results with verification limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate bugs and implement requested features
• Review code and run relevant tests
• Diagnose blocked pull requests

Find available computers and remote environments, then start or continue a task in the requested location. Route work involving files or apps on the user's computer to that computer, and follow progress while preserving the selected environment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Start a task on a named remote environment
• Route work involving files on your own computer
• Select your computer for work with a desktop app

Find Danish jobs for graduates and highly educated candidates through Akademikernes Jobbank. Filter by industry, education, region, or remote work, then retrieve posting details for graduate trainee, Ph.d., postdoc, and other roles.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find graduate trainee positions
• Search for Ph.d. and postdoc openings
• Look for fully remote software jobs

Search software, data, and engineering jobs across countries through freehire.me. Filter by skills, seniority, location, posting age, and remote work, and retrieve full descriptions to assess opportunities or inspect a specific posting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find remote React jobs in the EU
• Search recent DevOps openings in Germany
• Compare senior backend engineering roles

Find Danish jobs for graduates and highly educated candidates through Akademikernes Jobbank. Filter by industry, education, region, or remote work, then retrieve posting details for graduate trainee, Ph.d., postdoc, and other roles.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find graduate trainee positions
• Search for Ph.d. and postdoc openings
• Look for fully remote software jobs

Use Reasonix to build or improve a Python command-line interface for existing software. The workflow covers source analysis, interactive commands, JSON output, tests, documentation, and installation checks using the software’s own backend where possible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build command-line access to a GUI application
• Add missing features to an existing command-line interface
• Test commands against the actual software backend

Find marketing ideas for a SaaS or software product based on its stage, audience, budget, and team. Draw from 139 ideas to shortlist relevant options, with starting steps, expected outcomes, and resources needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding new ways to promote a software product
• Choosing marketing tactics on a limited budget
• Exploring promotion ideas before launch

Deploy osquery on Windows, macOS, and Linux to inspect processes, listening ports, software, and system settings using SQL, a database query language. Configure scheduled checks and centralized management to support threat hunting and compliance monitoring.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploying osquery across Windows, macOS, and Linux
• Investigating suspicious processes and network connections with SQL
• Periodically checking software inventories and system settings

Create Mermaid diagrams from text to explain software structure, API interactions, workflows, and database relationships. The skill guides diagram selection, syntax, styling, and export, helping keep visual documentation editable and stored alongside code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explaining system architecture with diagrams
• Mapping API requests and responses
• Documenting database table relationships

Connect business software to Claude by checking existing connectors first, then Zapier or scheduled exports. The skill narrows the task, configures access, tests real data, and explains limits, with approval required for write actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect business software that has no native Claude connector
• Retrieve open work orders for a daily briefing
• Use scheduled exports when direct connections are unavailable

Turn requirements for software or other multi-step work into a structured plan with an approach, constraints, and verification steps. It also helps develop existing plans, researching decisions before handing the work over for execution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning implementation from requirements
• Breaking complex work into manageable steps
• Adding detail to an existing plan

Prepare reproducible setup and removal instructions for software environments on Open-Science SSH hosts, including Slurm clusters. Check available tools, define named activation settings, and validate the environment where jobs run after the user installs it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a remote environment for required packages
• Making job environment activation repeatable
• Checking software and GPU operation on Slurm nodes

Build a software quality assurance process with structured test cases, execution tracking, bug severity levels, and quality metrics. Includes templates for progress reports and team handoffs, plus prompts for agent-driven test execution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a software QA process
• Standardizing test cases and bug reports
• Tracking test progress and release criteria

Architecture patterns, design principles, and proven recipes for building robust robotics software. Use this skill when designing robot software architectures, choosing between behavioral frameworks, structuring perception-planning-control pipelines, implementing state machines, designing safety systems, or architecting multi-robot systems. Trigger whenever the user mentions behavior trees, finite state machines, subsumption architecture, sensor fusion, robot safety, watchdogs, heartbeats, graceful degradation, hardware abstraction layers, real-time constraints, or software architecture for robots. Also applies to sim-to-real transfer, digital twins, and robot fleet management.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Asure Software integration. Manage data, records, and automate workflows. Use when the user wants to interact with Asure Software data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AFAS Software integration. Manage data, records, and automate workflows. Use when the user wants to interact with AFAS Software data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Software design principles, patterns, and architecture from SOLID through distributed systems. Covers the five SOLID principles with violations and fixes, DRY/KISS/YAGNI heuristics, separation of concerns, 12 GoF design patterns organized by intent (creational, structural, behavioral), architectural patterns (MVC, MVP, MVVM, layered, hexagonal, microservices, event-driven), coupling and cohesion metrics, dependency injection, and the design decision framework for choosing between competing approaches. Use when making design decisions, reviewing architecture, refactoring code, or teaching software engineering principles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deterministic Software Graph analysis via Ontoly CLI and MCP. Use when: (1) Codebase architecture, dependency, route, service, module, configuration, or impact questions need graph evidence, (2) A repository should be analyzed before source search, (3) You need a persistent SoftwareGraph.json for validation, MCP, or agent workflows. Triggers: "build software graph", "trace route", "impact analysis", "architecture summary", "dependency graph", "what uses this", "Ontoly".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use whenever the user wants to find, shortlist, vet, or enrich US marketing agencies — including branding, content marketing, PPC/paid media, social media, email marketing, performance/demand-gen, video production, and full-service digital agencies. Triggers on requests like "shortlist three B2B branding agencies in California", "find a PPC shop with ecommerce experience", "we need a content marketing partner for a SaaS launch", or "pull contact info for these 12 agency domains", even when the need is described indirectly. Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings, and third-party listings. Skip SEO-only asks (use find-seo-agency), web/software-development asks (use find-web-developer or find-software-developer), recruiting an in-house marketing hire, "write me a marketing plan" do-the-work asks, non-US firms, individual freelancers, marketing-software-product recommendations, and consumer/personal-brand asks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.