'software' 검색 결과

Helps older OpenRig instructions that reference software-for-agents lead to its maintained successor, agent-operated-software. This temporary compatibility redirect identifies where to find the current architecture and operating guidance.

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

• Following older OpenRig instructions
• Finding guidance under the successor skill name
• Checking the compatibility redirect's retirement schedule

Reconstructed reference notes on US FDA medical-device software regulation, built from seven public-domain FDA sources (the QMSR final rule 89 FR 7496, FDA device software guidance documents, and the eSTAR program page; pinned 2026-10-12). Use for regulatory pathways and premarket submissions (510(k), De Novo, PMA, eSTAR), premarket software documentation levels (Basic or Enhanced), software validation and Computer Software Assurance, the Quality Management System Regulation (QMSR, 21 CFR 820), medical-device cybersecurity (secure product development, SBOMs, FD&C Act section 524B, labelling), clinical decision support boundaries, off-the-shelf software, MDDS and other software-function scope questions, and the 510(k) software-change trigger. SCOPE LIMITS: US FDA device regulation only; no EU MDR or UKCA content (see `med-device-eu`); no ISO 13485, ISO 14971, or IEC 62304 text, which are named and summarized only as FDA obligations; no drug, biologic, or combination-product rules; reflects the pinned source dates, not later FDA actions; synthesized reference notes, not legal advice and not a substitute for the guidance documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

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

Analyze a software bill of materials, an inventory of software components, against known vulnerability records. Trace indirect dependencies, assess risk, and produce reports that help teams prioritize fixes and review supplier software.

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

• Assessing vulnerabilities in vendor-provided software inventories
• Checking whether a newly disclosed CVE affects deployed software
• Adding SBOM vulnerability checks to CI/CD

Foundational software design principles applied specifically to robotics module development. Use this skill when designing robot software modules, structuring codebases, making architecture decisions, reviewing robotics code, or building reusable robotics libraries. Trigger whenever the user mentions SOLID principles for robots, modular robotics software, clean architecture for robots, dependency injection in robotics, interface design for hardware, real-time design constraints, error handling strategies for robots, configuration management, separation of concerns in perception-planning- control, composability of robot behaviors, or any discussion of software craftsmanship in a robotics context. Also trigger for code reviews of robotics code, refactoring robot software, or designing APIs for robotics libraries.

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

Use whenever the user wants to find, shortlist, vet, or enrich US software development firms — custom software, web development, mobile app development, backend/API development, DevOps/cloud, system integration, and hosting. Triggers on "find a software dev shop in Austin", "shortlist three custom-software firms with healthcare experience", "we need a mobile app developer for our iOS launch", or "pull contact info for these 10 dev shop domains", even when described indirectly (build a tool, ship a feature, technical partner). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer to find-web-developer for strictly website/landing-page projects. Defer AI/ML, ML pipelines, model building, and data-engineering asks — those are a sibling industry, not software development. Skip in-house engineer hires, code-writing/debugging tasks, cloud-product comparisons, hardware/civil engineering, non-US firms, individual freelancers.

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

Reconstructed reference notes on US NRC software assurance guidance for digital computer software in nuclear power plant safety systems, built from seven public-domain sources (Regulatory Guide 1.168 Revision 2, July 2013; Regulatory Guides 1.169, 1.170, 1.171, 1.172, and 1.173 Revision 1, July 2013; NUREG-0800 Branch Technical Position 7-14 Revision 6, August 2016; pinned 2026-10-12). Use for software life cycle process questions, software requirements specifications, software configuration management plans, verification and validation with reviews and audits, test documentation and unit testing, and what NRC staff examine in a BTP 7-14 software review of plans, implementation, and design outputs. SCOPE LIMITS: NRC Regulatory Guides and the BTP 7-14 staff review position only; the endorsed IEEE standards (IEEE Std 603-1991, 7-4.3.2-2003, 828-2005, 829-2008, 830-1998, 1008-1987, 1012-2004, 1028-2008, 1074-2006), IEC 60880, IEC 61513, IEC 62138, and IAEA guides are cited by designation and edition only, with no standard text; RG 1.152 Rev 4, BTP 7-18, BTP 7-19, other SRP Chapter 7 sections, and NUREG/CR contractor reports are outside the pack; reflects the pinned 2013 and 2016 editions, not later agency actions; synthesized reference notes, not legal or licensing advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. § 105).

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

