Create Landing Page Iteration
Create a new landing page iteration with 3 variants based on provided improvements.
Usage
code
/landing [improvement description or prompt file path]
Workflow
Phase 1: Context Gathering
Before making any changes, read and understand:
- •Current landing:
index.html - •Product description:
ProductSpecification/BriefProductDescription.txt - •User stories:
ProductSpecification/MvpStories.txt - •Story specifications:
ProductSpecification/stories/*/NN_StoryName.md - •UI Mockups:
ProductSpecification/stories/*/mockups/ - •Previous prompts:
ProductSpecification/Archived/prompts/(if archived landing prompts exist) - •Latest version folder: Check
ProductSpecification/Landing-UI/LandingVersions/to determine next version number (if Landing-UI exists)
Phase 2: Analyze Requirements
If user provided a prompt file path (e.g., Draft/LandingPrompt#5.txt):
- •Read the file and extract improvement requirements
- •Summarize what needs to change
If user provided inline description:
- •Parse the improvement requirements from their message
Phase 3: Create Variants
- •Determine next version number (vN+1)
- •Create folder:
ProductSpecification/Landing-UI/LandingVersions/vN+1/
Phase 4: Design Constraints (MUST follow)
- •Color scheme: Light theme with neon green accent
#00e87b - •Language: English
- •Responsive: Mobile/tablet/desktop
- •Animations: Scroll-triggered fade animations
- •Phone input: International format
- •Never modify: Original
index.htmland sections that are not supposed to be changed - •Never modify: Sections that are not the topic of the prompt
Phase 6: Output Summary
After creating variants, provide:
- •List of created files with paths
- •Brief description of each variant's approach
- •Key differences between variants
- •Recommendation on which to review first
Example Invocations
code
/landing Draft/LandingPrompt#5.txt
code
/landing Improve the "how it works" section with product mockups and add a profits highlight before pricing
Notes
- •Always create 3 variants so user can compare approaches
- •Variants should be meaningfully different, not minor tweaks
- •Stay consistent with design decisions from previous prompts