저장소 README를 불러오는 중…
수집된 skill 45개 중 40개를 표시합니다.
Design a shipped feature so it actually gets used — lower the cost of starting, give one obvious next step, and plan for the moment the user stalls, is embarrassed, is in the wrong place, or gets it wrong. Draws the pattern library from Duolingo's public…
원문 언어: 영어
Run LLM agents as production infrastructure instead of demos — split what an agent is (prompt, tools, access, output schema) from how it runs (runtime, model, SDK, environment), make every step durable and retryable, grade the diff instead of the prose, cap…
원문 언어: 영어
Decide where to point AI so it changes your cost structure instead of adding a feature — which bottleneck absorbs the automation budget, how to divide labor between expert staff and models, when to adopt a capability that is still visibly bad, and how to make…
원문 언어: 영어
Treat working memory as the binding constraint on every screen, session, and document — cap what competes for it, cut what wastes it, and deliberately spend what is left on the one thing you are trying to teach. Covers how much new material fits in one unit,…
원문 언어: 영어
Make a server request fast and hard to break, using Duolingo's published engineering results as the case study. Covers what to delete from the synchronous request path, how to split data into precompute-and-cache versus caller-injected, how long to hold a…
원문 언어: 영어
Duolingo's playbook for picking and entering a new market or adding a second product line — where to attack an incumbent, what to port from the product that already works, and what to rebuild from a blank page. Use when someone asks "should we enter this…
원문 언어: 영어
Build a reusable cast, illustration style, animation vocabulary and avatar system that a small team can actually produce at volume, and make those assets do product work instead of decorating it. Covers choosing a visual style by production throughput,…
원문 언어: 영어
Build the team the way Duolingo built theirs — the Green Machine operating model, talent density over headcount, candor protocol ("focus on what, not who"), hire-slow / fire-fast, and the "no process unless it makes decisions better" rule. Use when the user…
원문 언어: 영어
UI patterns from the Duolingo design system — juicy motion, the character system as the emotional channel, design tokens (color/type/spacing), sound as a UX surface, accessibility as a default not a checklist, and "error-as-delight" detailing. Use when the…
원문 언어: 영어
Put each user at the edge of what they can currently do — estimate item difficulty and user ability in one model, target a band rather than a floor, and use live signals to tell whether the model is honest. Covers joint item-user modelling, the…
원문 언어: 영어
Prove your product actually works — with instruments you did not author, on axes that do not substitute for each other, and in a way a skeptic outside your company can check. Covers the four-axis efficacy framework (enjoyment, mastery, real-task application,…
원문 언어: 영어
Drive the marginal cost of an experiment toward zero so a team runs hundreds of tests a quarter instead of three. Covers experimentation as shared internal infrastructure rather than a per-test project, how the cost of the marginal test quietly selects which…
원문 언어: 영어
Duolingo-style experimentation as a decision protocol — hundreds of A/B tests a week, opinions resolved by data, ideas killed quickly. Covers hypothesis design, metric selection, guardrails, sample size, novelty effects, and explicit kill criteria. Use when…
원문 언어: 영어
Run in-house expertise as a credentialed publishing program fed by the questions users already send you, and earn trust by marking in public where your evidence stops. Covers turning a support inbox into a recurring column, the named expert byline and when to…
원문 언어: 영어
Decide where the paid line sits when your free tier is also your distribution engine — what to charge for, what to never charge for, and when an upsell costs more than it earns. Covers friction-removal pricing versus core-value paywalls, metering a premium…
원문 언어: 영어
Add Duolingo-style play to any product — XP systems, juicy feedback, leagues, celebration moments, hearts/energy, and the anti-grind discipline that keeps gamification from turning toxic. Use when the user asks how to make a product fun, addictive, or "feel…
원문 언어: 영어
Decide what to measure and which single lever to staff when your top-line engagement number has gone flat, and how to read demand that arrives from outside your product. Covers decomposing a top-line number into user states and transition rates, spotting when…
원문 언어: 영어
Duolingo-style growth that doesn't break retention — viral loops, brand-as-acquisition (the TikTok playbook), referral mechanics, localization as a growth lever, and the founder-mode marketing that turned a mascot into a meme. Use when the user is planning…
원문 언어: 영어
Stop your product filtering people out on circumstance instead of ability. Covers removing preconditions (location, hardware, contiguous free time), building escape hatches at the level of the blocked capability rather than the session, putting scaffolding on…
원문 언어: 영어
Make infrastructure spend visible, attributable and cuttable without slowing the company down — hourly per-dimension cost tagging, pushing the number into channels engineers already read, defining a win as waste removed rather than spend removed, pricing tech…
원문 언어: 영어
Keep people attempting a skill they believe they are bad at — by lowering what it costs to be visibly wrong, replacing unscoreable goals with ones they can hit, pre-announcing how bad early progress will feel, and supplying the attribution that turns a…
원문 언어: 영어
Make an LLM or agent feature survive its ten-thousandth call — split the prompt into a fixed constraint zone and per-instance slots, decompose a long interaction into one narrow prompt per move, isolate the high-stakes generation into its own call,…
원문 언어: 영어
Ship your product to people who do not share your language, script, reading direction, demographics or fluency with software — and decide which markets that opens. Covers writing into the register users actually speak instead of the formally correct one, why…
원문 언어: 영어
Design and report a number that survives an outsider's scrutiny — prove the outcome on an instrument you did not build, break a headline score into components only when they add information, publish the component where you lose, audit bias at intersections…
원문 언어: 영어
Decide when to bring something back in front of a user, and treat every capability they have as quietly rotting rather than banked. Covers spacing versus massing at equal cost, per-item half-life scheduling instead of fixed interval ladders, retrieval versus…
원문 언어: 영어
Choose, weight and defend the single number your team is graded on, so that moving it means users actually got value rather than merely spent time. Covers putting activity weights inside the formula instead of a memo, threshold-percentage goals versus…
원문 언어: 영어
Decide where a learned model beats a hand-written rule tree, judge it on a metric that moves where users actually care, and run a generation pipeline that does not quietly produce errors at scale — ranking noisy queues instead of filtering them, harvesting…
원문 언어: 영어
Make a shipped client app start fast, stay small, and stay cheap to change — startup budgets scored against conversion rather than milliseconds, deferring non-first-screen work, perceived versus actual latency, device-tier and worst-region equity, profiling…
원문 언어: 영어
Work out which users will still be here in a year and why — segmenting by the motive they gave rather than by age, country or plan tier — then build the attachment, ritual and permission that keep an optional behaviour worth doing. Covers relational versus…
원문 언어: 영어
Ask users why they are here, store that declared motive as a first-class dimension next to behaviour, and learn where self-report and telemetry each lie to you. Covers collecting a stated reason at signup, why the biggest segment is usually not the most…
원문 언어: 영어
How to name things, design symbols, and write reference material so users derive the answer instead of memorizing it — and how to handle the near-misses, overloaded tokens and silent misreadings that produce confident wrong behaviour. Use when asking what…
원문 언어: 영어
Make effort feel like it is going somewhere — pick the granularity of your progress number, size the unit of work that ends in a completion event, set an honest timeline, and decide what to say when a user stalls because they succeeded. Covers shipping a…
원문 언어: 영어
Work with the mental model your users already carry from a prior system — where it transfers free, where it fires a confident wrong answer, and how to redirect it instead of fighting it. Use when users keep doing things the old way after a migration or…
원문 언어: 영어
Make product decisions the way Duolingo does — long-view over short-term, ruthless prioritization, ship-and-learn over plan-and-ship, dogfooding, and the "intuitive by default" quality bar. Use when the user is roadmapping, deciding what to cut, debating…
원문 언어: 영어
How to know what production is actually doing, and what to run when it breaks — extracted from Duolingo's engineering blog and made portable to any product. Covers always-on request identity versus sampled tracing, runtime dead-code detection, kill switches…
원문 언어: 영어
Decide what a product teaches, in what order, and with how much support — then design the removal of that support instead of leaving it in forever. Covers sequencing by task rather than by the subject's taxonomy, borrowing an external standard as the…
원문 언어: 영어
Turn behavioural logs you already hold into a recurring public report that journalists, researchers and buyers cite instead of discounting. Covers cadence and a frozen measurement window, which unit to cut the data to so readers find themselves in it,…
원문 언어: 영어
Duolingo-style retention engineering for any product — habit loops, streaks, leagues, churn diagnostics, day-N drop-off, and the discipline of building a "forever product." Use when the user asks how to keep users coming back, debug churn, design a streak…
원문 언어: 영어
How to cause the next session to start — where the reminder lives, when you have earned the right to ask for notification permission, what an ambient widget or lock-screen surface should show, how to attach a new behaviour to a cue the user already fires, how…
원문 언어: 영어
Decide whether to explain something at all, when the explanation should land, and how to compress a rule into something a user can actually execute under pressure. Use when you are writing docs, tooltips, onboarding copy, error messages, a runbook or a…
원문 언어: 영어
이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/HKTITAN/duolingo.README를 불러오지 못했습니다. 아래의 저장소 Skill 목록은 계속 이용할 수 있습니다.