skills/emz1998/brainstorming-features/SKILL.md
Facilitates creative ideation sessions for mobile and web app features, generating structured ideas with user stories, technical considerations, and implementation suggestions. Use when planning new features, exploring product direction, generating app ideas, feature discovery, product brainstorming, or when user mentions 'brainstorm', 'ideate', 'app ideas', or 'feature suggestions'.
npx skillsauth add aiskillstore/marketplace brainstorming-featuresInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps generate, explore, and structure feature ideas for mobile and web applications through systematic ideation workflows. It produces actionable, well-organized feature concepts with technical context and user value.
Before generating ideas, understand:
Project Context:
Brainstorming Scope:
Method A - Problem-First:
Method B - Opportunity-First:
Method C - Competitive Analysis:
Method D - User Journey Mapping:
For each feature idea, provide:
## Feature: [Feature Name]
**One-line description:**
[Brief, compelling description in 10-15 words]
**Problem it solves:**
[User pain point or opportunity addressed]
**Target users:**
[Primary and secondary user personas]
**User story:**
As a [user type], I want to [action] so that [benefit].
**Key capabilities:**
- Capability 1
- Capability 2
- Capability 3
**Technical considerations:**
- Technology/library suggestions
- Integration points
- Data requirements
- Potential challenges
**Implementation complexity:**
[Low / Medium / High] - [Brief justification]
**Expected impact:**
[User value and business value]
**Success metrics:**
- Metric 1 (e.g., engagement increase)
- Metric 2 (e.g., task completion rate)
After initial generation, refine ideas by:
Feasibility Check:
Value Assessment:
Prioritization Matrix:
High Value, Low Effort → Do First (Quick Wins)
High Value, High Effort → Strategic Investments
Low Value, Low Effort → Consider Later
Low Value, High Effort → Avoid
Format 1 - Feature Brief (Detailed): Use the full template above for 3-5 top features
Format 2 - Feature List (Concise):
1. **[Feature Name]** - [One-line description] [Complexity: Low/Med/High]
2. **[Feature Name]** - [One-line description] [Complexity: Low/Med/High]
...
Format 3 - Feature Roadmap: Organize by phases or sprints:
### Phase 1 - Foundation (Sprint 1-2)
- Feature A (enables core workflow)
- Feature B (critical user need)
### Phase 2 - Enhancement (Sprint 3-4)
- Feature C (improves experience)
- Feature D (adds value)
### Phase 3 - Advanced (Sprint 5+)
- Feature E (differentiator)
- Feature F (scale optimization)
Context: React Native note-taking app for nursing students
Brainstorm Request: "Generate 5 feature ideas to improve study efficiency"
Output:
## Feature: AI-Powered Flashcard Generation
**One-line description:**
Automatically create study flashcards from notes using AI term extraction
**Problem it solves:**
Students spend hours manually creating flashcards instead of studying
**Target users:**
Nursing students preparing for exams and clinical rotations
**User story:**
As a nursing student, I want my notes automatically converted to flashcards so that I can focus on studying instead of card creation.
**Key capabilities:**
- Auto-detect medical terms and concepts
- Generate question-answer pairs from context
- Spaced repetition scheduling
- Manual edit and refinement
**Technical considerations:**
- OpenAI API for term extraction
- IndexedDB/Dexie for local flashcard storage
- Background processing for large notes
- Offline-first sync with Firestore
**Implementation complexity:**
Medium - Requires AI integration and smart parsing logic, but leverages existing note structure
**Expected impact:**
- 70% reduction in flashcard creation time
- Increased study time availability
- Higher exam preparation quality
**Success metrics:**
- Flashcards generated per note
- User edits to auto-generated cards (lower = better accuracy)
- Study session frequency increase
Context: Next.js e-commerce platform, early stage
Brainstorm Request: "Brainstorm checkout flow improvements"
Output (Concise Format):
1. **One-Click Reorder** - Save previous orders as templates for instant reordering [Complexity: Low]
2. **Smart Address Autocomplete** - Google Places API integration for accurate shipping addresses [Complexity: Low]
3. **Guest Checkout Express** - No account required, optional account creation post-purchase [Complexity: Medium]
4. **Cart Recovery Emails** - Automated emails for abandoned carts with incentives [Complexity: Medium]
5. **Buy Now Pay Later Integration** - Klarna/Afterpay integration for flexible payments [Complexity: High]
6. **Multi-Item Gift Options** - Individual gift wrapping and messages per item [Complexity: Medium]
7. **Saved Payment Methods** - Tokenized card storage with Stripe for returning customers [Complexity: Medium]
Context: Exploring gamification features
Brainstorm Request: "Generate gamification ideas for workout motivation"
Output (Feature Brief):
## Feature: Achievement Streak Tracker
**One-line description:**
Visual streak counter with milestone rewards for consecutive workout days
**Problem it solves:**
Users lack motivation to maintain consistent workout routines
**Target users:**
Casual fitness enthusiasts seeking habit formation
**User story:**
As a user, I want to see my workout streak and earn rewards so that I stay motivated to exercise daily.
**Key capabilities:**
- Daily streak counter with flame icon visualization
- Milestone badges (7-day, 30-day, 100-day streaks)
- Streak freeze option (1 per week)
- Social sharing of achievements
- Push notifications for streak risk
**Technical considerations:**
- Local notification scheduling (Expo Notifications)
- Streak calculation with timezone handling
- Badge icon assets and animations
- Firebase Cloud Functions for streak validation
- Social sharing via React Native Share
**Implementation complexity:**
Low - Simple date tracking logic with notification system
**Expected impact:**
- 40% increase in daily active users
- 25% improvement in 30-day retention
- Higher social engagement and viral growth
**Success metrics:**
- % users with active streaks
- Average streak length
- Notification engagement rate
- Social shares per achievement
Respond to these phrases by activating this skill:
After initial brainstorming:
For further refinement, consider:
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.