'contracts' 검색 결과

Use after a backend build succeeds or whenever authentication, authorization, actor/identity handling, external service calls (IdP, JWKS, DB, clock), logging, observability, configuration or error contracts are in play — delegates to the backend-design-reviewer agent for a design-quality review of the current branch.

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

Influencer/creator marketing command desk (Busabase App-in-Skill) — the agent sweeps and fit-scores creator candidates, drafts outreach and briefs, and gates content before it ships; the human reviews creator cards, approves outreach/briefs/contracts, and tracks campaign ROI. Use when the user invokes $kelly-creators or /kelly-creators, mentions influencer or creator marketing, creator discovery, fit scoring, outreach DMs, campaign briefs, UGC, sponsorship or partnership deals, content review / FTC disclosure gating, or campaign ROI, or wants to review/approve agent-drafted creator outreach before it is sent through other channels.

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

Delegate writing predictable code to the `code-write` command, which has a cheaper writer model write the target file directly so the generated code never enters your context. Use for tests, scaffolding, fixtures, boilerplate, or a new file that copies an existing pattern, and when the user says "code write", "生成を委譲", or "雛形を書かせて". Do NOT use for design decisions, changes to public contracts or shared modules, edits inside an existing file that needs judgment, or logic with subtle correctness requirements.

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

Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.

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

Stellar dApp / frontend development. Covers the JavaScript stellar-sdk (browser + Node.js), Freighter wallet, Stellar Wallets Kit (multi-wallet), Wallet Standard, smart accounts with passkeys, transaction building / signing / submission, smart contract invocation from the client, simulation, and error handling. Use when building a React/Next.js/Node.js app that talks to Stellar — classic operations or smart contracts.

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

PM planning workflow — analyze requirements, select tech stack, decompose into prioritized tasks with dependencies, and define API contracts

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

Convert external documents — specs, contracts, reports — to markdown for knowledge base ingestion.

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

Check, from the employer's side, what has been put in writing before a paid Otameshi Tenshoku assignment starts under gyomu-itaku: item by item whether the deliverable, delivery date, fee and how it is calculated, payment due date, who pays, out-of-scope work, revision limits, company support, rights, confidentiality and termination are stated in a contract, purchase order or email rather than in chat or by word of mouth, count the days from delivery to payment, and find pay tied to satisfaction or hiring, unpaid or unlimited revisions and one-sided termination. Use when a hiring manager, recruiter or small-business owner is about to offer terms to a candidate, has been asked by a candidate what is still unwritten, or needs the conditions written for a platform contract screen; do not use to judge whether the terms are lawful or the fee fair, to compute withholding or consumption tax, for employment contracts, or to sign, send or conclude the contract on the user's behalf.

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

Handles BED-format genomic intervals (BED3 through BED12, narrowPeak/broadPeak) and the coordinate-system substrate the whole interval category rests on, with bedtools (CLI) and pybedtools/pyranges/pandas (Python). Covers the 0-based half-open vs 1-based-closed convention boundary and the start-1/end-unchanged conversion, the silent failures (chrom-name mismatch, CRLF, lexicographic-vs-version sort under -sorted), genome/chrom.sizes generation, sorting contracts, BED12 block invariants, validation, makewindows, cross-assembly liftover (liftOver/CrossMap), and BED<->VCF/BAM/FASTA conversion. Use when reading, creating, validating, sorting, lifting between genome builds, or converting interval files, preparing inputs for bedtools/tabix/bigBed, or debugging an off-by-one or empty-overlap result.

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

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.

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

Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits. Skip for Q&A or trivial edits.

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

Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.

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

Create or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnica', 'techspec do prd-SLUG', 'design the solution for…'. Do NOT use to change product scope, before PRD and stories approval, or for design notes outside SDD.

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

Reconcile SDD Composy task Markdown and the JSON projection: read-only inspect and plan, then apply only with an explicit authority and the CONFIRM-SDD-SYNC token. Use when task contracts and operational state diverged — 'sincronizar as tarefas', 'o JSON das tasks está desatualizado', 'markdown and json disagree'. Do NOT use to list or advance tasks (sdd-tasks), for a status overview (sdd-status), or to simulate approval.

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

Read-only consolidated snapshot of an SDD Composy workspace: lifecycle stage, task contracts, trace integrity, loops, fleets, and the next action, without changing any file. Use for 'em que pé está o SDD', 'status do fluxo', 'qual a próxima ação', 'where are we in the workflow'. Do NOT use for git, CI, infrastructure, or other plugins' status, or to change state.

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

Generate and safely advance the SDD Composy task projection from approved PRD, stories, and TechSpec: import contracts, list/next/show, and guarded start/block/transition/verify. Use when work must be decomposed or a task's state inspected or moved — 'quebrar a spec em tarefas', 'listar as tarefas', 'qual a próxima task', 'mark TASK-003 blocked'. Do NOT use to implement a task (sdd- execute), reconcile Markdown and JSON (sdd-sync), or for a status overview (sdd- status).

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

Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.

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

Enforces modern TypeScript best practices for type-safe code, strict configuration, runtime validation, and clear type contracts. Use when writing or reviewing TypeScript/JavaScript code, configuring tsconfig.json, or when the user asks for TypeScript style guidance.

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

Turn a chosen design direction into a canonical DESIGN.md plus production tokens that don't look vibecoded — state-level colors (8-step neutral ramp, rest/hover/active/ disabled, focus ring), APCA-checked contrast, typography, spacing/radius/motion/elevation, an icon strategy, and component contracts for the core atoms. Emits tokens in the project's stack format (shadcn HSL vars or Tailwind v4 @theme). Load when the user asks to build a design system, generate design tokens, create a DESIGN.md, set up a theme, design a color or type system, pick icons, or when frontend-design routes here. Replaces design-tokens-craft and icon-craft. Sub-skill of frontend-design. Reads DIRECTION.md first.

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

Design stable APIs and module boundaries — contract-first types, consistent errors, boundary validation, additive changes. Load when designing REST or GraphQL endpoints, public module interfaces, component props, or FE/BE contracts. Also triggers on "API design", "interface design", "design the API", "module boundary", "API contract", "define the interface". Complements feature-spec (product layer). Routes breaking retirement to api-deprecation-and-migration when it exists.

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

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.

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

Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.

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

Handles BED-format genomic intervals (BED3 through BED12, narrowPeak/broadPeak) and the coordinate-system substrate the whole interval category rests on, with bedtools (CLI) and pybedtools/pyranges/pandas (Python). Covers the 0-based half-open vs 1-based-closed convention boundary and the start-1/end-unchanged conversion, the silent failures (chrom-name mismatch, CRLF, lexicographic-vs-version sort under -sorted), genome/chrom.sizes generation, sorting contracts, BED12 block invariants, validation, makewindows, cross-assembly liftover (liftOver/CrossMap), and BED<->VCF/BAM/FASTA conversion. Use when reading, creating, validating, sorting, lifting between genome builds, or converting interval files, preparing inputs for bedtools/tabix/bigBed, or debugging an off-by-one or empty-overlap result.

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

Use this skill when the user asks about towing + recovery operations — separate FMCSA authority class, light-duty vs medium-duty vs heavy-duty wrecker rules, AAA + AAA-Plus contracts, Roadside-Assistance (RA) operations, "non-consensual tow" rules + state-by-state, and how towing operations differ from general freight. Reference state Public Utility Commission + 49 CFR 395 application.

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