업무 효율화 스킬

Check an educational practice or task for cultural bias, WEIRD assumptions, and cross-cultural validity. Use when adapting resources for diverse contexts or questioning universal claims.

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

Orchestrate compassionate systems tools from issue or aspiration to wise action. Use when a class needs a complete inquiry workflow.

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

A harness that makes Opus (or any Claude model) behave like Fable — it enforces seeing a task through to the end, with evidence and verification, as procedure. Use when starting a multi-step task (2+ sequential stories), long autonomous work, debugging or root-cause investigation, building render/executable artifacts (HTML, SVG, games, charts), or when the user says "fablize", "see it through", "verify as you go", "split into goals".

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

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

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

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.

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

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.

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

Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.

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

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

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

Shape output for a reader with ADHD. Use this skill whenever responding to ANY user message including coding tasks, debugging, explanations, planning, and casual conversation. Output should lead with concrete next actions, number multi-step work, externalize state across turns, suppress tangents, give specific time estimates, and make wins visible. Trigger even on casual messages and even when the user did not explicitly ask for brevity.

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

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

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

Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

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

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

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

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

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

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

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

Project onboarding - determine project type, complexity, tech stack, and route to correct phase

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

AI-assisted development, testing, and reverse engineering through structured agent collaboration

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

Brownfield improvements — the full WDS pipeline in miniature for existing products

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

Create UX scenario outlines from Trigger Map through structured micro-steps

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

Map business goals to user psychology through structured workshops

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

Create alignment around your idea before starting the project

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

Establish project context - foundation for all design work

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

Generate visual and text assets from specifications through AI-powered creative production

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