'ramp' 검색 결과

30/60/90 Day Onboarding Plan — Day 1 setup, week 1 ramp, month 1 milestones, month 2 contributions, month 3 evaluation criteria

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

Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行

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

Product-launch command desk (Busabase App-in-Skill) built on the RAMP discipline — Research / Assemble / Mobilize / Prove. The agent assembles the launch checklist and drafts launch assets, channel submissions (Product Hunt / Hacker News / directories), press pitches, and the launch-day runbook; the human approves the launch-readiness gate and steers launch day in a review UI. Use when the user invokes $kelly-launch or /kelly-launch, or mentions launching / shipping a product, a launch checklist or runbook, launch readiness, RAMP, Product Hunt / Show HN / press-kit / launch-email drafting, or wants to review and approve launch assets and channel submissions before they go public. This is launch OPERATIONS — the checklist, assets, submissions, and runbook — not a launch video (for a promo video use product-launch-video).

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

화면의 여백, 글자, 모서리 둥글기, 그림자와 움직임을 점검해 외관과 조작감을 다듬습니다. 버튼과 카드 등의 구체적인 개선안을 변경 전후로 제시합니다.

• 답답하거나 미완성처럼 보이는 화면 점검
• 버튼, 카드, 폼의 세부 마무리
• 호버 및 로딩 상태 개선

Review CSS color definitions and convert palettes to oklch(), a color format designed around human perception. Use consistent lightness steps to build color scales, dark-mode palettes, and interaction states, with guidance for wide-gamut displays.

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

• Organizing reusable CSS color definitions
• Building color scales with consistent perceived lightness
• Designing dark-mode and hover colors

Edit screen recordings from the command line with zoom effects, speed changes, cuts, cropping, and text annotations. Adjust backgrounds and framing, review rendered previews, and export the finished video as MP4 or GIF.

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

• Create a demo video from a screen recording
• Zoom in on important steps
• Cut or speed up waiting time

Create step-by-step code walkthroughs tailored to readers such as new contributors, reviewers, or bug fixers. Produce CodeTour .tour files linked to verified files and line numbers, with explanations of behavior, design choices, and pitfalls.

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

• Create a code walkthrough for new team members
• Guide reviewers through a PR and its risks
• Trace code involved in a bug or incident

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

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

• Define the assessment scope for systems handling controlled information
• Calculate an SPRS score and prioritize unmet security requirements
• Prepare security plans, remediation milestones, and assessment evidence

Process vendor bills, assign accounting categories, check cash forecasts, and prepare a payment run for approval. Separate approvals for recording bills and paying them help owners review both the accounting entries and the proposed spending.

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

• Process a backlog of vendor bills
• Check available cash before paying bills
• Prepare this week's payment list

Create a one-page Monday briefing that combines cash, sales, sales opportunities, saved performance reports, and upcoming commitments. Identify one priority for the week using connected services or data supplied through pasted text and uploaded files.

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

• Reviewing cash, sales, and sales opportunities on Monday
• Combining saved performance reports into a weekly briefing
• Checking upcoming commitments and replies you owe

Coordinate month-end reconciliation, owner sign-off, and a 30/60/90-day cash forecast based on closed books. Combine the results into a reporting packet with financial explanations and open items, with approval required before external delivery.

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

• Reconcile monthly books against payment data
• Explain changes in revenue and margin
• Refresh cash forecasts using closed-month figures

Create green isometric illustrations, using angled views without perspective, of developer and design workspaces as SVG files. A bundled drawing kit helps arrange equipment on one platform, with consistent shading, fine details, shadows, and validation checks.

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

• Illustrate a server room or development stack
• Show a CI pipeline as an illustrated scene
• Create artwork for empty states and onboarding

Build fire effects in Three.js, including fireballs, moving flame fronts, whirls, and smouldering ground. A reusable module combines rising flames, temperature-based color, smoke, sparks, heat distortion, and shared firelight, with a five-stage demonstration.

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

• Creating held flames and thrown fireballs
• Building expanding walls and rings of fire
• Staging fire whirls with smoke columns

Manage a crypto wallet with the awal CLI, including sign-in, balance checks, transfers, swaps, and funding. Also find and pay for APIs through x402, a payment protocol, set up paid endpoints, and query blockchain data on Base.

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

• Check wallet balances across supported networks
• Send tokens to an address or ENS name
• Swap tokens or add wallet funds

Run stepped HTTP load tests with ab/wrk, ramping concurrency levels to collect p50/p90/p99 latency, detect performance inflection points, and recommend optimal concurrency. Triggered by requests like 'load test this URL', 'benchmark my API', 'find the max concurrency', or mentions of p99 latency, throughput saturation, or capacity planning.

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

Use when styling UI for ramp.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

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

Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.

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

Recommend the right trading workflow, skillset, API profile, and setup path from a natural-language goal. Use this as the on-ramp when a user expresses a trading or investing goal and needs to know which skill/workflow to use, where to start, or whether something works without paid API keys — e.g. "where do I start", "which skill should I use", "I want to swing trade only when the market is favorable", "what works without API keys", "どれを使えばいい", "API キー無しで 使えるものは". Routes and explains only; it never executes trades or auto-runs other skills, and it is honest when no workflow has shipped yet.

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

Use when the user asks to "plan the participation ramp before we promote", "how much account history or karma do we need in this community", or "design entry incentives and member lifecycle for our own Discord"; produces the per-community pre-promotion warming plan — account-history/tenure expectations (Estimated, named sources), a give-before-ask ledger spec, a per-community etiquette + rule digest with last-verified dates, and the warming → active graduation criteria that channel-registry requires as state-transition evidence — plus the owned-community variant (entry paths + member lifecycle for your own Discord/Slack/forum/企业微信私域). Not for launch-day submissions or T-0 threads — use community-launch-runner. 社区预热/先给后取/账号养成/毕业标准

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

Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar early-warning (Estimated heuristic), PH votes/featured status, store charts and reviews, news echo, D0/W1/M1 KPI snapshots vs targets, spike-vs-sustain and owned-capture reads, and alert thresholds against the launch-tier KPI targets. Not for launch-day go/rollback calls — use launch-day-conductor; not for metric deep-dives — use performance-analyzer; not for SEO rank tracking — use rank-tracker. 发布监控/排名轮询/火焰战比/spike-sustain

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

Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a warmup + send-throttle ramp schedule, jurisdiction opt-in/CAN-SPAM guardrails (guidance, not legal advice), and a SEND S-dimension read. Not for B2C lifecycle flows — use email-sequence-designer; not for the consent record — use consent-registry; not for computing EQS — use email-quality-auditor. B2B冷启动外联序列/回复分流/域名预热

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

Use when the user asks to "log this launch", query a launch date/embargo, record a stage transition, or update submissions/outcomes; curates launch facts through the append-only launches event stream with optimistic revisions and derived dossier/calendar views. Not for RAMP scoring — use launch-readiness-auditor; not for planning tier/window — use launch-tier-planner. 发布台账/发布日历/阶段与禁运期记录

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

Select chart types and design data encodings — marks, axes, labels, and accessible chart styling. Use when presenting data graphically. Owns chart selection and encoding only; the categorical colour ramp itself belongs to `color-system`.

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

Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner or leaver.

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