'prototype' 검색 결과

[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution.

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

Turns an idea into a working, user-testable prototype with AI builders (Lovable, v0, Bolt, Replit, Cursor, Claude Code) and gets you unstuck when the tool breaks. Produces a Prototype Brief with a build-prompt pack, a debugging log and a user-test plan. Use for 'vibe coding', 'build a prototype', 'prototype this feature', 'Lovable prompt', 'my AI builder is stuck', 'prototype instead of a PRD', or 'demo for users'. Draws on 44 Lenny's Podcast guests incl. Lazar Jovanovic, Zevi Arnovitz and Guillermo Rauch.

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

Convert per-page styled HTML prototypes (stardust under stardust/prototypes/**, or claude-design / Mobirise / Relume / Lovable / v0 / Figma-derived pages, or JSX prototypes pre-rendered to HTML, often under samples/) into Edge Delivery Services (EDS / AEM) blocks and content pages, then deploy via DA. Each prototype section becomes one EDS block; the prototype's per-section CSS becomes that block's CSS scoped under the block class. Use when the user wants to lift styled per-page HTML prototypes into a working EDS site under blocks/ and content/.

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

Build a quick, disposable game prototype in HTML, a game engine, or on paper to test one core mechanic. Use playtest findings to decide whether to continue, change direction, stop, or leave the idea unassessed.

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

• Test whether a core game mechanic is fun
• Compare several variations of a game concept
• Explore a mechanic change during production

Deploy a runnable prototype to the hosting service you choose, such as Sites or Vercel. Use the available deployment tool, return a working shareable URL, and identify any remaining manual steps.

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

• Publishing a prototype for others to try
• Deploying a prototype to Sites
• Deploying a prototype to Vercel

Build a self-contained local prototype at .turbo/prototypes/<slug>.html, drive it, and hand it to the user to settle unknowns that prose cannot answer. Use when the user asks to "prototype this", "build a prototype", "mock this up", "show me what it would look like", "let me try the interaction first", or when a decision waits on seeing a surface or using it firsthand.

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

Builds new UI prototypes and makes targeted changes to existing prototypes using consumer-owned context. Use when asked to build a prototype, mock up a UI, or add, change, refine or recreate part of an existing prototype. Do not use for unrelated tasks, routine commands, Git lifecycle actions, acknowledgements or infrastructure work.

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

Build a throwaway prototype to answer a design question, as UI variations or a state-model walkthrough. Use when the user types /prototype, wants to sanity-check whether a state model or logic feels right, wants to explore what a UI should look like, or as the prototype step of the web design flow with brainstorm or grill before the final plan goes to plan-canvas (annotate the running prototype with the plan-canvas annotation tool).

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

Prototype a single-page website for SaaS, documentation, or knowledge products. Use warm off-white backgrounds, serif headings, fine dividers, generous spacing, and subtle motion to create a restrained layout with features and a signup or pricing section.

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

• Prototype a SaaS marketing page
• Explore a documentation page design
• Build an introduction page for a knowledge product

Create soft, polished web prototypes with silver or cream backgrounds, nested card borders, rounded surfaces, and carefully specified motion. The skill defines page sections, buttons, navigation, and mobile layouts for a consistent visual style.

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

• Prototyping a calm SaaS website
• Creating a soft visual style for a consumer product site
• Building a feature page with cards and prominent action buttons

Create a functional application prototype from an initial idea. The workflow covers requirements, technology choices, plan approval, project setup, implementation, visual assets where needed, build verification, and instructions for starting the result.

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

• Building a website prototype from an idea
• Creating an initial mobile or desktop application
• Developing a playable 2D or 3D game prototype

Turn existing game code or prototypes into missing design, architecture, or concept documents. Extract implemented rules, formulas, and technical choices, ask about their intended purpose, and clearly separate observed behavior from unconfirmed interpretations.

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

• Documenting a feature built without a design document
• Understanding an inherited codebase with missing documentation
• Turning a gameplay prototype into a concept document

Build a disposable prototype to test how a product should work, feel, or look before committing to an approach. Let the user experience it, record their choices, and carry those decisions into requirements or further planning.

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

• Trying a navigation flow before committing to it
• Judging layout density and color choices
• Resolving design questions that sketches cannot answer

Build a runnable prototype from a plain feature request, then add capabilities one step at a time. The skill records consequential assumptions before coding, checks each step, and reports remaining placeholders, deferred work, and review limits.

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

• Building a runnable prototype from a feature description
• Extending a prototype through checked feature steps
• Recording decisions where requirements are unclear

Turn a feature request into a working prototype, starting with a minimal path from input to output and adding features through individual checks. Record consequential assumptions before coding, then use a separate model to find decisions missing from that record.

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

• Building a working prototype from a feature description
• Extending a prototype one checked feature at a time
• Recording assumptions made during implementation

Compares a prototype’s rendered screens with its source design to find differences in typography, spacing, colors, images, and text. Produces prioritized fixes and records visual evidence from follow-up checks before handoff.

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

• Check a prototype against its Figma source before handoff
• Compare an image-based build with the original visual
• Review visual differences across screen sizes and states

Hunt API security misconfiguration — mass assignment, prototype pollution, HTTP verb tampering. Mass assignment: send {is_admin:true, role:admin, verified:true} on profile/account/reset endpoints — server blindly applies. JWT signature/crypto forging (alg:none, key confusion, kid/jku) is owned by hunt-jwt-crypto; this skill covers only non-crypto JWT handling. Prototype pollution: __proto__ injection in JSON merge / Object.assign / lodash _.merge → polluted prototype reaches sink (RCE in Node, XSS in browser). HTTP verb: GET-bypass-CSRF, X-HTTP-Method-Override, TRACE enabled. Detection: API responses with extra fields, JWTs in headers (decode at jwt.io). CORS misconfiguration (reflect-any-origin, null origin, subdomain-regex bypass, postMessage) is owned by hunt-cors. Use when hunting API misconfigs, mass-assignment, prototype pollution (JWT crypto → hunt-jwt-crypto).

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

Direct-invocation specialist for polished, responsive, self-contained HTML mockups and interactive prototypes grounded in the user's conversation, product context, and design language. Use when the user explicitly invokes html-prototype or the broad html skill routes a mockup or prototype request here. Do not activate independently from a general request. Treat a mockup as a noninteractive fidelity mode within this skill, not as a separate skill.

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

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

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

Generate visual prototype prompts from SCR- entries for Google Stitch (or equivalent UI generation tool). Triggers on: 'make a prototype', 'visualize screens', 'generate Stitch prompt', 'I need a visual demo', 'prototype the workflow', 'show me what this looks like', 'get this to a demo', 'visual gate'. Consumes SCR- (Screen Flow Definition), PER- (Personas), UJ- (User Journeys), DES- (Design Components). Outputs Stitch prompt blocks per SCR- entry + Feedback Capture Template. No new SoT IDs created — this skill makes existing SCR- entries visual and routes feedback back to them.

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

Hi-fi interactive HTML prototype — single-file, double-click-to-open, Playwright-verified. Use when asked to "make it clickable", "build a prototype", "hi-fi mockup", "interactive demo", "iOS prototype", "app mockup", "ui demo", or "prototype this". Goes beyond wireframes into visually finished, state-driven HTML with device frames and real images. Not production code — a design artifact for testing flows and pitching ideas.

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

Identify and exploit Prototype Pollution vulnerabilities in JavaScript/Node.js applications. This skill covers the progression from polluting `Object.prototype` to identifying functional gadgets (like `child_process.spawn`) to achieve Remote Code Execution (RCE).

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

Identify and exploit Prototype Pollution vulnerabilities in JavaScript applications to achieve client-side Cross-Site Scripting (XSS), bypass authentication, or execute Remote Code Execution (RCE) on Node.js servers by manipulating the core Object prototype.

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

Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to see multiple visual approaches to a component. Also trigger when user says "show me different ways to build...", "explore different designs for...", or wants rapid visual exploration of a UI idea — even without saying "prototype" explicitly.

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