'standard' 검색 결과

Triages an incoming non-disclosure agreement against the organisation's written standard NDA positions and returns a DRAFT triage pack: a clause-by-clause deviations table with a severity band, a suggested response per clause quoted from the positions document, open questions and a governing-law flag, all for counsel to decide. Never gives legal advice or an acceptability call. Use when the user asks to "triage this NDA against our standard positions", "screen this confidentiality agreement before it goes to legal", "red-flag this mutual NDA", "first-pass the counterparty's NDA" or "is this NDA standard or does it need counsel". Do not use for a full review of an MSA, SOW, licence or any whole contract, use contract-review-pack instead; for one clause lined up across several documents, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.

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

Turns the text of a regulatory change (new regulation, amendment, rule, guidance or standard revision) into a DRAFT impact note: what changed against the prior text where supplied, who is affected as the text scopes it, an obligations table with dates and owners to confirm, and open interpretation questions for legal. States only what the text says; the rest is UNKNOWN. Use when the user asks to "brief legal on this new regulation", "list what we must do by when under this amendment", "compare the new standard with the version it replaces", "turn this directive into an obligations table" or "what does this rule mean for us". Do not use for assessing existing controls against a requirement set, use controls-gap-pack instead; for gapping a policy against a standard, use policy-gap-review. Drafts for human review; never approves, authorises or signs off.

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

標準原価差異分析スキル。標準原価（予定原価）と実際原価の差異を価格差異・数量差異に分解し、 材料費・労務費・製造間接費のカテゴリ別に集計・分析する。差異の有利/不利判定、 責任部門の特定、根本原因の仮説提示を行う。CSVデータのアップロードによる自動分析に対応。 Use when: 製造原価の差異分析を行いたいとき。標準原価計算制度の運用、 月次原価差異レポート作成、原価低減活動の効果測定に使用。 Triggers: "標準原価", "原価差異", "価格差異", "数量差異", "standard cost", "cost variance", "price variance", "quantity variance", "予定原価", "操業度差異", "原価管理"

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

Knowledge base from NASA-STD-8729.1A — NASA's R&M (Reliability and Maintainability) standard covering spaceflight and support systems (Revision A, 2017-06-13). Use for NASA's objectives-driven R&M framework — the R&M objectives hierarchy (one Top Objective decomposed into four sub-objectives, paired with tailorable strategies), how R&M requirements are established inside the SMA Plan required by NPR 7120.5, the SMA Technical Authority concurrence/independent-evaluation governance, milestone vs. readiness review gates, the reliability/maintainability/availability vocabulary (Ai vs. Ao, the failure causal chain, risk as a triplet), and the R&M Evidentiary Methods catalogue (FMEA/FMECA, FTA, RBDA, RCM, LORA, plus the space-environment and parts-pedigree analyses). Scoped to NASA spaceflight and support systems and to assurance planning: it is an objectives-and-strategies standard, so it deliberately does NOT prescribe step-by-step analysis procedures (those live in the referenced NASA Preferred Reliability Practices) and is thin on facility R&M, detailed math/derivations, and non-NASA or commercial life cycles.

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

Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire, standardizing campaign tracking, fixing broken lead routing, cleaning up HubSpot or CRM data, building QA checklists for campaign launches, or creating incident response procedures for marketing system failures. Also use when asked to "fix our UTM mess," "standardize campaign naming," "build a QA checklist," "audit our marketing ops," or "create an ops runbook." Designed for B2B SaaS marketing teams running HubSpot with multi-geo, multi-segment operations.

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

Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.

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

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

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

Enforces consistent structured logging with request correlation IDs, standardized log schema, middleware integration, and best practices. Use for "structured logging", "log standardization", "request tracing", or "log correlation".

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

Spring Boot와 Quarkus의 Java 코드를 명명, 불변 데이터, 예외 처리, 프로젝트 구조와 테스트 규약에 따라 작성하고 검토합니다. 빌드 파일로 프레임워크를 판별합니다.

• Java 코드의 규약 준수 검토
• Optional과 streams 사용 확인
• 패키지와 프로젝트 구조 정리

C++ 코드 구현·검토·리팩터링에서 타입 사용, 메모리 관리, 예외 처리와 동시성을 점검합니다. 표준 지침에 따라 안전성과 코딩 방식의 일관성을 정리합니다.

• 모던 C++ 코드 작성
• 메모리 소유권과 자원 해제 검토
• 기존 C++ 코드 리팩터링

