226건 · 관련도순
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value target. Applied by migration-import-engineer and architect/pm so onboarding is designed as a funnel, not an afterthought. Our whole wedge is "low switching cost"; this skill makes that real on day one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Domain knowledge for SMB industry products — the vocabulary, the entities a spec must model, the incumbent to route around, and what a naive build gets wrong — one file per industry, plus local SEO and money-on-a-phone. Read the one file that applies before speccing or building the product.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Download, transcribe, analyze, and clip video content — vertical shorts, captions, thumbnails
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzing pre-change impact across vertical (dependency chains, files) and horizontal (pattern consistency, naming) dimensions. Use to estimate blast radius before a refactor. No code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply evidence-first engineering discipline to any agent-built software project: fact discovery before action, evidence-calibrated status reporting, explicit change boundaries and stage gates, controlled confirmation for risky or external actions, sensitive-information redaction for anything shared publicly, and resumable continuity after interruptions. Use when users ask an agent to take over an existing codebase, deliver a feature across stages, verify whether work is actually complete, judge release readiness, or keep conclusions honest about what is proven versus assumed. This foundation skill is domain-neutral; vertical suites (for example mini-program engineering) build on it by adding domain facts and platform rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a learning task where mixed-age students work together with mutual benefit for all age groups. Use when planning cross-age tutoring, vertical grouping, or multi-year group activities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Make a papercut reel, video or explainer end to end. Short vertical (9:16) cut-paper explainers from a link (repo, product page, announcement), idea to mp4. Also routes partial asks to the stage skills and hands out the style prompt for other tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide creation of new industry use cases for the Adobe Experience Platform blueprints repository. Use this skill when adding a new use case to an industry vertical (retail, automotive, healthcare, financial services, insurance, media & entertainment, telecommunications, travel & hospitality, B2B), when the user wants to add business scenarios to industry pages, or when updating the use case catalog. Handles the full workflow: gathering use case details, assessing maturity level, generating content, updating the industry overview page and use case catalog, and invoking the use-case-icon-generator skill for icon creation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Agent Media when an agent needs to create captioned vertical UGC videos, narrated b-roll overlays, reusable characters, images, and voice through a hosted MCP server and companion skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hunt Insecure Direct Object Reference (IDOR) — test horizontal and vertical privilege escalation across user IDs, org IDs, tenant boundaries, and unguessable identifiers. Use when the user has an API endpoint with an identifier in the path/body that may be tested for unauthorized cross-user access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement cloud cost optimization strategies for Kubernetes workloads using tools like Kubecost for visibility, right-sizing recommendations, horizontal and vertical pod autoscaling, spot/preemptible instances, and resource quotas. Covers cost allocation, showback reporting, and continuous optimization practices. Use when cloud costs are growing without proportional business value, when resource requests are misaligned with actual usage, when manual scaling leads to over-provisioning, or when implementing showback and chargeback for internal cost accountability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Local SEO analysis covering Google Business Profile optimization, NAP consistency, citation health, review signals, local schema markup, location page quality, multi-location SEO, and industry-specific recommendations. Detects business type (brick-and-mortar, SAB, hybrid) and industry vertical (restaurant, healthcare, legal, home services, real estate, automotive). Use when user says "local SEO", "Google Business Profile", "GBP", "map pack", "local pack", "citations", "NAP consistency", "local rankings", "service area", "multi-location", or "local search".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "make a Spotify Wrapped style video", "build a year in review / year-in-review video", "create a personalized data video", "generate a recap video", "build a wrapped video generator", "turn a data table into shareable videos", or "make per-user stat videos". Covers the data row → one shareable video pattern, the Wrapped scene grammar (big-number reveals, top-X lists, superlatives), animated data counters, vertical 9:16 framing, and batch-rendering many personalized videos from one template.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build MindNode-inspired mind mapping interfaces — 8 node shapes, 27+ themes, layout algorithms (horizontal, vertical, radial with D3), keyboard shortcuts, focus mode, dual view. React + xyflow/react v12 + Zustand + Tailwind. Triggers on mind map, visual thinking tool, node-based diagram, brainstorm canvas, MindNode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Render a deterministic 15-second vertical promo video from real Simulator screenshots with a three-beat viewer challenge and no Remotion initialization. Use in a twelve-minute parallel launch lane, as a reliable fallback to a richer Claude Design animation, or whenever ffmpeg and ImageMagick are available.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create branded 试界TryWorld AI-knowledge videos in the fixed "Paper Algorithm" (纸上算法) style with HyperFrames. Input is a Chinese voiceover script and optional images; output is a 16:9 horizontal video with Azure YunxiNeural (真·云希) voiceover, word-synced captions, ink/paper animations and unified transitions, an always-visible anti-counterfeit red seal, plus horizontal (4:3) and vertical (3:4) cover images and platform-optimized titles for Bilibili/Douyin/Xiaohongshu. Brand values are theme-driven (themes/paper-algorithm.json by default; custom brand themes supported — see references/theme-guide.md). Use when the user provides an AI 科普/教程/内容解读/知识分享 script and wants a TryWorld/试界 branded video, asks for the 纸上算法/Paper Algorithm style, wants a consistent script-to-video pipeline with covers and titles, or wants this pipeline with their own brand theme.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Slice a NowStack Mobile app's .agents/plan/PRD.md + .agents/plan/ARCHITECTURE.md into well-scoped, implementable task files under .agents/plan/tasks/, each an autonomous 1–3h vertical slice (Convex schema/function → Expo screen → wiring) with success criteria, dependencies, and verification commands. Use for "create tasks", "ns tasks", "break this into tickets", or as the third planning step after ns-prd and ns-architecture. Both docs must exist first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restate requirements, assess risks, and create a step-by-step implementation plan with Vertical Slices (Tracer Bullets).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.