Skillπ
Categories
By use caseBy profession ↗Collections ↗
Development & operations
Coding & code reviewTesting & security
Systems & automation
Browser automationWorkflow automation
AI & agents
Building agents & AI appsPrompts & model use
Data & analytics
Analysis & visualizationDatabases & processing
Office & collaboration
Documents & spreadsheetsKnowledge bases & notes
Writing & content
Writing & copywritingDesign & images
Business & industries
SEO & marketingSales & customer service
Learning & research
Research & informationTeaching & learning
Life & interests
Personal productivity & daily lifeEntertainment & hobbies
Browse all skills →
GuideAboutCreator Studio
Collections
Curated skills for your next task
Product launchFrom a clear brief to a page you can inspect and a release decision backed by evidence.Agent starter kitA practical first workflow for Codex or Claude Code: build one small change and verify it.Clear, human writingImprove structure and phrasing without inventing facts or erasing the writer’s voice.Marketing & SEOConnect an audience, a useful page and measurable improvements instead of chasing a generic score.Documents & knowledgeTurn source material into a readable document, inspect PDF output and connect knowledge only when the workspace is ready.Design engineeringChoose a coherent direction, implement the interface and inspect the details without losing the product’s identity.
Browse all collections →Reviewed weekly · Individual terms apply
Packs ↗
中文

A SKILLπ COLLECTION

Product launch

From a clear brief to a page you can inspect and a release decision backed by evidence.

5 skills0 upstream referencesEdited 2026-11-03

THE OUTCOME

What you will work toward

Founders, product teams and independent builders

  • A short launch brief
  • A consistent landing page and visual direction
  • A checklist of evidence and remaining blockers

A SUGGESTED SEQUENCE

Start with this sequence

  1. Define the promise

    Choose the audience, the problem and one primary action. Write down which claims need evidence before drafting the page.

  2. Build, then inspect

    Use a primary frontend direction, add supporting visuals, and test the actual user journey at desktop and mobile sizes. Keep payment or account decisions separate from visual demos.

  3. Make a release decision

    Review copy and runtime evidence. Record what passed, what is simulated and what still needs a person. A release-readiness report does not sign contracts, deploy or take payment.

CHOOSE WHAT FITS

Skills in this collection

Choose what your task needs rather than applying every skill at once. The links retain their individual sources and licenses.