「got」の検索結果

Drafts a Build-Out Allowance Agreement as a commercial lease addendum governing landlord-provided TI allowance terms. Use when structuring TI allowance financing, negotiating landlord work letters, or documenting tenant improvement funds at lease execution.

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

[user] Business Legal Counsel / CLO level contract drafting, review, and legal risk assessment. Handles domestic Chinese contracts (中文), cross-border contracts, and offshore international contracts in Chinese and English. Jurisdictions: PRC law (Civil Code, Company Law, Anti-Unfair Competition Law), US law (UCC, common law), Hong Kong law (common law, HK ordinances). Combines relevant laws, regulations, and litigation case precedents in contract analysis. Generates Word (.docx) files with track changes and persuasive margin comments for contract review markup. Use when user mentions contracts, legal review, contract drafting, legal risk assessment, NDA, agreement, 合同, 法律, 审核, 起草, 合同审查, 法务, legal negotiation, due diligence, 尽职调查, 风险评估, 条款谈判, 反不正当竞争, or any contract-related task.

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

Produces structured asset and liability summaries from financial documents for legal proceedings. Extracts valuations, ownership classifications, and encumbrances, then outputs net-worth overview, categorized schedules, disputed items, and documentation gaps. Use when preparing financial summaries for divorce/dissolution, estate planning, bankruptcy, business valuation, or settlement negotiations. Trigger on: net worth summary, marital estate, balance sheet, asset schedule, liability schedule, community/separate property.

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

Negotiates a file-based sprint contract between generator and evaluator before code is written: turns a spec into testable acceptance criteria with rubric tie-ins.

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

Create new skills with proper structure, compliance checks, and registration. Use when asked to create a skill, build a new skill, or scaffold a skill template. Enforces mk: prefix, sub-agents.md structure, and context engineering principles.

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

Use when writing tests, running validation scripts, or (in TDD mode) enforcing red-green-refactor cycle. Activates during Phase 2 (Test) and Phase 3 (Build). NOT for coverage gap mapping (see mk:nyquist); NOT for sprint contract negotiation (see mk:sprint-contract).

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

Save a project fact, decision or gotcha so your next session already knows it.

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

Framework for coordinating meaning across autonomous agents that use different conceptual models, vocabularies, and knowledge representations. Treats ontologies as first-class negotiable resources rather than hardcoded implementation details.

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

Choose multi-agent architectures using environment-first analysis, coordination pressure, commitment tuning, and knowledge levels. Use for autonomy design, protocol choice, and coordination failures. NOT for single-agent planning, centralized schedulers, or prompt-only swarms.

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

Maps between gene identifier systems (Ensembl, Entrez, HGNC symbol, UniProt, RefSeq, MANE) using AnnotationDbi, biomaRt, mygene, pyensembl, and Ensembl REST. Encodes Ensembl version stripping with GENCODE _PAR_Y preservation, the Ziemann 2016 Excel autocorrect debacle and Bruford 2020 HGNC renames (SEPT*->SEPTIN*, MARCH*->MARCHF*, MARC*->MTARC*, DEC1->DELEC1), OCT4/POU5F1 alias resolution, biomaRt archive endpoints for release pinning, the `filters` (plural) gotcha, MANE Select for clinical reporting, cross-species orthology via Ensembl Compara / OMA / OrthoDB, and tx2gene construction for tximport. Use when converting gene IDs across systems, handling renamed symbols, building tx2gene, pinning to a specific Ensembl release for reproducibility, or mapping cross-species orthologs.

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

Build publication-quality figures with matplotlib using the object-oriented Figure/Axes API, constrained_layout, rcParams customization, TrueType (Type-42) font embedding for journal submission, and CVD-safe palettes. Covers seaborn integration, common chart types, axis formatting, and the small gotchas that distinguish reproducible matplotlib from notebook scratch. Use when producing publication figures in Python — RNA-seq scatter, single-cell embeddings, generic biological plotting.

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

Ensure every factual claim in a response is backed by verifiable evidence from the codebase, documentation, or external sources. Use when preparing technical documentation, code reviews, or any output where accuracy is non-negotiable.

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

