client-scoping
/client-scoping
Przygotowuje rozmowy discovery, zakres i wycenę dla freelancera Figma i Webflow, wraz z wiadomościami o zaliczce i zakresie.
- Autor
- UncleBenisimo ↗
- Repozytorium
- claude-kit-designeri ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Przygotowuje rozmowy discovery, zakres i wycenę dla freelancera Figma i Webflow, wraz z wiadomościami o zaliczce i zakresie.
Wyzwalacze z opisu
Oryginalny opis (EN)
Prepares and processes client discovery calls, scoping and quotes for a freelance Figma + Webflow designer-developer. ALWAYS use when the user says "discovery call", "call cu clientul", "pregătește-mă pentru call", "scoping", "ofertă", "estimare", "cât să cer", "deviz", "propunere de proiect", "brief", pastes call notes or a client message about a new project, or needs a scope/quote/deposit message. Also use to turn messy call notes into a clear scope and next steps.
Jak działa
- Mode A — Before the call (prep)
- Mode B — After the call (notes → scope)
- Mode C — Client-facing message
- Rules
Podgląd SKILL.md
--- name: client-scoping description: Prepares and processes client discovery calls, scoping and quotes for a freelance Figma + Webflow designer-developer. ALWAYS use when the user says "discovery call", "call cu clientul", "pregătește-mă pentru call", "scoping", "ofertă", "estimare", "cât să cer", "deviz", "propunere de proiect", "brief", pastes call notes or a client message about a new project, or needs a scope/quote/deposit message. Also use to turn messy call notes into a clear scope and next steps. --- # Client Scoping Goal: walk into calls prepared, leave with a clear scope, and protect against unpaid scope creep. ## Mode A — Before the call (prep) Given what's known about the client/project, produce: 1. **What we know / what we don't** (2 short lists). 2. **Question list, grouped and prioritized** (max ~15, star the 5 must-asks): - Goals & success: why now, what's broken with the current site/platform, how success is measured. - Audience & content: who uses the site, languages, who writes content, is content ready, photos/brand assets. - Scope: pages/templates, CMS collections (events, articles, team…), forms, integrations (payments, memberships, newsletter, CRM, booking), animations. - Technical: current platform, domain/DNS/hosting access and who holds it, existing accounts (Stripe, analytics), migration of old content/SEO redirects. - Decision & budget: who decides, who gives feedback, budget range, deadline and what drives it. - After launch: maintenance, training, who edits the CMS. 3. **Risks to probe** (e.g., access held by a previous agency, no content ready, many stakeholders, "we'll know it when we see it"). 4. **A 1-sentence positioning line** to say if asked "why you". Always ask early who controls the domain, DNS and third-party accounts — lost access to these can block a finished project from going live. ## Mode B — After the call (notes → scope) From raw notes, produce: 1. **Scope summary**: in scope / out of scope (explicit) / open questions. 2. **Deliverables & phases**, typically: Discovery & sitemap → Design in Figma (key pages + responsive) → Webflow build & CMS → Integrations → QA, launch, handover/training. 3. **Estimate**: break into phases with hour ranges; show the math so the user can adjust the rate. Do not invent a market rate — ask for or use the user's rate. Add a buffer (10–20%) for revisions/unknowns and say so. 4. **Payment terms** recommended by default: upfront deposit before any work starts (commonly 30–50%), remaining tied to milestones; revisions included per phase stated as a number; extra requests billed separately. 5. **Assumptions** that the price depends on (content provided by client, X revision rounds, access to accounts by date Y). ## Mode C — Client-facing message Draft the follow-up/quote message in the client's language (RO/EN/RU): warm, concise, recap of their goals, scope, price or range, timeline, deposit, next step. No jargon. Keep it under ~250 words unless a formal proposal is requested. ## Rules - Never set prices on your own without flagging they're estimates to adjust. - Out-of-scope list is mandatory — it's what prevents scope creep. - Flag red flags plainly (no budget clarity, no decision-maker, unpaid "trial").
Wersje
W bazie nie ma innych skilli o nazwie client-scoping.
Migawka bazy z 13.11.2026 · wersja paczki f2798a5c6853 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100freelance-client-onboarding-discovery-calls
Prowadzi ustrukturyzowane rozmowy z potencjalnymi klientami, by zdiagnozować wymagania, ryzyka i zakres projektu. - 100upwork-proposal
Ocenia oferty pracy z Upwork lub cold maili i pisze przekonujące propozycje dla freelancera projektanta i programisty. - 100proposal-and-quote-drafter
Przygotowuje ofertę i wycenę dla klienta z notatek z rozmowy lub briefu: zakres, produkty, harmonogram, trzy pakiety cenowe i list przewodni. - 100freelance-client-ops
Prowadzi biznesową stronę pracy freelancera: oferty, umowy, zarządzanie zakresem, fakturowanie i komunikację z klientem. - 90webflow-mcp:figma-to-webflow
Buduje stronę, sekcję, komponent lub całą witrynę w Webflow z projektu Figma przez Figma MCP i Webflow MCP, jako żywe elementy i style. - 100client-call-notes
Spisuje notatki z rozmowy sprzedażowej lub z klientem: cele i bolączki klienta jego słowami, budżet, termin, zakres i dalsze kroki.