Design performance management system - review cycles, calibration process, career ladder, and PIP framework. Use when asked to "build a performance review process", "design career levels", "how do we handle underperformers", or "run a review cycle".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build onboarding playbook - day 1 through week 4 checklist, access provisioning, context transfer, and success milestones. Use when asked to "build an onboarding process", "how do we onboard new hires", or "reduce time to productivity for new joiners".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run human-to-agent migration - audit which roles can be agent-assisted or replaced, design the transition playbook, and manage the offboarding of displaced roles. Use when asked to "which roles can agents replace", "how do we transition to AI-first ops", or "build our agent migration plan".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and build database schema — tables, columns, types, indexes, constraints, relationships. Given a domain description, output the schema and write the files. Use when asked to "design schema", "database design", "create tables", or "data model".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Wireframe a screen — text/ASCII by default, or hand-drawn HTML when the user says "sketch", "hand-drawn", "lo-fi HTML", "whiteboard", "graph paper", or "visual wireframe". Text mode produces a buildable ASCII spec Form and Prism can act on. HTML mode produces a single self-contained file with graph-paper background, marker headlines, sticky-note annotations, and hatched chart placeholders — looks like a designer's whiteboard, commits to nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Close a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answer this objection".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and execute canary releases for model updates — traffic splitting, rollback triggers, success metrics. Use when asked to "canary the new model", "roll out this model safely", or "set up a traffic split for a model update".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing. Use when asked to "price this deal", "build a sales playbook", "close an enterprise deal", or "manage the B2B pipeline".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing CDN and edge configuration — find cache misses, missing headers, and performance gaps. Use when asked to "audit our CDN", "why is our cache hit rate low", or "find edge config gaps".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build automated regression suites — golden sets, threshold alerting, CI integration for model changes. Use when asked to "catch model regressions in CI", "build a golden set", or "automate eval regression".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and configure model serving infrastructure — endpoint scaling, batching, GPU allocation. Use when asked to "serve this model", "design an inference endpoint", or "size GPU allocation for serving".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or audit a feature store — serving, freshness, and sharing across models. Use when asked "do we need a feature store", "design a feature store", or "share features across models".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cold outbound sequence builder — produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.