공통 기준으로 코드의 명명, 가독성, 원본 데이터를 바꾸지 않는 갱신 방식과 오류 처리를 검토합니다. 중복과 복잡한 구조를 찾아 유지보수하기 쉽게 정리합니다.

• 기존 코드의 명명과 가독성 검토
• 긴 함수와 깊은 조건 분기 정리
• 새 모듈의 코딩 규칙 통일

브라우저, API, 명령줄 도구와 백그라운드 처리의 오류를 조사하고 수정·검증합니다. 세 단계의 점검 범위를 선택하고 수정 근거와 출시 판단 자료를 받습니다.

• 웹사이트 오류 수정
• API와 CLI 동작 확인
• 작업과 webhook 처리 확인

화면 애니메이션 코드를 속도, 자연스러움, 중단 대응, 렌더링 성능, 접근성 관점에서 검토합니다. 수정안과 이유를 제시하고 승인 여부를 판단합니다.

• 드롭다운과 툴팁의 움직임을 점검합니다
• 연속 조작에 대한 반응을 확인합니다
• 렌더링 성능을 해치는 애니메이션을 찾습니다

글로 설명한 내용을 손으로 그린 듯한 Excalidraw 도표로 만듭니다. 용도에 따라 애니메이션 SVG, 온라인 편집 링크, PNG 내보내기를 사용할 수 있습니다.

• 글로 설명한 내용을 손그림 도표로 만듭니다
• 도표를 온라인에서 편집합니다
• 도표를 PNG 이미지로 내보냅니다

Coordinate changes across multiple GitHub repositories with teams of AI agents. Align package versions, synchronize documentation, standardize project structures, and organize integration tests and pull requests for updates that affect several projects.

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

• Aligning dependency versions across repositories
• Synchronizing shared documentation
• Standardizing repository structures and CI workflows

Look up recorded tariffs for one product traded between two countries using its six-digit HS product code. Compare standard and partner-specific preferential rates, and check the data year and basis used to report the applied rate.

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

• Looking up a product's tariff between two countries
• Comparing standard and preferential tariff rates
• Checking whether a trade agreement lowers the recorded rate

Keep coding changes small by questioning unnecessary work and reusing existing code, standard libraries, and native platform features. Apply this approach to implementation, bug fixes, reviews, and dependency choices while preserving validation, security, and accessibility.

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

• Reduce unnecessary code and dependencies
• Fix shared root causes of bugs
• Review code for excessive abstraction

Check a codebase for known dependency vulnerabilities, hard-coded secrets, and risky code patterns using Ruflo security tools. Choose a scan depth, inspect matching lines, and report verified concerns with a clear account of what was checked.

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

• Checking pull requests for security regressions
• Inspecting authentication and input-handling code for risky patterns
• Running security checks before production deployment

Create a standard folder layout for a DDD bounded context, a module organized around one business area. Generate TypeScript export files, keep infrastructure outside the public exports, and record the context in a domain model graph.

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

• Starting a module for a new business area
• Splitting a monolith into bounded contexts
• Listing existing contexts

Audit URL capitalization and help standardize paths to lowercase. Review routes, internal links, and sitemaps, then check that uppercase variants permanently redirect to the lowercase address to reduce duplicate page URLs.

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

• Auditing uppercase letters in URL paths
• Planning lowercase URL handling for a new site
• Verifying 301 redirects for mixed-case URLs

Review JavaScript loops and replace suitable ones with standard array and object methods. Make transformations, filtering, and aggregation easier to understand, with practical explanations and browser checks to confirm that changes preserve the intended behavior.

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

• Refactoring manual loops into array methods
• Clarifying data transformation, filtering, and aggregation
• Reviewing object transformations and deep copying

Audit a business website for inconsistent names, addresses, and phone numbers. Compare visible page content with structured data, then standardize spelling and formatting to support accurate business information in local search.

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

• Check business details across a local website
• Standardize address and phone number formats
• Compare structured data with visible contact details

Review ARIA roles, labels that tell assistive technology what page elements do, and correct invalid values. Prefer standard HTML controls where suitable, then check keyboard behavior, focus movement, and screen reader output to verify the changes.

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

• Finding invalid or misspelled ARIA role values
• Replacing custom widgets with standard HTML controls
• Reviewing accessibility in shared UI components

Check the current date and time in Pakistan Standard Time, which is UTC+5. The skill uses a bash command and presents a concise line containing the date, a 24-hour time, and the PKT label.

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

• Checking the current time in Pakistan
• Getting the date and time in PKT
• Displaying Pakistan time in a concise 24-hour format