「got」の検索結果

Discipline for the seam between two SDKs (or two sides of one contract) that the same hand writes. The failure mode: "we own both sides" produces dirty contracts no foreign reviewer would accept. The exercise: pretend the other side is FFI, IPC, or a network protocol you cannot rewrite. Spawn an adversarial subagent profiled as the producer's maintainer; negotiate the change as a feature request, not a PR. Companion to $sdk-design. Language-agnostic — applies to a TS package + its consumer, a Rust crate + its WASM binding, two services sharing a wire format, or any other boundary the same author writes both ends of.

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

Arbitrary write to RCE playbook. Use when you have an arbitrary write primitive (from heap exploitation, format string, or OOB write) and need to convert it into code execution by targeting GOT, hooks, _IO_FILE vtable, exit_funcs, TLS_dtor_list, modprobe_path, .fini_array, or C++ vtables.

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

Format string exploitation playbook. Use when printf-family functions receive user-controlled format strings, enabling arbitrary stack reads (%p/%s), arbitrary memory writes (%n/%hn/%hhn), GOT/hook overwrites, and canary/libc/PIE leaks.

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

Guided journey from a business with lucky months to a repeatable growth engine that produces a forecast. Orchestrates nine skills phase by phase - one-page-marketing, hundred-million-offers, predictable-revenue, contagious, influence-psychology, crossing-the-chasm, cold-start-problem, lean-analytics, negotiation - asking the user questions at every decision point and recording results in the project docs/ folder (MARKETING.md, OFFER.md, METRICS.md, GROW-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a marketing and sales system, manufacture predictable pipeline, engineer word-of-mouth and referrals, or says 'revenue is real but lumpy and I need growth that repeats'. If the offer, retention, or operations underneath are broken, run improve-business first; with no paying customers yet, start with create-business; when the product itself must carry the growth loops, use grow-app. For one framework in isolation, invoke that skill directly.

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

Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager's calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage, production principles, meetings as the medium of management, decisions, OKRs, and task-relevant maturity. For intrinsic motivation, see drive-motivation. For a company operating system, see traction-eos.

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

Guided journey from a stalled, plateaued business to one with an honest diagnosis, a working operating rhythm, and offers repriced to real value. Orchestrates eight skills phase by phase - good-strategy-bad-strategy, traction-eos, high-output-management, team-topologies, drive-motivation, lean-analytics, negotiation, monetizing-innovation - asking the user questions at every decision point and recording results in the project docs/ folder (STRATEGY.md, OPERATIONS.md, METRICS.md, IMPROVE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a business that has plateaued, diagnose why growth stalled, tighten strategy and execution, re-motivate a team, or says 'revenue is flat and I do not know why'. Starting from scratch with no customers: use create-business. Once the fundamentals work and the goal is expansion: use grow-business. When the product itself drags the business down: use improve-app. For one framework in isolation, invoke that skill directly.

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

Manages the relationship with a represented workforce — administering a collective agreement, handling grievances, understanding what supervisors may and may not say, and preparing for bargaining. Use this for a grievance or arbitration question, a work rule change in a represented unit, supervisor guidance during organizing, contract interpretation and past practice, or preparation for negotiations.

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

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.

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

Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.

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

Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.

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

Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor quality, or decide what to automate.

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

1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work. 2. Validate that the request matches the documented scope and stop early if the task would require unsupported as.

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

Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.

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

Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)

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

Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

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

Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version compatibility.

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

Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.

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

Scan a contract you're about to sign in plain language — surface the clauses that could bite you, what they mean, and what to question or renegotiate. Use when asked to check this contract before I sign, what am I agreeing to, are there red flags in this agreement, or explain this contract's risky bits. Produces a plain-English flag list of the risky/unusual clauses (auto-renewal, lock-in, liability, IP, termination, fees), what each means for you, questions to ask, and suggested changes — flagging when it's important enough for a lawyer. Not legal advice.

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

Decode a brand deal or UGC contract before signing — usage rights, exclusivity windows, whitelisting, payment terms, and kill clauses ranked 🔴🟡🟢 by what they can cost a creator, plus the counter-ask email. Use when a creator says 'is this brand deal fair', 'what does perpetual usage mean', 'they sent me a contract', or 'should I sign this collab agreement'. Produces a clause-by-clause decode, a money-math check on the rate, and a ready-to-send negotiation email. Not legal advice.

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

Make a genuinely good drink from the bottles already on your shelf — no special trip, no 12-ingredient recipe. Use when asked what can I make with [spirits], cocktail from what I have, I've got [bottles] what can I drink, or make me a drink without buying anything. Produces two or three cocktails you can build right now with ratios, a method, sensible substitutions for what you're missing, and a zero-proof version — scaled to how many you're making.

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

Compare job levels (职级) across Chinese technology companies and against international ladders, to judge an offer, a job move or a promotion target: what a level usually means in scope and expectations, how levels roughly line up, and what to ask the recruiter. Use when asked P7 相当于什么级别, 跳槽职级怎么对标, 字节 2-2 对应阿里什么, 这个 offer 的职级合理吗, compare Chinese tech levels, or how does Alibaba P-level map to Google levels. Produces a level comparison built from the person's own ladders and offer details, a scope-and-expectation profile for each level, the negotiation questions to ask, and a clear note on what is approximate.

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

Explain a contract clause in plain English — what it means, who it favours, the realistic risk, and what to negotiate. Use when asked what a clause means, to decode legal language, explain a term in a contract, or assess whether a provision is standard or aggressive. Produces a plain-language translation, a who-does-this-favour read, a risk rating, and concrete redline suggestions. Not legal advice; confirm with counsel.

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

Decode a mortgage Closing Disclosure line by line — which fees are real, which are shoppable or junk, and what changed since the Loan Estimate. Use when asked to decode my closing disclosure, review my closing costs, why did my costs go up, or which fees can I negotiate. Produces a section-by-section decode, the Loan-Estimate comparison with tolerance flags, the challenge list with scripts, and the cash-to-close verification.

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

Send your position to a meeting instead of your body — a one-page brief carrying your stances, fallbacks, red lines, tradables, and delegation limits, readable by the colleague (or agent) representing you. Use when you can't attend a decision-making meeting, when double-booked, when briefing someone to negotiate for you, or 'what would you need from me to represent me?'. Produces the clone brief plus a 60-second verbal version for the person carrying it.

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