「nda」の検索結果

Capture meeting notes with clear structure: attendees, agenda, decisions, action items with owners and deadlines. Ensure accountability and alignment post-meeting.

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

Context is the complete state available to a language model at inference time. It includes everything the model can attend to when generating responses: system instructions, tool definitions, retrieved documents, message history, and tool outputs.

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

When agent sessions generate millions of tokens of conversation history, compression becomes mandatory. The naive approach is aggressive compression to minimize tokens per request.

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

Use Angular CLI and development tools effectively in Angular v20+ projects. Use for project setup, code generation, building, testing, and configuration. Triggers on creating new projects, generating components/services/modules, configuring builds, running tests, or optimizing production builds. Don't use for Nx workspace commands, custom Webpack configurations, or non-Angular CLI build systems like Vite standalone or esbuild direct usage.

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

Instrument applications with Azure Application Insights and OpenTelemetry for end-to-end observability. Use this skill when users ask about telemetry, tracing, metrics, logging, or monitoring setup. Covers SDK setup, correlation, sampling, dashboards, and alerts per OpenTelemetry standards.

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

Design and operate Azure Storage services for durability, performance, and secure access. Use this skill when users ask about Blob, Files, Queues, Tables, or Data Lake storage patterns. Covers redundancy, tiering, access models, lifecycle policies, and compliance.

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

Create modern Angular standalone components following v20+ best practices. Use for building UI components with signal-based inputs/outputs, OnPush change detection, host bindings, content projection, and lifecycle hooks. Triggers on component creation, refactoring class-based inputs to signals, adding host bindings, or implementing accessible interactive components.

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

Apply OpenAI's brand colors, typography, and visual identity standards to artifacts. Ensure design consistency with OpenAI branding for presentations, documents, and UI components.

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

Publication-quality statistical visualization with mandatory best practices. Use when creating plots, charts, figures, or any data visualization. Enforces accessibility, uncertainty display, proper labeling, and statistical accuracy.

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

Core statistical methodology and pedagogical approach for all Inquiro analyses. Always loaded to maintain teaching quality and reproducibility standards.

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

Auto-activate for uv build, hatch build, PyApp, PYAPP_*, wheel assets, GitHub release matrices, cargo-zigbuild, or python-build-standalone. Not for runtime deployment.

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

Auto-activate for Litestar, Controller, Router, @get/@post, FromPath, MsgspecDTO, OpenAPIConfig, Provide, FromDishka, Guard, ASGIMiddleware, HTTPException, ChannelsPlugin, or WebSocket. Not for standalone libs.

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

PRD 到高保真 UI 交付对齐 / 桌面工作台 UI mockup：当用户已有 PRD、UI 规范、真实前端项目路径、截图或页面状态清单， 需要先从 PRD 提炼 UI 结构、状态模型和 ASCII 布局，再进入高保真 mockup、项目原生 preview 或开发交付 handoff 时使用。 优先输出项目原生 preview route/component；只有早期概念确认或无法接入真实项目时才输出 standalone HTML。 必须包含结构阶段产物、screen contract、component map、implementation notes、截图/验证结果和 HTML/preview 的迁移边界。

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

PRD 架构师 / 需求文档起草：当用户要把一个产品想法、需求草稿、脑暴结果或功能说明整理成 PRD 时使用。 可用中文唤起：“帮我写 PRD”“帮我选 PRD 模板”“把这个需求整理成 PRD”“判断该用轻量 PRD 还是标准 PRD” “补一张可编辑 Draw.io 核心流程图”“PRD 里加架构图”。 会在 PRD-lite、PRD-standard、PRD-ai-native 中选择一个模板资产按需加载，并在需要时加载 mockup handoff、 Draw.io 图示或开发 handoff 附录；页面型 PRD 默认联动生成项目 UI 对齐的 HTML、关键截图和正文证据。 不用于直接编码、单纯画 UI，或评审一份已经写好的 PRD。

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

Project documentation structure — standard proj-[name]/ layout with ADRs, stories, and operations guides. Use when: initializing docs for a new project, recording architecture decisions, or maintaining project knowledge bases.

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

Prove — or honestly fail to prove — a specific technical claim: "the fix works", "it's deployed", "the service is running", "the site is done", "there are no vulnerabilities". Atomizes the claim, picks the shortest decisive signal on the evidence ladder, and returns a verdict from a fixed vocabulary (pass / partial / fail / skip) with an explicit coverage boundary. NOT code review, NOT a fix, NOT orchestration — only "what is proven, and what we merely hope". Triggers — "prove it works", "is it really done?", "are you sure?", "we deployed — is it live?", "verify that", "did we actually check?".

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

Evaluate an incoming workflow upgrade — a skill, MCP server, subagent, library, external service, prompt, or pattern — through one disciplined pipeline before adopting it. Security is a blocking gate. Records every verdict so the same thing is never evaluated twice. Use when considering a new tool from a post, repo, or recommendation. Triggers — "vet this", "should we adopt", "is this safe to install", "evaluate this skill/MCP", "what do you think of this tool".

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

Runs a team of 50 LLM personas through a 30-round structured debate to predict market direction. Uses the Canvas Agent Swarm Service — the same shared infrastructure other skills use for smaller agent teams. Output is an influence-weighted consensus direction + trade recommendation with a transparent record of every argument, research query, and cross-examination.

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

Research historical news events that moved (or are moving) an asset's price and plot them as data points directly on the chart. Click a marker in the Historic News tab to zoom the chart to that event and read the article. Useful for identifying the fundamental drivers behind price action — earnings, regulation, product launches, macro shocks, geopolitical events.

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

Master dark mode UI design with atmospheric theming, WCAG accessibility, and cross-platform best practices. Specializes in weather/sky/ocean-inspired color systems that adapt to time of day and environmental conditions. Use when the user explicitly needs dark mode design expert help. NOT for unrelated tasks.

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

Review GEODE dependency direction, composition boundaries, circular imports, and optional-dependency loading when changing package or subsystem dependencies.

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

GEODE runtime context for model selection and metadata, architecture, packaging, release, docs, CI, AgenticLoop, async runtime, and plugin boundaries.

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

Select complementary review lenses for a requested multi-perspective review or a high-risk GEODE change. Covers design, agent constraints, gateway operations, and CLI/tool behavior; not a mandatory four-agent gate for ordinary edits.

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

GEODE CHANGELOG.md management rules. Version releases, change logging, scope determination, format standards. Triggers on "changelog", "release", "version", "릴리스", "변경사항", "버전".

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