「standard」の検索結果

Map construction data to standard ontologies. Create semantic mappings between different data schemas

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

Classify BIM elements using AI and standard classification systems. Map elements to UniFormat, MasterFormat, OmniClass, and CWICR codes.

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

Generate comprehensive BIM model validation reports. Check data quality, completeness, and compliance with standards.

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

Compare cost estimates across projects, versions, and scenarios. Identify variances, benchmark against standards, and generate comparison reports.

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

Analyze labor productivity from site data. Compare planned vs actual, identify trends, benchmark against industry standards.

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

Access and utilize open construction pricing databases. Match BIM elements to standardized work items, calculate costs using public unit price databases with 55,000+ work items.

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

Serverless compute for Databricks jobs, Lakeflow pipelines and Declarative Automation Bundles (DABs), with STANDARD or PERFORMANCE_OPTIMIZED and classic only where serverless cannot run the workload. Use when creating, deploying, scheduling or editing a job or pipeline, or deciding its compute. Invoke BEFORE writing a job spec. For migrating existing classic workloads, use databricks-serverless-migration.

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

Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML. Use when building standardized KPIs, revenue metrics, order analytics, or any reusable business metrics that need consistent definitions across teams and tools.

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

Create standardized UTM tracking for all campaigns. Ensure consistent naming conventions across team and generate tracking reports.

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

Argues the strongest honest case against a decision, plan, belief, hire, pricing move, strategy, or piece of work the user is leaning toward. Steelmans the other side, ranks at most three objections by consequence, runs a short pre-mortem, credits what the user got right, and ends with what would have to be true for their choice to work. Calibrated and collegial, never combative; says plainly when the position is strong. Use whenever the user says "play devil's advocate", "argue the other side", "poke holes in this", "what am I missing", "am I making a mistake", "talk me out of it", "stress-test this idea", "tell me why this is a bad idea", or asks for pushback on something they have mostly decided. Supports gentle, standard, and hard intensity. Not for interrogating requirements before a build (grill-the-brief) or staging a multi-persona debate (debate-simulator).

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

Turn a process walkthrough -- meeting transcript, screen-recording transcript, rough notes, or a folder of scattered how-to docs -- into a clean standard operating procedure: numbered steps, roles, decision points, exceptions, and a consistent template across your whole SOP library.

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

Generates full consulting proposals from a brief. Input client name, problem description, and rough scope. Outputs proposal.md with executive summary, problem statement, proposed approach, timeline, team, pricing tiers, and terms. Researches client company for personalization. Multiple pricing models. Professional formatting matching consulting standards.

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

Review contracts for concerning clauses, extract key terms, compare to standard terms, and flag unusual provisions. Use when user needs contract review, legal document analysis, or agreement evaluation.

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

Standardize Notion task updates across all modes

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

Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.

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

Standardizes release approvals with GitHub-aware checklists and deployment gates. Use before releasing to production to verify all gates pass.

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

Provides standardized pytest config, reusable fixtures, and CI integration patterns. Use when setting up or auditing a Python plugin's test infrastructure.

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

Captures and retrieves PR-review findings in memory palaces. Use after PR review to store architectural decisions, patterns, and standards for future reference.

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

Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.

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

Use when designing or auditing how an LLM or multimodal LLM is evaluated on a clinical task (report generation, VQA, text extraction). Covers reference standard, clinical-efficacy metrics beyond BLEU/ROUGE, hallucination, contamination and prompt sensitivity. Imaging models are /model-assessment.

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

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.

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

Before showing the user any substantive GTM deliverable (positioning, value prop, homepage, launch post, pricing, sales script, the brief or roadmap), stress-test it against the standard as an independent critic, because the agent that wrote it is the worst judge of whether it is good. Use as a gate right before presenting work, or when the user asks whether something is actually strong.

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

Builds new Claude Code agents with consistent structure, enforced standards, and project-aware configuration. Use when creating a new agent, when the user describes a specialised role they want delegated to, or when discussing team composition.

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

Builds new Claude Code skills with consistent structure, enforced standards, and project-aware configuration. Use when creating a new skill, when the user describes a workflow they want automated, or when the user says they want a new slash command.

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