initial commit
This commit is contained in:
@@ -0,0 +1,117 @@
|
||||
---
|
||||
name: 'step-01-load-context'
|
||||
description: 'Load everything needed for full page design compositions from specs, design system, and wireframes'
|
||||
nextStepFile: './step-02-inventory.md'
|
||||
---
|
||||
|
||||
# Step 1: Load Context
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Load everything needed for full page design compositions — page specifications, complete design system, visual direction, and any approved wireframes to build upon.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner loading page design context
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring systematic context loading, user brings project specifics
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on loading and summarizing page design context
|
||||
- 🚫 FORBIDDEN to generate designs or select styles in this step
|
||||
- 💬 Load all four context sources: specs, design system, visual direction, wireframes
|
||||
- 📋 Present clear context summary before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document context summary
|
||||
- 📖 Check `{output_folder}/E-Assets/wireframes/` for approved wireframes
|
||||
- 🚫 FORBIDDEN to skip any context source
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Project configuration, page specifications, design system, visual direction
|
||||
- Focus: Loading all inputs needed for page design generation
|
||||
- Limits: Do not start generating — just load context
|
||||
- Dependencies: Page specifications and design system must exist
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load Page Specifications
|
||||
|
||||
Read from `{output_folder}/C-Scenarios/`: complete page structure, user journeys, content copy, image placement.
|
||||
|
||||
### 2. Load Design System
|
||||
|
||||
Read full design system: color palette, typography scale, component patterns, spacing tokens, border/shadow/elevation tokens.
|
||||
|
||||
### 3. Load Visual Direction
|
||||
|
||||
Read brand and visual direction: brand guidelines, mood board, photography direction, illustration style.
|
||||
|
||||
### 4. Load Wireframes
|
||||
|
||||
Check `{output_folder}/E-Assets/wireframes/` for approved wireframes as structural reference.
|
||||
|
||||
### 5. Present Context Summary
|
||||
|
||||
```
|
||||
Page Design Context:
|
||||
- Pages to design: [list]
|
||||
- Design system: [name] — [token count] tokens
|
||||
- Wireframes available: [count] pages
|
||||
- Visual direction: [summary]
|
||||
- Content ready: [yes/no per page]
|
||||
```
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save context, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and context is summarized will you load {nextStepFile} to begin building the page design inventory.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Page specs loaded
|
||||
- Full design system loaded
|
||||
- Visual direction loaded
|
||||
- Wireframes checked
|
||||
- Context summary presented
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting generation without full context
|
||||
- Not checking for wireframes
|
||||
- Skipping visual direction
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
name: 'step-02-inventory'
|
||||
description: 'Identify all pages needing full design compositions and assess readiness'
|
||||
nextStepFile: './step-03-select-style.md'
|
||||
---
|
||||
|
||||
# Step 2: Asset Inventory
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Identify all pages needing full design compositions, assess readiness (wireframe, content, images, components), flag dependencies, and let the user select the generation scope.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner organizing page design inventory
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring readiness assessment expertise, user brings scope decisions
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on cataloging and assessing readiness
|
||||
- 🚫 FORBIDDEN to generate designs in this step
|
||||
- 💬 Flag pages blocked by missing assets (suggest other activities first)
|
||||
- 📋 Wait for user scope selection
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document inventory with readiness assessment
|
||||
- 🚫 FORBIDDEN to proceed without user scope selection
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Page design context from Step 1
|
||||
- Focus: Cataloging pages and assessing readiness
|
||||
- Limits: Do not generate — just catalog
|
||||
- Dependencies: Context from Step 1
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. List All Pages
|
||||
|
||||
With columns: page name, has wireframe, has content, priority.
|
||||
|
||||
### 2. Assess Readiness
|
||||
|
||||
For each page: wireframe approved? Real copy available? Source images available? All needed components defined?
|
||||
|
||||
### 3. Flag Dependencies
|
||||
|
||||
Pages needing other assets first (e.g., hero images, icon set). Suggest relevant activity (Images, Icons) first.
|
||||
|
||||
### 4. Present Inventory
|
||||
|
||||
Show ready count, blocked count, already designed count. Present scope options.
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save inventory and scope, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and scope is confirmed will you load {nextStepFile} to begin selecting design style.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All pages cataloged with readiness assessment
|
||||
- Dependencies flagged with suggestions
|
||||
- User selected generation scope
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Starting generation without readiness check
|
||||
- Not flagging blocked pages
|
||||
- Not waiting for user scope selection
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,104 @@
|
||||
---
|
||||
name: 'step-03-select-style'
|
||||
description: 'Choose design style and content style that define the visual character of page designs'
|
||||
nextStepFile: './step-04-generate.md'
|
||||
---
|
||||
|
||||
# Step 3: Select Style
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Choose the design style and content style that define the visual character of page designs, merging selected styles with design system tokens.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner defining page design visual standards
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring design style expertise, user brings aesthetic preferences
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on selecting and configuring design and content styles
|
||||
- 🚫 FORBIDDEN to generate designs in this step
|
||||
- 💬 Merge style selection with design system tokens
|
||||
- 📋 Confirm complete style selection before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document style selection with design system merge
|
||||
- 📖 Load styles from `data/styles/design-styles/` and `data/styles/content-styles/`
|
||||
- 🚫 FORBIDDEN to proceed without confirmed style
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Inventory (Step 2), design system, style libraries
|
||||
- Focus: Selecting visual style for page design generation
|
||||
- Limits: Do not generate — just define style
|
||||
- Dependencies: Inventory and scope from Step 2
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load Design Styles
|
||||
|
||||
Present available design styles from `data/styles/design-styles/`: Minimal, Corporate, Brutalist, Organic, Playful, Editorial. Highlight matches with project brand direction.
|
||||
|
||||
### 2. Load Content Styles
|
||||
|
||||
For generated visual elements within pages: select content style if the page uses illustrations or decorative elements. Skip if photography only.
|
||||
|
||||
### 3. Combine with Design System
|
||||
|
||||
Merge: style mood + design system colors, style spacing feel + design system spacing tokens, style typography approach + design system fonts.
|
||||
|
||||
### 4. Confirm Style Selection
|
||||
|
||||
Present: design style, content style (or photography only), applied to design system, output dimensions (desktop x auto, mobile x auto).
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save style, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and style is confirmed will you load {nextStepFile} to begin generating page designs.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Design style selected
|
||||
- Content style selected (or skipped for photography)
|
||||
- Style merged with design system tokens
|
||||
- Complete configuration confirmed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating without defined style
|
||||
- Not merging with design system
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
name: 'step-04-generate'
|
||||
description: 'Craft detailed prompts and generate full page design compositions'
|
||||
nextStepFile: './step-05-review.md'
|
||||
---
|
||||
|
||||
# Step 4: Generate Page Designs
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Craft comprehensive prompts and generate full page design compositions, generating desktop first then mobile, using approved results as references for batch consistency.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner executing page design generation
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring comprehensive prompt crafting expertise, user brings approval decisions
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Generate desktop first, then mobile using desktop as reference
|
||||
- 🚫 FORBIDDEN to batch-generate without per-page approval
|
||||
- 💬 Include wireframe reference when available
|
||||
- 📋 Track progress per page and view
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Track progress per page/view
|
||||
- 📖 Use approved pages as reference for subsequent generations
|
||||
- 🚫 FORBIDDEN to skip per-page approval
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Inventory (Step 2), style (Step 3), wireframes, specs
|
||||
- Focus: Prompt crafting and page design generation
|
||||
- Limits: Generate only — full set review in Step 5
|
||||
- Dependencies: Confirmed style and scoped inventory
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Build Page Design Prompt
|
||||
|
||||
For each page: layout (from wireframe or spec), color palette (hex from design system), typography (font families, sizes), style keywords, content (real headlines and body text), components, image areas, dimensions.
|
||||
|
||||
### 2. Include Wireframe Reference
|
||||
|
||||
Attach wireframe as structural reference when available. Note: "Follow layout structure, add full visual design."
|
||||
|
||||
### 3. Select Service
|
||||
|
||||
[G] Generate via MCP or [E] Export prompts.
|
||||
|
||||
### 4. Generate Sequentially
|
||||
|
||||
For each page: desktop first, present for approval, use approved desktop as mobile reference, chain approved pages for batch consistency.
|
||||
|
||||
### 5. Track Progress
|
||||
|
||||
Display progress per page and view (desktop/mobile).
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save generated designs, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and all scoped pages are generated will you load {nextStepFile} to begin reviewing the design set.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Prompts crafted with all context
|
||||
- Desktop generated before mobile
|
||||
- Reference chaining for consistency
|
||||
- Progress tracked per page/view
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Batch-generating without approval
|
||||
- Not using wireframe references
|
||||
- Generating mobile before desktop
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
117
_bmad/wds/workflows/6-asset-generation/steps-p/step-05-review.md
Normal file
117
_bmad/wds/workflows/6-asset-generation/steps-p/step-05-review.md
Normal file
@@ -0,0 +1,117 @@
|
||||
---
|
||||
name: 'step-05-review'
|
||||
description: 'Review page designs as a cohesive set for design system compliance and consistency'
|
||||
workflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 5: Review and Iterate
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Review all page designs as a cohesive set, verify design system compliance and cross-page consistency, iterate on flagged designs, and save the final approved set.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a creative production partner conducting design quality review
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring design system compliance expertise, user brings final approval
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Review as a complete set — design system compliance AND cross-page consistency
|
||||
- 🚫 FORBIDDEN to save without user approval
|
||||
- 💬 Group by page with desktop + mobile pairs
|
||||
- 📋 Check both design system tokens and cross-page visual rhythm
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Save to `{output_folder}/E-Assets/page-designs/`
|
||||
- 📖 Check: colors, typography, spacing, components, responsive layout
|
||||
- 🚫 FORBIDDEN to skip compliance or consistency checks
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All generated designs, design system, style configuration
|
||||
- Focus: Quality review, compliance, and final approval
|
||||
- Limits: This is the final step — focus on quality and delivery
|
||||
- Dependencies: Generated designs from Step 4
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Present Design Set
|
||||
|
||||
Show all designs grouped by page (desktop + mobile pairs), full-page scrollable views.
|
||||
|
||||
### 2. Design System Compliance
|
||||
|
||||
Check each design: colors match palette tokens, typography follows type scale, spacing follows spacing scale, components match patterns, responsive layout follows breakpoint rules.
|
||||
|
||||
### 3. Cross-Page Consistency
|
||||
|
||||
Verify: navigation identical across pages, footer consistent, color usage consistent (primary for CTAs), typography hierarchy consistent, visual rhythm unified.
|
||||
|
||||
### 4. User Review
|
||||
|
||||
Present: [A] Approve all, [R] Regenerate specific, [S] Style adjust, [D] Detail edit specific element, [C] Compare side-by-side.
|
||||
|
||||
### 5. Iterate
|
||||
|
||||
For flagged designs: capture feedback, adjust prompt, regenerate with approved pages as reference.
|
||||
|
||||
### 6. Save Approved Set
|
||||
|
||||
Save to `{output_folder}/E-Assets/page-designs/`: `{page-name}-desktop.png`, `{page-name}-mobile.png`, `page-design-set-summary.md`.
|
||||
|
||||
### 7. Update Design Log
|
||||
|
||||
Record: pages designed count, styles used, compliance status.
|
||||
|
||||
### 8. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF M: Save set, update design log, return to Activity Menu in {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
This is the final step of the Page Designs workflow. When M is selected and set is saved, return to the Activity Menu.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Full design set reviewed
|
||||
- Design system compliance verified
|
||||
- Cross-page consistency verified
|
||||
- User approved final set
|
||||
- Saved to correct location
|
||||
- Design log updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Saving without user approval
|
||||
- Skipping compliance or consistency checks
|
||||
- Not updating design log
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user