Skip to content

Instantly share code, notes, and snippets.

@johnlindquist

johnlindquist/gist:a731a754f1225f4c1b21c85bf3244e53

Created October 4, 2025 19:07
Show Gist options
  • Save johnlindquist/a731a754f1225f4c1b21c85bf3244e53 to your computer and use it in GitHub Desktop.
Save johnlindquist/a731a754f1225f4c1b21c85bf3244e53 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
cursor-workshop-recommendations.md# Cursor Workshop Landing Page - Multi-Perspective Analysis
**Analysis Date:** January 2025
**Method:** Three simultaneous GPT-5 Pro analyses from different perspectives
---
## Executive Summary
Three expert analyses of the Cursor Workshop landing page converged on similar core issues while providing complementary recommendations. All three identified the need for:
1. **Concrete, measurable learning outcomes** instead of vague skill descriptions
2. **Complete logistics information** (pricing, schedule, prerequisites, FAQ)
3. **Better page structure** with scannable sections and clear CTAs
4. **Proof of value** through specific deliverables and artifacts students will keep
5. **Team/enterprise buyer focus** alongside individual enrollment
---
## Perspective 1: Structure & Learning Outcomes
**Focus:** Page architecture, concrete outcomes, missing sections
### Key Recommendations
#### Concrete Learning Outcomes (Replace current "Essential Skills")
By the end of the workshop, you will be able to:
1. **Author a team Cursor Rulebook** that enforces code style, naming, and file boundaries; publish it to your repo
2. **Generate a project scaffold** (API + UI) with tests and linting in 15 minutes
3. **Plan agent work** with acceptance criteria so the agent doesn't wander into wrong files
4. **Curate agent context** to reduce 1k+ file repos to the 8-12 files actually needed
5. **Detect and break agent loops** using logging and intermediate checks with Git rollback
6. **Pipe logs and test output** directly into Chat/Composer and iterate until tests pass
7. **Refactor safely** keeping public APIs stable with passing tests
8. **Automate Composer toolchain** replacing 2-3 terminal steps
9. **Review AI changes** with rule-driven PR hygiene checklist
10. **Measure impact** with ready-made dashboard (PR size, time-to-green, revert rate)
**Deliverables students keep:**
- Cursor Rulebook for team use
- Composer pipelines for CI-like automation
- Acceptance Criteria + Agent Plan templates
- Context Curation Playbook
- Loop Breaker Checklist
- PR Hygiene Checklist
#### Recommended Page Structure
```
1. Hero (above fold)
- H1: Ship reliable AI-generated code with Cursor in one day
- Subhead: Master shared rules, agent planning, context curation
- Primary CTA: "Enroll now"
- Secondary CTA: "Get team pricing"
- Trust badges: Testimonials, "Recording included", Team licenses
2. Sticky Navigation
- Outcomes Curriculum Schedule Pricing Team FAQ
3. Who This Is For / Not For
- 3-5 bullets each for self-qualification
4. What You'll Walk Away With
- Measurable outcomes
- Tangible assets/templates
5. Curriculum (6 modules)
- For each: What you'll learn What you'll do What you'll keep
6. Schedule & Format
- Live cohort details
- Day-of agenda with timestamps
- Recording access window
7. Pricing & Plans
- Individual: 1 seat + recordings + assets
- Team (5-10): + shared rulebook review + Q&A
- Enterprise: custom date + repo-specific support
- Guarantee: 14-day refund
8. Team Outcomes (B2B block)
- Shared rulebooks, faster PR cycles, lower revert rate
9. Testimonials (Role Result format)
- "Kent C. Dodds, Educator Shipped OAuth in minutes"
10. FAQ (8-12 questions)
- Recording access, difficulty level, tool requirements, refunds
11. Final CTA
- Repeat outcomes + guarantee + price
```
#### Missing Sections to Add
- **Schedule**: Specific date/time, timezone, breaks, duration
- **Pricing**: Transparent tiers with what's included
- **Prerequisites**: Git comfort, Node setup, IDE installed
- **Guarantee**: "Full refund if you don't get a working rulebook and pipeline"
- **What's Included**: Templates, recordings, office hours duration
- **FAQ**: Address common objections
- **Team Buyer Block**: ROI metrics, procurement support
---
## Perspective 2: Marketing & Messaging
**Focus:** Copywriting, persuasion, value proposition clarity, conversion optimization
### Key Recommendations
#### Hero Section Improvements
**Current:** "In just a single day you'll set up shared rules..."
**Recommended:**
```
H1: Ship reliable AI-generated code with Cursor in one day
Subhead: Master the planning, context, and feedback loops that make AI
coding tools reliableon any team and any codebase.
CTA buttons:
- Reserve your seat (Primary)
- Download syllabus (Secondary)
Trust row: Recording included Team licenses 14-day refund
```
#### Outcome-Focused Copy
Instead of: "You'll learn agent behavior, tool calls, and context limitations"
Use: **"By the end of the day, you'll ship a small feature from a written plan, with a rules file, a Composer pipeline, and a clean PR that passes testswithout the agent going off the rails."**
#### Testimonial Format Upgrade
**Current:** Just quotes
**Recommended:** Mini case studies with Problem Change Result
```
Kent C. Dodds Educator & OSS maintainer
Problem: New OAuth flow was tedious across repos
Change: Applied Cursor rules + Composer pipeline for auth scaffolding
Result: "One-shot OAuth in minutes" (with repo diff snapshot)
David Wells Founder/Engineer
Problem: Agents looped on a CI error
Change: Implemented loop signals + stop-and-swap playbook
Result: Resolved in <10 minutes; repeatable for future incidents
```
#### Pricing Structure
```
Individual Live Seat: $X00
- Live workshop
- Recording (12 months)
- Templates & checklists
- Updates for 90 days
Team Pack 5 Seats: $Y,YYY
- All Individual benefits
- Private Q&A call for your team
- Shared rulebook review
Company License: Contact sales
- Unlimited seats
- Private date
- NDA option
Policies:
- 14-day refund if not satisfied
- Transfer seat up to 24h before start
- Limited seats for interactive exercises
```
#### Copy Improvements
1. **Fix typos:** "along side" "alongside"
2. **Tighten paragraphs:** Split long sentences, remove parentheticals
3. **Add specificity:** Name concrete deliverables for each section
4. **Reduce emoji use:** Keep single in testimonials, avoid in body copy
5. **Convert feature headers to benefit headers:**
- Instead of: "Logging & Feedback Loops"
- Use: "Turn failures into fast fixes: pipe logs straight into the agent"
#### "What's Included" Section
Make this explicit:
- Workshop recording + searchable transcript
- Rule templates, planning prompts, Composer pipeline examples
- Debugging loop checklist, context-pack worksheet
- Example repo(s) with tags per exercise
- Slide deck + "cheat sheets" (hotkeys, prompt patterns)
- Optional: certificate/badge of completion
---
## Perspective 3: Technical Accuracy & Features
**Focus:** Current Cursor features, competitive landscape, technical correctness
### Key Recommendations
#### Curriculum with Exercises + Deliverables
**Module 1 Project Generation Mastery**
- **Learn:** Scaffolding patterns, dependency pinning, test harness
- **Do:** Spin up minimal full-stack app; add auth stub
- **Keep:** Starter templates + "safe-scaffold" checklist
**Module 2 Planning & Cursor Rules**
- **Learn:** Write maintainable rules, acceptance criteria, task breakdown
- **Do:** Create Rulebook for naming, file boundaries, testing
- **Keep:** Rulebook template + 20 proven rule snippets
**Module 3 Bulk Code Analysis & Bugfinding**
- **Learn:** Target right files; recognize loop signals
- **Do:** Fix seeded bug by constraining context to <15 files
- **Keep:** Context curation playbook + loop breaker checklist
**Module 4 Logging & Feedback Loops**
- **Learn:** Pipe test/runtime logs into Chat/Composer
- **Do:** Break failing test streak in 3 cycles
- **Keep:** Log-to-prompt shortcuts, triage template
**Module 5 Refactoring & UI Checks**
- **Learn:** Safe refactors, visual diffs, UI snapshot checks
- **Do:** Refactor component without breaking consumers
- **Keep:** UI review checklist, refactor plan template
**Module 6 Composer Toolchain Pipelines**
- **Learn:** Automate repetitive terminal workflows
- **Do:** Build "build test format summarize" pipeline
- **Keep:** 3 reusable Composer pipelines
#### Sample Schedule (1-Day Live)
**Time:** 6 hours total
- 0:000:20 Orientation + setup
- 0:201:20 Modules 12
- 1:201:30 Break
- 1:302:30 Modules 34 (hands-on)
- 2:302:40 Break
- 2:403:40 Modules 56 (hands-on)
- 3:404:00 Wrap-up, next steps
**Support:** Private chat space, 2 office-hour sessions post-workshop, template updates
#### Technical Requirements Section
**Tools:**
- Cursor (latest version)
- Git
- Node 18+
- Package manager (npm/yarn/pnpm)
**Accounts:**
- Model provider(s) with sufficient credits/limits
**Access:**
- Demo repo provided
- Optional "bring your repo" track
**OS:** macOS/Windows/Linux supported
**Pre-work (15-20 min):**
- Install tools
- Clone demo repo
- Run tests to verify setup
#### FAQ (Technical Focus)
**Q: Will this work if we use Windsurf/Kiro/Cline?**
A: Yes; principles are tool-agnostic, but demos use Cursor.
**Q: What if the models change next week?**
A: You'll learn durable workflows + get update guidelines.
**Q: How do you handle token limits?**
A: Context curation + file sets + diff-based prompting techniques.
**Q: Can we use our private code?**
A: Yes in private cohorts; otherwise sanitized demo repo provided.
**Q: Will I get the assets?**
A: Yes: rules, pipelines, templates, and checklists with team license options.
**Q: Invoices/procurement?**
A: Yes; team & enterprise options available.
**Q: Accessibility?**
A: Captions, transcript, keyboard-friendly labs provided.
---
## Implementation Checklist
### Phase 1: Structure (High Priority)
- [ ] Add sticky navigation with anchor links
- [ ] Restructure into 10-11 clear sections
- [ ] Add "Who this is for / not for" section
- [ ] Create FAQ section (8-12 questions)
### Phase 2: Content (High Priority)
- [ ] Replace generic "Essential Skills" with 10 concrete, measurable outcomes
- [ ] Add "What you'll keep" deliverables list
- [ ] Rewrite curriculum with Learn/Do/Keep format for each module
- [ ] Convert testimonials to Problem/Change/Result mini-case studies
### Phase 3: Logistics (High Priority - Conversion Blockers)
- [ ] Add transparent pricing with 3 tiers
- [ ] Add schedule with specific times/duration
- [ ] Add "What's included" section
- [ ] Add prerequisites/requirements
- [ ] Add guarantee/refund policy
- [ ] Add team/enterprise buyer block
### Phase 4: Polish (Medium Priority)
- [ ] Fix typo: "along side" "alongside"
- [ ] Tighten hero copy
- [ ] Add sticky CTA buttons
- [ ] Reduce emoji usage
- [ ] Add role/company to testimonials
- [ ] Create downloadable syllabus PDF
### Phase 5: Technical (Medium Priority)
- [ ] Add structured data (Course/Event/Product schema)
- [ ] Add Open Graph meta tags
- [ ] Optimize images
- [ ] Test mobile layout
- [ ] Add conversion tracking on CTAs
---
## Quick Wins (Do These First)
1. **Add concrete outcomes** - Replace vague "Essential Skills" with the 10 measurable outcomes
2. **Add pricing** - Transparent solo/team/enterprise tiers with guarantee
3. **Add schedule** - Specific date, time, duration, what's included
4. **Add FAQ** - 8-12 questions addressing common objections
5. **Fix testimonials** - Add roles, companies, specific results
6. **Add "What you'll keep"** - List the 6 deliverable assets
7. **Fix typos** - "along side" "alongside"
8. **Add team buyer block** - ROI metrics, procurement support
---
## Consensus Themes Across All Three Analyses
All three perspectives independently identified:
**Outcomes are too vague** - Need measurable, concrete statements
**Missing critical sections** - Pricing, schedule, FAQ, prerequisites
**Testimonials need work** - Add context, roles, specific results
**Page structure needs hierarchy** - Too flat, hard to scan
**Value prop unclear** - What exactly do students walk away with?
**Team buyer neglected** - Need B2B-specific section
**Copy could be tighter** - Too many long paragraphs
**CTAs need work** - Not prominent enough, lack urgency
---
## Next Steps
1. **Prioritize logistics sections** - Pricing/schedule/FAQ are conversion blockers
2. **Rewrite outcomes section** - Use the 10 concrete outcomes provided
3. **Add deliverables list** - The 6 artifacts students keep
4. **Restructure page** - Use recommended 10-section architecture
5. **Update curriculum** - Learn/Do/Keep format for each module
6. **Enhance testimonials** - Add Problem/Change/Result format
7. **Create FAQ** - Address the questions listed above
8. **Add team section** - ROI metrics, procurement options
---
**Analysis Complete.** All recommendations above are ready to implement directly into the page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment