Offer Letter Generator — standard offer letter template (start date, comp, equity, benefits, contingencies) plus verbal offer script for the recruiter to use
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
693건 · 관련도순
Offer Letter Generator — standard offer letter template (start date, comp, equity, benefits, contingencies) plus verbal offer script for the recruiter to use
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Smart contract and Web3 security audit skill for Solidity, Vyper, Move, and Cairo. Covers reentrancy, access control, oracle manipulation, MEV/sandwich exposure, signature replay, upgrade safety, ERC token edge cases, bridge risk, and DeFi invariants. Tooling includes Slither, Mythril, Echidna, Foundry, Halmo, Certora, and custom invariant tests. Use for design review, code audit, and incident analysis on contracts you own or are authorized to assess.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
商业合同法律顾问。负责供应商协议审查、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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply risk-based test-driven development to bugs, domain logic, state transitions, parsers, contracts, migrations, and behavior where a failing test sharpens the design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 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 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 system architecture, API contracts, and data flows. Use when translating analyzed requirements into technical design for feature implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design REST APIs or function contracts with clear request/response specifications, error handling patterns, authentication strategies, and comprehensive documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch and run a freelance practice covering positioning, pricing, contracts, and client management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Packaging React components as a consumable library — style delivery contracts, sideEffects, cascade layers, "use client" preservation, peer dependency ranges, server-safe vs client entries
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Specification frameworks for features that call a model — approach tier, model pinning, output contracts, budgets, failure modes and eval design. Load when a spec touches model calls, prompts, retrieval, tool calling, agent loops or evals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CLI specification frameworks — flag contracts, prompt flows, config precedence, exit codes, output per context (TTY, piped, JSON), error and help text, signals and cross-platform behaviour. Use when a spec adds or changes a command surface, an interactive flow, a config key, an exit path or what a command prints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend specification frameworks — endpoint contracts, error catalogs, auth per endpoint, schema with constraints and indexes, migration strategy, middleware order. Load when a spec adds or changes an API endpoint, a database table, or a request pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.