Maestro's skills

A few skills that change everything.

Shaping your idea, designing screens, writing code, checking the result: the team uses the skills your project needs. There is nothing for you to configure.

A skill helps the team do its work. The result still needs to be checked on your project.

Featured

Scroll through eight areas of expertise and their practical differences.

All the skills

The skills available in Maestro, grouped by topic.

146 skills

Launch and growth 28

  • Paid advertising
  • AI search visibility
  • Measurement and analytics
  • Retention
  • Cold email
  • Editorial strategy
  • Persuasive writing
  • Conversion optimization
  • Customer research
  • Email marketing
  • Product launch
  • Lead magnets
  • Marketing psychology
  • Product naming
  • Offer design
  • Onboarding and activation
  • Paywalls
  • Popups and banners
  • Pricing
  • Product marketing
  • Programmatic SEO
  • Referrals
  • Structured data
  • SEO audit
  • Sign-up and trials
  • Social media
  • Comparing two versions
  • Brand voice

Design and interface 27

  • Information architecture
  • Visual composition
  • Design references
  • Interface design
  • UX guidelines
  • Form design
  • Frontend design
  • Design standards
  • Interface accessibility
  • Interface colors
  • Interface details
  • Layout
  • Interface review
  • Typography
  • Visual reference analysis
  • Interface animation
  • Corporate style
  • E-commerce style
  • Fintech style
  • Food and hospitality style
  • Luxury style
  • Premium product style
  • Warm SaaS style
  • General SaaS style
  • Dark SaaS style
  • Showcase and sales style
  • Visual themes

Your product's business functions 8

  • Receipts and expenses
  • Invoicing
  • Payroll
  • Orders and payments
  • Bookings and time slots
  • Personal data and GDPR
  • Stock and inventory
  • Billable time

A founder's daily work 8

  • Turning business needs into requirements
  • User feedback
  • Founder finances
  • Fundraising emails
  • Investor research
  • Pitch deck
  • Customer support
  • Help documentation

Engineering 36

  • Authentication and secrets
  • Supabase database
  • React best practices
  • Choosing technologies
  • Code architecture
  • Code conventions
  • Email deliverability
  • API design
  • Transactional emails
  • Detecting silent failures
  • Finding bugs
  • Error handling
  • Multilingual product
  • Product instrumentation
  • Publishing on Vercel
  • Zero-downtime migration
  • Product notifications
  • Web performance
  • Native platform capabilities
  • Life in production
  • React interface patterns
  • Receiving reviews
  • Existing code rules
  • Fixing the build
  • Requesting reviews
  • Import-ready data structure
  • Security foundations
  • Security review
  • Technical SEO
  • Keeping code simple
  • Supabase integration
  • Methodical debugging
  • Tests first
  • Preventing errors with types
  • Environment variables
  • Evidence before delivery

Writing 4

  • Accessible content
  • Collaborative writing
  • Interface copy
  • Natural writing

Product 18

  • Refining the idea
  • Preparing to build
  • Pre-launch approval
  • Release decision
  • Task planning
  • Project reference documents
  • Problem definition
  • Project discovery interview
  • Metrics and dashboards
  • Decision history
  • Release notes
  • Competitive analysis
  • Product specification
  • First-run experience
  • First-version scope
  • Prioritization
  • Exploring ideas
  • Breaking work into tasks

Quality 12

  • Post-launch checks
  • Reproducing a reported bug
  • Edge case checks
  • User journey checks
  • Combinatorial test plan
  • Post-incident review
  • Code simplification
  • End-to-end tests
  • Component tests
  • Test quality
  • Pre-delivery verification
  • Application testing

Legal 5

  • Data retention
  • Cookie banners
  • European legal foundations
  • French law
  • External services and data