본문으로 건너뛰기
cccskills
무료GitHub에 공개

vertical-onboarding

Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value target. Applied by migration-import-engineer and architect/pm so onboarding is designed as a funnel, not an afterthought. Our whole wedge is "low switching cost"; this skill makes that real on day one.

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

avelikiy/great_cto
연동 도구Shopify
설치 방법 보기

포함된 파일(1)

  • SKILL.md4.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Vertical onboarding — switch them in, to first value, fast

The incumbent's moat is switching cost. Our wedge is dissolving it. Onboarding is where that promise is kept or broken. Design onboarding as a funnel with one activation milestone, import-first.

1. Import-first, not blank-slate

The default first-run path is "bring your data from {incumbent}", powered by migration-import-engineer's import contract — not an empty dashboard the user must fill by hand. A new user should see their own customers/jobs/menu/listings within minutes.

  • Offer the import on screen one, with the named incumbent ("Import from ServiceTitan").
  • Run it as a dry-run preview the user approves (the import contract's operator step).
  • Provide a sample-data fallback ("Explore with example data") for users who can't export yet — never a dead empty state.

2. One activation milestone (define it per product)

Pick the single action that means "this user got value" — the north-star of onboarding. Everything in first-run drives toward it. Examples:

productactivation milestone
quoting (home services)sent first priced quote
online-ordering (restaurants)published menu + took first test order
class-booking (fitness)imported members + first class booked
inventory (retail)synced catalog + first reorder rule set
transaction-coordination (real estate)first transaction checklist created
sponsorship-crm (creator)first sponsor + deal stage

Measure time-to-first-value (TTFV); target minutes, not days. State the target in the architecture doc.

3. The onboarding funnel (spec these steps)

1. Identify incumbent → 2. Import (dry-run → approve) → 3. Verify own data
→ 4. Complete the one setup the product needs → 5. Activation milestone → 6. Invite team

Each step: a clear single CTA, skippable where safe, resumable, and with progress shown. Defer everything not on the path to the activation milestone.

4. Reduce setup to the minimum

  • Pre-fill from imported data wherever possible (branding from the website, hours from the listing, tax rate from the address).
  • Sensible defaults over required choices; advanced config lives in settings, not onboarding.
  • One required integration max before activation (e.g. Stripe for quoting) — sequence the rest after first value.

5. Trust + reversibility

  • Show what was imported and let the user undo a batch (ties to the import contract's rollback) — trust comes from "you can't break anything."
  • Don't ask for payment details before the activation milestone unless the product is charge-to-use.

Output

When applied, contribute an Onboarding section to the architecture or design doc:

## Onboarding
- incumbent(s): <names> → import via docs/data-import/IMPORT-{slug}.md
- activation milestone: <the one action>
- TTFV target: <minutes>
- funnel: identify → import(dry-run→approve) → verify → setup → activate → invite
- empty-state fallback: sample data
- required-before-activation: <≤1 integration>

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

aesthetic-instrument

무료

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.

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

avelikiy/great_cto1052026년 10월 22일 업데이트

anti-patterns

무료

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

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

avelikiy/great_cto1052026년 10월 22일 업데이트

anydesign

무료

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

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

avelikiy/great_cto1052026년 10월 22일 업데이트

archetype-review-base

무료

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

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

avelikiy/great_cto1052026년 10월 22일 업데이트

brainstorming

무료

Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.

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

avelikiy/great_cto1052026년 10월 22일 업데이트

codex-host

무료

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.

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

avelikiy/great_cto1052026년 10월 22일 업데이트

avelikiy의 스킬 모두 보기

이 스킬의 문제 신고