์Šคํ‚ฌ screenshot-feature-extractor
๐Ÿ“ธ

screenshot-feature-extractor

์•ˆ์ „ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด๐ŸŒ ๋„คํŠธ์›Œํฌ ์ ‘๊ทผ

Extract features from UI screenshots

Analyzing screenshots manually to extract features and create task lists is time-consuming and error-prone. This multi-agent skill analyzes UI screenshots in parallel from three perspectives to identify features, interactions, and business logic, then generates a ready-to-use development task checklist.

์ง€์›: Claude Codex Code(CC)
๐Ÿ“Š 71 ์ ์ ˆํ•จ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"screenshot-feature-extractor" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Analyze this dashboard screenshot and create a feature task list

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • User Authentication module: Login screen, Remember me, Password reset
  • Dashboard Overview module: Stats cards, Real-time data, Date range picker
  • Navigation module: Sidebar menu, Breadcrumbs, User menu dropdown
  • Reporting module: Export PDF, Date filter, Graph visualization

"screenshot-feature-extractor" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Analyze these 5 screenshots from an e-commerce app

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Product Listing: Search bar, Category filters, Sort options, Product cards with images and prices
  • Product Detail: Image gallery, Add to cart, Size selector, Reviews section
  • Cart: Quantity controls, Total calculation, Promo code input, Checkout button
  • Checkout: Shipping form, Payment options, Order summary, Confirm purchase

"screenshot-feature-extractor" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Compare this competitor screenshot against our similar feature

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Competitor unique features: Dark mode, Voice search, Social sharing integration
  • Feature gaps: Missing in our product - Collaborative playlists, Offline mode
  • Priority recommendations: Implement voice search first, then dark mode, then social features

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „
v5 โ€ข 1/17/2026

This skill is pure documentation with no executable code. It only contains markdown prompts that orchestrate AI agents. No Ruby, shell, Python, JavaScript, or TypeScript files exist. All static findings are false positives from the scanner misinterpreting markdown backticks and JSON structures. The skill reads user-provided screenshots and writes output to predictable local paths.

3
์Šค์บ”๋œ ํŒŒ์ผ
413
๋ถ„์„๋œ ์ค„ ์ˆ˜
2
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
5
์ด ๊ฐ์‚ฌ ์ˆ˜

ํ’ˆ์งˆ ์ ์ˆ˜

41
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
22
์ปค๋ฎค๋‹ˆํ‹ฐ
100
๋ณด์•ˆ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Create requirements from mockups

Turn UI mockups or screenshots into feature specs and task lists for engineering teams

Understand feature scope quickly

Analyze competitor apps or reference designs to understand feature scope before implementation

Document existing products

Reverse-engineer existing products by analyzing their screens to document capabilities

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Basic screenshot analysis
Analyze this screenshot and extract all visible features, UI components, and interactions. Output file: docs/plans/YYYY-MM-DD-app-features.md
Multi-screen analysis
Analyze these screenshots from the same application. Identify all features across screens and create a consolidated task list. Deduplicate similar features.
Competitive analysis
Analyze these competitor screenshots. Identify unique features and gaps compared to our product. Create a feature comparison matrix with development task priorities.
Detailed feature breakdown
Perform deep analysis on this screenshot. Break down each feature into 3-5 granular subtasks focusing on user interactions and business logic. Output detailed development checklist.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Provide context about the product purpose and target users for better analysis
  • Use high-resolution screenshots with clear text for accurate feature detection
  • Include multiple related screens to capture navigation and state transitions

ํ”ผํ•˜๊ธฐ

  • Using low-resolution or blurry screenshots that obscure UI details
  • Analyzing screenshots without providing product context or user goals
  • Expecting implementation-level details like tech stack or database schema

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

What image formats are supported?
PNG, JPG, and common image formats are supported. Use high-resolution images for best results.
How many screenshots can I analyze at once?
No strict limit, but best results come from 3-10 related screens for comprehensive feature coverage.
Can I integrate this with my design tools?
Export screenshots from Figma, Sketch, or Adobe XD as PNG/JPG files before analysis.
Is my data sent to external servers?
No. All analysis happens locally through Claude Code. Screenshots are not uploaded to external services.
Why are my screenshots not detecting features accurately?
Ensure screenshots are high-resolution, well-lit, and include relevant context. Add product details in your prompt.
How does this compare to manual feature mapping?
This skill uses multiple AI agents in parallel for faster, more comprehensive analysis with consistent output format.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

notedit

๋ผ์ด์„ ์Šค

MIT

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“ references/

๐Ÿ“„ output-format.md

๐Ÿ“„ SKILL.md