「contracts」の検索結果

Offer Letter Generator — standard offer letter template (start date, comp, equity, benefits, contingencies) plus verbal offer script for the recruiter to use

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

商业合同法律顾问。负责供应商协议审查、NDA 分类、SaaS MSA 审查、中国合同风险扫描和条款重述、续约/取消期限审查、升级标志识别。当企业法务主理人（法衡中）调度执行合同审查任务时激活。典型问题：审查 NDA/供应商协议/SaaS MSA；该条款是否需要升级？为业务方总结合同风险。

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

Generate production-ready business documents including freelance contracts, project proposals, SOWs, NDAs, and MSAs with jurisdiction-aware clauses. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) legal frameworks. Includes contract templates, clause libraries, and DOCX conversion. Use when starting client engagements, writing proposals, drafting partnership agreements, or needing GDPR-compliant data processing addenda.

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

Analyze and red-flag contracts systematically, identifying risks, unfavorable terms, and negotiation opportunities

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

Compose, revise, validate, compare, inspect, and export original multi-track music as Standard MIDI with BeatFlow's compact, style-neutral Python DSL. Use for turning a musical brief into a deterministic Composition, testing explicit phrase/counterpoint/theme contracts, or inspecting MIDI.

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

Prepare and validate portable CAD, polyline, node-element, clump, and boundary geometry contracts for PFC 5.0 asphalt models without bundling opaque legacy executables.

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

Plan and validate PFC 5.0 asphalt fluid, pore-pressure, buoyancy, seepage, and PFC-FLAC coupling contracts while keeping version-specific commands and licensed coupling assets external.

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

"Apply contract theory to design incentive-compatible agreements under moral hazard and adverse selection. Use this skill when the user needs to structure principal-agent contracts, evaluate compensation schemes, or analyze incomplete contract problems where parties cannot specify all contingencies ex ante.".

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

Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

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

Design API and module boundaries with clear contracts, error semantics, pagination, and additive compatibility. Use before implementing REST/GraphQL endpoints, SDKs, or public module APIs.

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

Design agent tools and CLI surfaces—schemas, naming, errors, idempotency, and discoverability for LLM callers. Use when defining tools for agents, SDKs, or AI-native CLIs.

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

"Design and implement smart contracts as self-executing programmatic agreements on blockchain. Use this skill when the user needs to build automated on-chain logic, evaluate smart contract security, or design tokenized business rules — even if they say 'smart contract development', 'automated agreement', or 'on-chain logic'.".

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

Design system architecture, API contracts, and data flows. Use when translating analyzed requirements into technical design for feature implementation.

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

Design REST APIs or function contracts with clear request/response specifications, error handling patterns, authentication strategies, and comprehensive documentation.

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

Design component architecture, REST API contracts, and data models (Pydantic schemas) before implementation. Use when planning how to build a feature, defining endpoints, or modeling data. Trigger on "design the architecture", "design the API", "data model", "how should I structure this feature".

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

Apply risk-based test-driven development to bugs, domain logic, state transitions, parsers, contracts, migrations, and behavior where a failing test sharpens the design.

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

Conduct structured legal due diligence for M&A, joint ventures, or investment transactions. Cover all 9 workstreams — Corporate, Contracts, IP, Litigation, Regulatory, Employment, Tax, Environmental, and Data Privacy. Produce a risk matrix with deal-breaker flags and closing conditions. Use when evaluating a target or counterparty.

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

Review commercial contracts, NDAs, MSAs, SOWs, and vendor agreements for obligation clarity, risk allocation, termination, data handling, and negotiation red flags. Use when a user needs a structured contract summary, red flag list, fallback positions, or clause-by-clause review. Do not use as jurisdiction-specific legal advice, litigation strategy, or final legal sign-off.

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

Smart contract vulnerability playbook. Use when auditing Solidity/EVM contracts for reentrancy, integer overflow, access control, delegatecall, flash loan, signature replay, and MEV-related attack patterns.

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

Packaging React components as a consumable library — style delivery contracts, sideEffects, cascade layers, "use client" preservation, peer dependency ranges, server-safe vs client entries

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

Backend specification planning frameworks. Use when a spec touches API endpoints, database schema, middleware, or auth. Covers endpoint contracts with request/response shapes, error catalogs, auth per endpoint, schema design with constraints and indexes, migration strategy, and middleware pipeline ordering.

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

AI specification planning frameworks. Use when a spec touches model calls, prompts, retrieval, tool calling, agentic loops, or evals. Covers approach selection, model and provider choice, structured output contracts, loop guards, budgets, failure modes, and eval design.

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

CLI specification planning frameworks. Use when a spec touches a command surface, an interactive flow, config precedence, exit codes, or output modes. Covers flag contracts, prompt flow design, precedence tables, exit-code taxonomy, TTY/piped/JSON output, error text, signals, and cross-platform concerns.

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

Frontend specification planning frameworks. Use when a spec touches UI components, forms, client state, or user-facing flows. Covers UI-state completeness (loading, error, empty, success), component boundaries, form validation contracts, state ownership, and measurable UI success criteria.

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