Web Project Brainstorming
Overview
This skill provides a structured, masterclass-level framework for brainstorming web projects, web applications, or individual page designs at their inception. It guides developers and designers through scoping the core product concept, mapping user flows, defining visual styling aesthetics, selecting the technical stack, and planning for search engine optimization (SEO) and performance.
When to Use This Skill
- Use at the start of any new web development project or page redesign.
- Use when scoping feature sets, user roles, and interaction patterns for web applications.
- Use when establishing design systems, color tokens, and layout guidelines.
- Use when evaluating tech stacks (e.g., Next.js vs. Vanilla JS, CSS Grid vs. Tailwind).
How It Works
Execute web project brainstorming sequentially across six structured phases. Ask the user questions one phase at a time to maintain focus and ensure thorough alignment.
Phase 1: Core Concept & Scoping
Define the product's primary value proposition and scope:
- Target Audience: Who is using the website or application?
- Core Value: What problem does it solve for users?
- Key Features: What are the top 3–5 mandatory features?
Phase 2: User Experience (UX) & Information Architecture
Map how users navigate and interact:
- Page Hierarchy: What is the sitemap and page structure?
- User Journeys: What step-by-step flows do users take to complete key goals?
- Responsive Layout: Is the interface mobile-first, desktop-first, or balanced?
Phase 3: Visual Styling & Design System
Establish the visual guidelines and aesthetic parameters:
- Design Aesthetic: Modern, minimalist, brutalist, glassmorphism, or luxury?
- Color Palette: What are the primary, secondary, and accent colors? (Prefer tailorable HSL/RGB models over static color keywords).
- Typography: Which Google Fonts or system fonts fit the theme? (e.g., Inter, Outfit, Syne).
- Interactive States: How do hovers, clicks, transitions, and loading states behave?
Phase 4: Technical Stack & Architecture
Select the technologies and integration systems:
- Frontend Framework: React, Next.js, Vite, Astro, Svelte, or Vanilla HTML/JS?
- Styling Method: Vanilla CSS, Tailwind CSS, or CSS Modules?
- Data & Backend: REST API, GraphQL, tRPC, Firebase, Supabase, or SQLite?
- State Management: Zustand, Context API, Redux, or local React state?
Phase 5: SEO, Accessibility (A11y), and Performance
Plan for discoverability and fast loading times:
- SEO Elements: Title tag structure, meta descriptions, and semantic HTML tag hierarchy.
- Accessibility: ARIA labels, semantic tags, keyboard navigation, and color contrast.
- Performance: Preloading assets, lazy loading images, server-side rendering (SSR), and CDN delivery.
Phase 6: MVP Scope & Project Phases
Break the work down into manageable increments:
- Phase 1 (MVP): The absolute minimum viable product needed to deploy.
- Phase 2 (Enhancements): Nice-to-have features, micro-animations, and advanced integrations.
Examples
Interactive Questionnaire Prompt Template
Use this prompt layout when initiating a brainstorming session with a client or team member:
👋 Let's brainstorm your new web project! We will walk through 6 quick phases.
---
### Phase 1: Core Concept & Scoping
1. What is the main title or working name of this project?
2. Who are the primary target users (e.g., tech-savvy professionals, shoppers, children)?
3. What are the 3 core tasks a user must be able to perform?
---
Brainstorming Output Document Template
Once all phases are complete, generate a markdown blueprint for the project using this template:
# Project Blueprint: [Project Name]
## 1. Product Concept
- **Value Proposition**: [Summary]
- **Key Features**:
1. [Feature 1]
2. [Feature 2]
## 2. Information Architecture & UX
- **Pages**: `/index.html`, `/dashboard.html`
- **Primary User Flow**: User signs up -> completes onboarding -> views dashboard.
## 3. Styling & Aesthetics
- **Aesthetic**: Sleek Glassmorphism Dark Mode
- **Color Tokens**:
- Background: `hsl(222, 47%, 11%)`
- Accent/Primary: `hsl(217, 91%, 60%)`
- **Typography**: Inter (Body), Outfit (Headings)
## 4. Technical Architecture
- **Framework**: Next.js (App Router)
- **Styling**: Tailwind CSS
- **Database**: PostgreSQL with Prisma ORM
## 5. SEO & Performance
- **Primary Title**: "[Brand] | [Tagline]"
- **Performance Strategy**: Dynamic image optimization, caching pages via Cloudflare.
## 6. MVP vs Phase 2 Roadmap
- **MVP**: Authentication + core dashboard view.
- **Phase 2**: Real-time notifications and PDF reporting.
Best Practices
- ✅ Ask questions incrementally—never dump all six phases in a single response to avoid cognitive overload.
- ✅ Propose logical defaults (e.g., recommending responsive Tailwind/CSS Grid and standard semantic HTML) if the user is unsure.
- ✅ Ensure semantic HTML layout hierarchy (one
<h1> per page, sequential <section>, <article>, <header>, <footer> elements) is planned from the start.
- ✅ Document explicit non-goals to prevent feature creep.
Limitations
- This skill focuses on conceptual mapping, architecture, and feature planning; it does not replace the writing of implementation code or system configuration.
- Brainstorming outcomes should be treated as flexible blueprints and refined as technical constraints are discovered during development.
Security & Safety Notes
- During Phase 4 (Architecture), flag any security requirements (e.g., SSL certificates, CORS policies, secure authentication storage, environment variables protection) early.
- Do not store actual API tokens, passwords, or credentials in design or blueprint documents.
Common Pitfalls
- Problem: Scope Creep (the project expands too quickly before building an MVP).
Solution: Enforce Phase 6 strictly. Push nice-to-have features into Phase 2.
- Problem: Ignoring mobile design until late in development.
Solution: Brainstorm responsive patterns in Phase 2 before deciding on layout style in Phase 3.
Related Skills
@writing-plans - Organizing structural step-by-step engineering plans.
@architecture-decision-records - Documenting architectural decisions.
@ux-flow - Designing deep user experience flows and interaction details.
Source: sickn33/agentic-awesome-skills → skills/web-project-brainstorming/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/web-project-brainstorming/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/web-project-brainstorming/SKILL.md
1---
2name: web-project-brainstorming
3description: "Masterclass framework for brainstorming web development projects and page designs. Outlines structural phases for concept, UX flow, styling aesthetics, technical architecture, and SEO."
4allowed-tools: "[claude, cursor, gemini]"
5category: productivity-and-workflow
6source_repo: sickn33/agentic-awesome-skills
7source_path: "skills/web-project-brainstorming/SKILL.md"
8source_url: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/web-project-brainstorming/SKILL.md
9metadata:
10 source: https://skillmd.com/skills/sickn33/web-project-brainstorming
11---
12
13
14# Web Project Brainstorming
15
16## Overview
17
18This skill provides a structured, masterclass-level framework for brainstorming web projects, web applications, or individual page designs at their inception. It guides developers and designers through scoping the core product concept, mapping user flows, defining visual styling aesthetics, selecting the technical stack, and planning for search engine optimization (SEO) and performance.
19
20## When to Use This Skill
21
22- Use at the start of any new web development project or page redesign.
23- Use when scoping feature sets, user roles, and interaction patterns for web applications.
24- Use when establishing design systems, color tokens, and layout guidelines.
25- Use when evaluating tech stacks (e.g., Next.js vs. Vanilla JS, CSS Grid vs. Tailwind).
26
27## How It Works
28
29Execute web project brainstorming sequentially across six structured phases. Ask the user questions one phase at a time to maintain focus and ensure thorough alignment.
30
31### Phase 1: Core Concept & Scoping
32Define the product's primary value proposition and scope:
33- **Target Audience**: Who is using the website or application?
34- **Core Value**: What problem does it solve for users?
35- **Key Features**: What are the top 3–5 mandatory features?
36
37### Phase 2: User Experience (UX) & Information Architecture
38Map how users navigate and interact:
39- **Page Hierarchy**: What is the sitemap and page structure?
40- **User Journeys**: What step-by-step flows do users take to complete key goals?
41- **Responsive Layout**: Is the interface mobile-first, desktop-first, or balanced?
42
43### Phase 3: Visual Styling & Design System
44Establish the visual guidelines and aesthetic parameters:
45- **Design Aesthetic**: Modern, minimalist, brutalist, glassmorphism, or luxury?
46- **Color Palette**: What are the primary, secondary, and accent colors? (Prefer tailorable HSL/RGB models over static color keywords).
47- **Typography**: Which Google Fonts or system fonts fit the theme? (e.g., Inter, Outfit, Syne).
48- **Interactive States**: How do hovers, clicks, transitions, and loading states behave?
49
50### Phase 4: Technical Stack & Architecture
51Select the technologies and integration systems:
52- **Frontend Framework**: React, Next.js, Vite, Astro, Svelte, or Vanilla HTML/JS?
53- **Styling Method**: Vanilla CSS, Tailwind CSS, or CSS Modules?
54- **Data & Backend**: REST API, GraphQL, tRPC, Firebase, Supabase, or SQLite?
55- **State Management**: Zustand, Context API, Redux, or local React state?
56
57### Phase 5: SEO, Accessibility (A11y), and Performance
58Plan for discoverability and fast loading times:
59- **SEO Elements**: Title tag structure, meta descriptions, and semantic HTML tag hierarchy.
60- **Accessibility**: ARIA labels, semantic tags, keyboard navigation, and color contrast.
61- **Performance**: Preloading assets, lazy loading images, server-side rendering (SSR), and CDN delivery.
62
63### Phase 6: MVP Scope & Project Phases
64Break the work down into manageable increments:
65- **Phase 1 (MVP)**: The absolute minimum viable product needed to deploy.
66- **Phase 2 (Enhancements)**: Nice-to-have features, micro-animations, and advanced integrations.
67
68## Examples
69
70### Interactive Questionnaire Prompt Template
71Use this prompt layout when initiating a brainstorming session with a client or team member:
72
73```markdown
74👋 Let's brainstorm your new web project! We will walk through 6 quick phases.
75
76---
77### Phase 1: Core Concept & Scoping
781. What is the main title or working name of this project?
792. Who are the primary target users (e.g., tech-savvy professionals, shoppers, children)?
803. What are the 3 core tasks a user must be able to perform?
81---
82```
83
84### Brainstorming Output Document Template
85Once all phases are complete, generate a markdown blueprint for the project using this template:
86
87```markdown
88# Project Blueprint: [Project Name]
89
90## 1. Product Concept
91- **Value Proposition**: [Summary]
92- **Key Features**:
93 1. [Feature 1]
94 2. [Feature 2]
95
96## 2. Information Architecture & UX
97- **Pages**: `/index.html`, `/dashboard.html`
98- **Primary User Flow**: User signs up -> completes onboarding -> views dashboard.
99
100## 3. Styling & Aesthetics
101- **Aesthetic**: Sleek Glassmorphism Dark Mode
102- **Color Tokens**:
103 - Background: `hsl(222, 47%, 11%)`
104 - Accent/Primary: `hsl(217, 91%, 60%)`
105- **Typography**: Inter (Body), Outfit (Headings)
106
107## 4. Technical Architecture
108- **Framework**: Next.js (App Router)
109- **Styling**: Tailwind CSS
110- **Database**: PostgreSQL with Prisma ORM
111
112## 5. SEO & Performance
113- **Primary Title**: "[Brand] | [Tagline]"
114- **Performance Strategy**: Dynamic image optimization, caching pages via Cloudflare.
115
116## 6. MVP vs Phase 2 Roadmap
117- **MVP**: Authentication + core dashboard view.
118- **Phase 2**: Real-time notifications and PDF reporting.
119```
120
121## Best Practices
122
123- ✅ Ask questions incrementally—never dump all six phases in a single response to avoid cognitive overload.
124- ✅ Propose logical defaults (e.g., recommending responsive Tailwind/CSS Grid and standard semantic HTML) if the user is unsure.
125- ✅ Ensure semantic HTML layout hierarchy (one `<h1>` per page, sequential `<section>`, `<article>`, `<header>`, `<footer>` elements) is planned from the start.
126- ✅ Document explicit non-goals to prevent feature creep.
127
128## Limitations
129
130- This skill focuses on conceptual mapping, architecture, and feature planning; it does not replace the writing of implementation code or system configuration.
131- Brainstorming outcomes should be treated as flexible blueprints and refined as technical constraints are discovered during development.
132
133## Security & Safety Notes
134
135- During Phase 4 (Architecture), flag any security requirements (e.g., SSL certificates, CORS policies, secure authentication storage, environment variables protection) early.
136- Do not store actual API tokens, passwords, or credentials in design or blueprint documents.
137
138## Common Pitfalls
139
140- **Problem**: Scope Creep (the project expands too quickly before building an MVP).
141 **Solution**: Enforce Phase 6 strictly. Push nice-to-have features into Phase 2.
142- **Problem**: Ignoring mobile design until late in development.
143 **Solution**: Brainstorm responsive patterns in Phase 2 before deciding on layout style in Phase 3.
144
145## Related Skills
146
147- `@writing-plans` - Organizing structural step-by-step engineering plans.
148- `@architecture-decision-records` - Documenting architectural decisions.
149- `@ux-flow` - Designing deep user experience flows and interaction details.
150
151---
152
153**Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/web-project-brainstorming/SKILL.md`
154
155**Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/web-project-brainstorming/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/web-project-brainstorming/SKILL.md`