Keep a small requested change focused when optional refactors, architectural redesign, or unrelated cleanup threaten to expand its scope.

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

Agents with competing priorities reach consensus through structured trade-offs.

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

Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.

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

Use between coding-agent runs (Codex, Claude Code, Cursor, Aider, etc.) to stop the project from drifting, overbuilding, or accumulating dead weight. Forces a read-only audit that classifies every active item as KEEP / DELAY / REMOVE and ends with a single, unambiguous next action. Trigger on "audit before continuing", "what should I do next", "this project got too big", "between runs", "trim scope", "stop adding stuff", or any signal that the project feels noisy and the next step is unclear. Do NOT load for trivial one-line fixes, when the next action is already obvious, or when you're mid-run and just need to keep going.

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

Run on an existing project to decide KEEP / MERGE / ARCHIVE — never limbo. Forces a call on tools that already exist and may have stopped earning their keep. Trigger on "is this still worth keeping", "audit this repo", "tech-debt cleanup", "sweep the folder", "what's dead here", or any signal that something hasn't been touched in months. Judged from both the agent lens (still legible, still drivable, still safe) and the human lens (do I still reach for it, does it nag). Includes a non-negotiable footgun check for stale pipelines that can overwrite live data. Outputs a backed AUDIT.md and a one-line verdict note in the project root docs. Do NOT load for greenfield projects (use new-project-gate), one-off bug fixes, or when the answer is already obvious.

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

How to MEASURE this repo instead of eyeballing it — interpret the loop-station context-budget trend (history.jsonl, thresholds, the tokenizer-switch gotcha), read a session trace, use the eval ledger (cost-per-success), and pick the right evidence tool (app-shots, smoke-deployed, db-counts, --check modes). Use when asked "is the harness bloating", "how big is CLAUDE.md really", "did this agent run actually succeed", "prove this works", "what evidence do we have", or when tempted to declare a capability (browser, tool) unavailable. For RUNNING the loop-station scripts, defer to the loop-station skill — this skill is interpretation + the wider evidence toolkit.

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

The migration step and the package-owned-table exception — NOT the normal collection flow. For app collections use the crouton CLI/skill (schema JSON → `crouton config`); reach here when you then need to generate/apply the Drizzle migration and hit the schema.mjs-only-after-build gotcha ("No schema files found"), or when adding a package-owned infra table (the crouton-flow pattern) that does NOT go through `crouton config`.

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

Swap the external provider/library that backs a crouton package (e.g. the map renderer, geocoder, editor engine, storage SDK) while keeping the package's public API stable so consuming apps need no changes. Use when asked to "change the X provider", "replace library Y in package Z", "switch from <vendor A> to <vendor B>" inside packages/. Encodes the keep-the-API-stable playbook + the gotchas (dist .d.ts over docs, generator templates, fixtures, dup-dep type clashes).

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

Generate onboarding documentation for a codebase — architecture overview, key files, local setup, and common gotchas. Use this skill whenever someone asks to onboard onto a codebase, create onboarding docs, generate a codebase overview, explain a project's architecture to newcomers, or asks "how does this codebase work". Also trigger when users say things like "document this repo for new devs", "write a getting started guide", or "help me understand this project".

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

Comprehensive Stata reference for writing correct .do files. Covers syntax, options, gotchas, and idiomatic patterns. Use this skill whenever the user asks you to write, debug, or explain Stata code. Generates ready-to-run .do files for the user to execute manually.

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

Operating manual for Telegram over its MCP connector and roughly 115 tools: how to find a chat by title, the tool inventory grouped by job, resolving chat ids, auto-transcribing voice notes, and the connector gotchas (pinned-first ordering, big-page crashes, reload after reconnect, untrusted fields, always passing an explicit account). Load before any non-trivial Telegram work.

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

- Enumerate an organisation's subdomains and sibling domains from Certificate Transparency logs and passive DNS, without sending traffic to the target. Use when looking for staging, dev, admin or VPN hosts, mapping the full hostname footprint of a domain, or spotting infrastructure a company forgot it had

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