Reconstructed reference notes on US FAA approval guidance for airborne software and airborne electronic hardware, built from four public-domain sources (FAA Order 8110.49A, AC 20-115D, AC 20-152A, AC 00-69; documents dated 2017-07-21 to 2022-10-07, pinned 2026-10-12). Use for how FAA certification staff plan and conduct software reviews (certification liaison, desk versus on-site review, review planning agreements), how the level of FAA involvement (LOI) is picked and scored with the Appendix A worksheets, how software conformity inspection works (software part and installation conformity, ASE and ASI tasks, Form 8120-10), what AC 20-115D recognizes and how DO-178B processes and tool qualification transition to DO-178C/DO-330 (supplements, FLS, UMS, legacy software changes), and what AC 20-152A adds for airborne electronic hardware (simple versus complex custom devices, robustness and HDL code coverage, tool assessment, previously developed hardware, COTS IP, COTS devices, circuit board assemblies), and what AC 00-69 adds as best practices for change impact analysis, data and control coupling, and design-level error handling (best practices, not guidance and not a means of compliance). SCOPE LIMITS: FAA guidance only, and guidance is not regulation (ACs are acceptable means, not the only means); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, supplement, or SAE ARP text, which are copyrighted and named only (see the avionics-signpost pack); no AC 00-72 (named, not packed); no DO-178C software-level objective tables; no EASA AMC 20-115D or AMC 20-152A content (use easa-rules); reflects the pinned source dates, not later FAA actions; synthesized reference notes, not legal advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

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

Deploy a Software-Defined Perimeter that connects verified users to authorized applications. Configure single-packet authorization, mutual certificate authentication, access policies, and monitoring, then test whether unauthorized connections and access between applications are blocked.

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

• Building zero trust access to internal applications
• Hiding services from unauthenticated network scans
• Testing certificate authentication and access restrictions

Investigate malicious software delivered through trusted updates or dependencies. Compare suspect files with legitimate versions, examine signing anomalies and injected code, and organize evidence to assess the infection path and downstream impact.

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

• Comparing suspicious updates with legitimate versions
• Investigating software signatures and injected code
• Tracing infection through build artifacts

Organize software project documents from proposals through decisions, implementation specs, and incident reviews. Defines document status changes, links between records, and checks that help teams maintain related guides and preserve decision history.

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

• Organizing a software project's documentation
• Tracking proposal and decision statuses
• Linking incident reviews to related guides

Knowledge base from NASA NPR 7150.2D — NASA Software Engineering Requirements. Use for NASA's Agency-wide software-engineering requirements: the software classification scheme (Classes A–F), the Requirements Mapping Matrix and class-driven applicability, tailoring and Technical Authority governance, the SWE-### 'shall' requirements across software management (Ch 3) and the engineering life cycle (Ch 4), the supporting disciplines (configuration management, risk, peer reviews/inspections, measurement, non-conformance — Ch 5), safety-critical and cybersecurity requirements, IV&V applicability, traceability, and the Appendix A definitions. Does not cover detailed software-assurance/safety procedures (see NASA-STD-8739.8), implementation how-to and document content (see NASA-HDBK-2203), the systems-engineering process framework (see NPR 7123.1), or program/project management (see NPR 7120.5).

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

Review a repository’s architecture using Ontoly Software Graph, a map of code relationships. Explain module boundaries, package structure, dependencies, and architectural risks, with graph evidence and a stated confidence level.

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

• Understanding a repository’s overall architecture
• Reviewing module boundaries and package structure
• Investigating dependency cycles and architectural risks

Assess software dependencies, build pipelines, and container images for security risks. Create a software component inventory, check vulnerabilities and license conflicts, verify artifact signatures, and prioritize fixes based on whether vulnerable code can actually be reached.

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

• Creating and auditing a software component inventory
• Prioritizing dependency vulnerabilities by actual exposure
• Auditing CI/CD pipelines and secret handling

