이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/kensaurus/cursor-kenji.저장소 README를 불러오는 중…
수집된 skill 163개 중 40개를 표시합니다.
Plan-only GTM audit: detect monetization model, positioning, activation funnel, SEO/AEO and distribution, interview the founder one question at a time, emit a phased plan. Use when "GTM", "go-to-market", "get more users", "grow traffic", "should this be…
원문 언어: 영어
Read-only audit of where a repo is discovered: README first screen, npm / PyPI metadata and tarball, GitHub description, topics, social preview, plugin manifests, install one-liner. Use when "audit our npm listing", "README as landing page", "GitHub topics",…
원문 언어: 영어
Write honest bottom-funnel pages — "X vs Y", "alternatives to X", "migrate from X" — from verified facts, one unique page each, with a review date so they never rot into spam. Use when "comparison page", "vs page", "alternatives to", "competitor page",…
원문 언어: 영어
Versioned launch kit from the repo's real features: Show HN post, Product Hunt listing, Reddit / X / LinkedIn posts, article outline, release notes, calendar with UTM links. Use when "launch post", "Show HN", "Product Hunt listing", "announce this release",…
원문 언어: 영어
Apply-now growth loops on an existing product: "powered by" badge, shareable artifacts and templates, invite and referral credit, each with its own K-factor events. Use when "referral program", "viral loop", "powered by badge", "get users to invite".…
원문 언어: 영어
Apply-now lifecycle email driven by product events: activation nudges, trial-expiry track split by activated vs stalled, limit-reached upgrade, win-back — with exits, consent, and per-email events. Use when "onboarding emails", "trial expiry emails", "drip…
원문 언어: 영어
Apply-now activation pass: define the activation event, cut steps before first value, add empty-state templates, sample data, a short checklist; instrument signup→activated→habit. Use when "improve onboarding", "users sign up and leave", "time to value",…
원문 언어: 영어
Apply-now conversion pass for landing, pricing, and upgrade paths: hero matched to positioning, one CTA, real proof, tier packaging with anchor and annual toggle, upgrade prompts at value moments. Use when "pricing page", "improve conversion", "free to paid",…
원문 언어: 영어
Weekly go-to-market review for a shipped product: funnel by source, activation cohort, top drop-off, launch results, then one experiment and one post, scorecard row appended. Use when "weekly growth review", "what should we do this week for growth", "GTM…
원문 언어: 영어
Plan-only pricing and packaging audit: value metric, tiers, price points, free-tier boundary, annual and enterprise anchors, credits, plus a willingness-to-pay research plan. Use when "pricing strategy", "what should I charge", "value metric", "seat vs…
원문 언어: 영어
Take a shipped repo to market: plan-gtm audit + interview → approval → measure → message → activate → be found → launch → weekly loop. Use when "go to market", "grow users", "increase traffic and visibility". Strategy only → plan-gtm. Technical pre-launch…
원문 언어: 영어
Review this PR or diff for quality, security, and maintainability. Use when reviewing pull requests, examining a named change set, or the user asks for a code review of current work. Repo-wide anti-patterns → audit-code-quality. Bulk transform semantics →…
원문 언어: 영어
Run a PDCA quality audit on LLM/AI features: traces, prompts, costs, evals, grounding, hallucination. Use for "audit LLM quality", "check Langfuse", "audit prompts", "check AI quality", "audit AI costs", "check traces". Jailbreak/OWASP LLM →…
원문 언어: 영어
Implement error-handling patterns (boundaries, toasts, API error shape). Use when "error boundary", "error toast", or "standardize API errors". Plan-only observability audit → plan-error-handling. Live Sentry triage → debug-sentry-monitor.
원문 언어: 영어
Apply backend patterns — queues, caching, rate limits, serverless/edge. Use when "queue jobs", "caching layer", "rate limiting", "server actions", or "edge function". Which architecture to pick → audit-backend-architecture.
원문 언어: 영어
Implement real-time features using WebSockets, Supabase Realtime, Server-Sent Events, and live data. Use when user wants "real-time", "live updates", "WebSocket", "notifications", "chat", "collaborative", "presence", "live data", or "instant sync".
원문 언어: 영어
Create Cursor rules for persistent AI guidance. Use when user wants to create a rule, add coding standards, project conventions, file-specific patterns, or mentions ".cursor/rules", "AGENTS.md", "cursor rule", "coding standard", "convention", or "AI guidance".
원문 언어: 영어
Guide users through creating effective Agent Skills for Cursor. Use when user wants to create, write, update, or debug a skill, or asks about SKILL.md format, skill structure, ~/.cursor/skills/, or skill best practices.
원문 언어: 영어
Modify Cursor/VSCode user settings in settings.json. Use when user wants to change editor settings, preferences, themes, font size, tab size, keybindings, or mentions "settings", "preferences", "theme", "font", "format on save", "auto save", or "cursor…
원문 언어: 영어
Build interactive, accessible charts, graphs, and data dashboards using Recharts, D3, or Victory. Use when the user says "chart", "graph", "data visualization", "analytics dashboard", "metrics display", "D3", "Recharts", "time-series", or "data display".
원문 언어: 영어
Diagnose one error/bug with hypotheses and runtime evidence before fixing. Use when "debug this error", "investigate this bug", or behavior is unexpected. FE↔BE contract mismatch → debug-fe-be-integration. Sentry backlog/monitoring → debug-sentry-monitor.…
원문 언어: 영어
Design RESTful and GraphQL APIs following current best practices for naming, versioning, error shapes, and auth patterns. Use when the user says "design an API", "create endpoints", "structure my API responses", "plan API architecture", "REST vs GraphQL", or…
원문 언어: 영어
Create museum-quality visual art in .png and .pdf formats using design philosophy. Use when user asks for poster, visual design, infographic, certificate, badge, banner, social media graphic, print design, or mentions "create artwork", "design graphic",…
원문 언어: 영어
Create original algorithmic visuals with p5.js, Canvas, or SVG using seeded randomness and interactive controls. Use when "generative art", "procedural visuals", "flow fields", "particle system", or "art from code". Data charts → data-visualization. UI…
원문 언어: 영어
Design mobile-first UIs: touch targets, safe areas, gestures, then enhance up. Use when building for small screens, touch, swipe, PWA, or tablet. Linearized desktop / responsive audit → audit-responsive.
원문 언어: 영어
Design and implement new isolated motion — micro-interactions, page transitions, scroll, hover — with Framer Motion, CSS, or GSAP. Use when adding one animation to a new surface. Existing-app coherent pass → enhance-motion. Do not fire for "motion pass across…
원문 언어: 영어
Build a new design system (tokens, variants, theming). Use when "create a design system" or "component library from scratch". Drifted existing system → housekeep-design. Plan-only unification → plan-uiux-unification.
원문 언어: 영어
Apply cohesive visual themes to artifacts (slides, docs, landing pages). Provides 11 pre-set themes with colors/fonts. Use when user mentions "apply theme", "color palette", "brand colors", "styling slides", "presentation design", "visual identity", or wants…
원문 언어: 영어
Write developer docs: README content, API references, code comments, changelog entries. Use when "write docs", "document this API", "add code comments", or "explain for contributors". Visual README makeover → enhance-readme. Docs/code drift plan →…
원문 언어: 영어
Build landing pages, portfolios, and marketing sites that don't look AI-generated. Use when asked for "landing page", "portfolio", "marketing site", "anti-slop", "Awwwards-style", "premium frontend", or when design needs a strong point of view.
원문 언어: 영어
Scoped behavior-preserving refactor: map dependencies, change structure, run affected tests. Use when "refactor this", "reduce duplication", "improve readability". Dead code → plan-dead-code. Repo-wide anti-patterns → audit-code-quality. Bulk transform →…
원문 언어: 영어
Apply-now dead-code removal by category — one commit each, typecheck and tests between, bisect on red, then install the Knip ratchet so it cannot grow back. Use when "delete the dead code", "remove unused files", "wire up Knip". Audit first → plan-dead-code.…
원문 언어: 영어
Configuration-first dead-code audit — Knip baseline for unused files, exports and deps, plus duplication, debug residue, suppression debt, orphan assets, env and schema drift. Emits a ratchet plan; deletes nothing. Use when "find dead code", "is this code…
원문 언어: 영어
Apply-now consolidation of accreted CI gates, ratchets, and hooks into one aggregator required check. Use after audit-gate-logic, or when "clean up our CI checks", "we have three lint jobs", "make one quality gate". Audit-only → audit-gate-logic. Rule content…
원문 언어: 영어
Plan-only authenticity / AI-slop audit across prose, UI, code, and IA. Use when "looks like AI slop", "reads like ChatGPT", or "authenticity burndown". One-page UX apply → enhance-web-ux. Visual polish → enhance-web-ui.
원문 언어: 영어
Audit dependencies for hallucinated or slopsquatted packages, supply-chain risk, and licensing gaps, then a remediation plan. Use when "check my dependencies", "is this package real", "slopsquatting", "SBOM", or "did the AI hallucinate a package".
원문 언어: 영어
Set up and run mutation testing (StrykerJS / mutmut) to measure whether tests assert behavior, not just execute lines. Use when "add mutation testing", "are our tests real", "can our test suite be gamed", or after an agent bulk-generated tests. Coverage plan…
원문 언어: 영어
Apply repository maintenance: sync README, remove confirmed dead artifacts, and safely update dependencies. Use when "housekeep", "clean up repo", "update README", or "update dependencies". Unused files/exports/deps → plan-dead-code. Parked work →…
원문 언어: 영어
Analyse and shrink JavaScript bundle size for any web app. Use when asked to "reduce bundle size", "analyse bundle", "tree shaking", "lazy loading", "code splitting", "slow initial load", "large JS", "chunk size", "build performance", "LCP caused by JS", "why…
원문 언어: 영어
Detect and fix repo-wide anti-patterns and consistency drift (naming, organisation, repeated smells). Use when "code smell", "anti-pattern", "technical debt", or "standardize the codebase". This PR/diff review → audit-code-review.
원문 언어: 영어
README를 불러오지 못했습니다. 아래의 저장소 Skill 목록은 계속 이용할 수 있습니다.