brainstorming

Guide React Native or Expo feature design through structured dialogue and documented specs.

28|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/bidah/react-native-hifi --skill brainstorming-bidah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/bidah/react-native-hifi/tree/main/skills/brainstorming
Command: npx skills add https://github.com/bidah/react-native-hifi --skill brainstorming-bidah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature coding by forcing a design-first exploration of intent, constraints, and success criteria before any implementation.

Core Features & Use Cases

  • Structured discovery: Review files, documentation, and recent changes to understand the current project context before proceeding.
  • Clarifying dialogue: Ask one question at a time, present 2-3 approaches with trade-offs, and keep the user in the loop until a design is approved.
  • Design documentation: Draft, review, and commit a spec under docs/react-native-hifi/specs/, then ask the user to review it before invoking implementation planning.
  • Use Case: When a user asks for a new React Native or Expo screen, run through this checklist to freeze scope, design, and approval so implementation follows with confidence.

Quick Start

Ask brainstorming to explore the context, gather clarifying questions, and present a design for approval before any code is written.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a React Native feature before writing any code?▼

Design-first planning for React Native features involves structured context discovery, clarifying dialogue to understand intent, and documenting a spec with inline reviews to secure explicit user approval before implementation begins.

What is the best way to document a design spec for an Expo app feature?▼

The best way to document a design spec for an Expo app is to draft, review, and commit the specification under a dedicated directory like docs/react-native-specs, ensuring it captures visual direction and constraints before any implementation planning is invoked.

Can I use a structured discovery process to validate project intent for a new screen?▼

Yes, you can validate project intent for a new screen by applying a structured discovery process that reviews existing files and documentation, asks clarifying questions one at a time, and keeps you in the loop until the design is approved.

Does design-first planning work for early-stage React Native feature requests?▼

Yes, design-first planning works specifically for early-stage React Native or Expo feature requests where clarifying project intent, constraints, and visual direction through dialogue is required before proceeding to implementation.

When do I need to present approach trade-offs during the design validation phase?▼

You need to present approach trade-offs during the design validation phase after reviewing the project context, offering 2-3 distinct approaches with their respective trade-offs to the user for review before drafting the final design specification.