Analyze Windows Registry files to uncover user activity, installed software, USB connections, and automatic startup entries. Organize these traces into investigation summaries and timelines to help examine suspicious activity and possible malware persistence.

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

• Investigating suspicious automatic startup entries
• Reconstructing user activity around an incident
• Checking USB device connection traces

Improve resumes for software engineering, technical product management, data, and DevOps roles. Organize technical skills, connect achievements to business results, and highlight projects in a format suited to applicant tracking systems, software used to process job applications, and recruiters.

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

• Organize technical skills for a target role
• Rewrite experience to show technical and business impact
• Choose projects to highlight during a career change

Understand software architecture, trace request flows, and assess the impact of code changes using Ontoly’s graph of software relationships. Answers include supporting graph evidence, confidence, and relevant limitations.

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

• Explain a repository’s architecture
• Trace requests through routes and services
• Assess dependencies before refactoring

Assess weaknesses in the software supply chain, from dependency packages to build pipelines and distributed artifacts. Covers authorized proof-of-concept testing, package confusion, container image risks, signing abuse, and defensive checks for tampering.

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

• Assess dependency confusion risks in package registry settings
• Review tampering risks in CI/CD artifacts and container images
• Plan a non-destructive proof of concept and remediation report

Choose, create, and review software diagrams that explain structure, interactions, workflows, states, or data relationships. Select suitable notation and rendering tools, then plan static exports or interactive views with readable layouts, accessible controls, and validation.

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

• Explain login interactions with a sequence diagram
• Turn a database schema into an entity relationship diagram
• Document application architecture with C4

Generate motion design advertisement video prompts for software and tech companies using Seedance 2.0 on Higgsfield. Use whenever the user wants to create a software product ad, SaaS promo, app launch video, tech demo, UI showcase, startup video, or motion graphics for a tech company. Triggers on: software ad, SaaS video, product launch, app promo, tech commercial, UI animation, motion design ad, startup video, product demo video, feature showcase, or any software/tech promotional video request. Use even for "make a video for my app" or "promo for our platform.

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

Generate SaaS product launch and software demo video prompts for Seedance 2.0 on Higgsfield. Use whenever the user wants a product launch video, app demo, software walkthrough, feature showcase, startup promo, tech product reveal, or any SaaS/software marketing video. Triggers on SaaS, app, software, product launch, demo, feature, startup, tech, UI, dashboard, landing page video.

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

软件架构 (含 应用架构 / 系统架构 / 分布式 后端架构 / 前后端 数据流 与 数据模型 设计 / API 边界 / 可扩展性 / 演进式架构 — 不含 硬件架构 / 纯企业架构 / 纯 DevOps / 纯安全架构) (software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).) Master OS — automated mastery of software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「软件架构」「系统设计」「system design」「应用架构」「service design」

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

Use whenever the user wants to find, shortlist, vet, or enrich US engineering firms — civil, structural, MEP, mechanical, electrical, geotechnical, transportation, environmental, and manufacturing. **For real-world engineering (buildings, infrastructure, manufacturing) — NOT software engineering.** Triggers on "find civil engineering firms in Florida for transportation", "shortlist three structural engineering firms with high-rise experience", "MEP consultancy for a hospital project", or "pull contact info for these 12 engineering firm domains", even when described indirectly (PE-stamped drawings, building-permit review). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer software-dev / "engineering team" / SaaS-architecture asks to find-software-developer. Skip in-house engineering-manager hires, DIY questions, software-product comparisons (Revit, AutoCAD), non-US firms, individual freelancers.

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

Reviews one employee software request (tool, purpose, users, data handled, cost, urgency) against the approved-tools list and the policies the user provides and returns a draft review for the reviewer: match state on the list with the row quoted, approved tools the list itself describes as covering the same need, policy clauses that bear on the request with quoted text, questions for the requester and the reviewer, and one suggested decision with its basis. Never approves, procures, installs or adds a tool to the list. Use when the user asks to "review this software request", "is this tool on the approved list", "check this request against our software policy", "do we already have something approved that does this" or "prepare the decision note for this tool request". Do not use for a full vendor security assessment, use vendor-risk-screening-brief instead; for sorting mixed requests, use request-intake-triage. Drafts for human review; never approves, authorises or signs off.

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

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.

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