Skip to content

GktuOktay/autonomous-agency / .agents/skills/02_specialists/product_and_ba/prototype

Rapid Prototyping

Verified

Hızlı prototipleme, MVP geliştirme ve farklı tasarım aslına uygunluk seviyelerinde doğru aracı seçme stratejileri.

Rapid Prototyping and MVP Development

Prototyping is the process of creating a preliminary model of an application to validate concepts, flows, and technical feasibility before committing to full-scale development.

1. Choosing the Right Fidelity

Prototypes range from low to high fidelity. Choosing the right level is essential for efficiency.

Fidelity LevelFormatPurposeSpeedTools
Low (Lo-Fi)Paper Sketches, WhiteboardBrainstorming, defining core layout, early validation of user flows.Very FastPen & Paper, Excalidraw, Balsamiq
Medium (Mid-Fi)Wireframes, Clickable ScreensDefining structure, navigation, and content hierarchy without visual distraction.FastFigma, Sketch, Whimsical
High (Hi-Fi)Interactive MockupsFinalizing visual design (colors, typography), micro-interactions, realistic user testing.SlowFigma, Framer, Protopie
Coded (Code-Fi)Functional MVP (HTML/CSS/JS)Validating technical feasibility, testing with real data, actual user interaction on devices.Very SlowCodeSandbox, Vercel, HTML/CSS, Tailwind

2. Tool Selection

  • Figma: The industry standard for Mid-Fi and Hi-Fi prototyping. Excellent for collaboration, creating clickable flows, and sharing with stakeholders.
  • Code-based Prototyping: Tools like Framer (which bridges design and code) or jumping straight into React/Tailwind. Best when interactions are too complex for Figma or when you intend to iterate the prototype directly into production.
  • No-Code/Low-Code: Tools like Webflow, Bubble, or Retool. Excellent for functional MVPs without requiring a full engineering team.

3. Speed vs. Quality Tradeoffs

A prototype is a disposable artifact used for learning, not a production application.

  • Accept Technical Debt: Hardcode data, skip error handling, ignore edge cases.
  • Fake It 'Til You Make It: Use "Wizard of Oz" techniques (humans manually doing tasks behind the scenes) instead of building complex backend logic.
  • Focus on the Core Loop: Only build the features necessary to test the specific hypothesis.

4. Prototype Scope Definition

Before building, clearly define the scope:

  1. Hypothesis: What are we trying to learn? (e.g., "Will users understand how to use the new filtering system?")
  2. Audience: Who will test this?
  3. Tasks: What specific actions do we want users to attempt?
  4. Metrics: How will we measure success? (Task completion rate, time on task, qualitative feedback).

5. User Testing with Prototypes

  • Recruit Representative Users: Test with people who match your target demographic.
  • Task-Based Testing: Give users specific scenarios ("Find a red shirt in size medium and add it to your cart") rather than asking "What do you think of this design?"
  • Think Aloud Protocol: Ask users to vocalize their thoughts, confusion, and expectations as they interact with the prototype.
  • Do Not Defend the Design: If a user struggles, it is a flaw in the design, not the user. Observe and learn.

6. Iterating Based on Feedback

  • Synthesize Data: Look for patterns in user struggles. If 3 out of 5 users fail to find the checkout button, it needs redesigning.
  • Rapid Iteration: Make changes immediately between testing sessions if a critical flaw is discovered.
  • Kill Darlings: Be prepared to throw away designs that test poorly, regardless of how much time was spent on them.

7. Converting Prototype to Production Code

  • Never Use Prototype Code Directly: If you built a code prototype fast and dirty, do not deploy it to production. Rewrite it with proper architecture, testing, and security.
  • Design Handoff: Use Figma's Dev Mode or Zeplin to extract CSS values, assets, and spacing.
  • Component Driven: Identify repeating UI patterns in the prototype and build them as reusable React/Vue components in the production codebase.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall