'contract' 검색 결과

Используйте, когда нужно создать информационную базу через канонический runtime contract проекта.

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

Используйте, когда нужно выгрузить конфигурацию или расширение в исходники через канонический runtime contract проекта.

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

OrgX operations execution contract for OpenClaw. Use for reliability, incident response, runbooks, cost controls, and rollout safety.

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

Tactical negotiation framework based on Chris Voss's "Never Split the Difference." Use when preparing for negotiations, during live negotiation scenarios, analyzing counterpart behavior, crafting responses to difficult conversations, handling objections, salary/contract negotiations, or when asked about negotiation techniques like mirroring, labeling, calibrated questions, or the Ackerman method.

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

Pyramid multi-agent orchestration for OpenClaw: routes objectives from a CEO agent down through departments, services and employees via sessions_send / sessions_spawn, collects and merges results, enforces handoff contracts, and writes the final deliverable back to the originating session.

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

Understand blockchain technology, interact with smart contracts, and evaluate when distributed ledgers solve real problems.

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

中国法律法规查询工具。Use when user needs to search Chinese laws, regulations, judicial interpretations. Supports criminal law, civil law, labor law, contract law, intellectual property law. 中国法律、法规查询、法律条文。

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

中国法律场景解析工具。Use when user needs to analyze legal scenarios, understand legal implications, or get legal guidance for specific situations. Supports contract disputes, labor disputes, property disputes, family law cases. 中国法律分析、法律场景解析、法律建议。

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

Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.

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

Interact with Erc20 smart contract via read/write functions

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

Public-records OSINT investigation framework — SEC EDGAR filings, USAspending contracts, Senate lobbying, OFAC sanctions, ICIJ offshore leaks, NYC property records (ACRIS), OpenCorporates registries, CourtListener court records, Wayback Machine archives, Wikipedia + Wikidata, GDELT news monitoring. Entity resolution across sources, cross-link analysis, timing correlation, evidence chains. Python stdlib only.

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

Generate multiple radically different interface designs before implementation. Use when designing an API, module boundary, command surface, data contract, or when the user says "design it twice".

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

Use when a new feature needs a table, column or capability — evolving the schema so the new thing joins the permission, audit and RLS contract instead of sitting outside it. Covers the DDL/DML split, the resource/capability wiring, and the self-verifying migration.

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

Generate UI design contract (UI-SPEC.md) for frontend phases

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

Generate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategy

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

Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.

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

Reference for producing Adobe Document Authoring (DA, da.live) and Edge Delivery Services (EDS, aka aem.live/Helix) compatible content. Use whenever generating HTML for DA upload, uploading media binaries to DA, publishing to aem.live, or driving the DA admin API (auth, source PUT, preview/publish). Covers block HTML format (canonical div-class form and accepted table alternate), section structure, page/section metadata, icons, links, images, default content, document skeleton constraints, block cell content normalization, the DA Source API contract, IMS auth, media storage, supported formats, Media Bus vs Content Bus delivery, and silent-failure rules that corrupt content.

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

Reference for the Adobe AEM CLI (@adobe/aem-cli, formerly the helix-cli npm package; commands `aem up`, `aem import`, `aem content`) — installation, the local Edge Delivery dev server, .env / AEM_* configuration, HTTPS/TLS, proxy & certificate trust, content sync with da.live, and troubleshooting. Use when installing, running, or configuring the aem/hlx CLI, when `aem up` fails (port conflicts, cert errors, proxy 404s, pipeline vs. local-file confusion), or when migrating from the old helix-cli package. Do NOT use for da.live content-format rules or the DA Source API contract (use da-content); do NOT use for writing EDS block code (use content-driven-development).

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

Create or materially revise a durable specification when the user explicitly requests a spec/new feature contract or a named ambiguity requires formal DEFINE; do not trigger for ordinary bounded edits, implementation, task breakdown alone, review, or documentation of already-settled behavior.

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

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

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

Build a backend service or an end-to-end frontend/backend integration when service/API/data boundaries are the primary deliverable; do not trigger for pure UI, contract design only, security review, test workflow, or every feature touching both folders.

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

Code-review quality gate and test-enhancement rubric. Use when ROSE needs sharper review output contracts, severity and risk prioritization, evidence anchors, negative review cases, fixture or golden-output drift guidance, or a Chinese review report profile; do not use as a duplicate code-review agent or final PASS authority.

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

Create or update source-grounded documentation when the user explicitly asks for docs/ADR/onboarding material, a public contract change requires docs, or an accepted hard-to-reverse decision meets the ADR gate; do not trigger for every feature, architecture discussion, implementation, review, or SHIP request.

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

Produces comprehensive system architecture plans for features and products including component breakdown, data flow diagrams, system boundaries, API contracts, and scaling considerations. Use for "system design", "architecture planning", "feature design", or "technical specs".

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