S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

develop-platform-product-thinking

Design e Frontend Autor: alexe-ev

Apply platform and API product thinking to define developer experience, extensibility, and ecosystem strategy. Use this skill when a team is building a platform, API, or developer-facing product.

0estrelas
Atualizado há 7 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add alexe-ev/product-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/develop-platform-product-thinking/svg)](https://www.skillteca.com.br/skills/develop-platform-product-thinking)
#ai #api

Skills relacionadas

Ver todas de Design e Frontend →

frontend-design

153.1k 2

Cria interfaces frontend distintas e de nível de produção com alta qualidade de design, gerando código criativo e polido e design de UI que evita a estética genérica de IA. Use para construir componentes web, páginas e aplicações, ou para estilizar/embelezar UIs web.

Design e Frontend #ai #css por anthropics

mcp-builder

153.1k

Guia para criar servidores MCP (Model Context Protocol) de alta qualidade que permitem que LLMs interajam com serviços externos por meio de ferramentas bem projetadas. Use ao construir servidores MCP para integrar APIs ou serviços externos, seja em Python (FastMCP) ou Node/TypeScript (MCP SDK).

Design e Frontend #api #llm por anthropics

webapp-testing

153.1k

Kit de ferramentas para interagir e testar aplicações web locais usando Playwright. Suporta a verificação de funcionalidades de frontend, depuração de comportamento da UI, captura de screenshots do navegador e visualização de logs do navegador.

Design e Frontend #test por anthropics

web-artifacts-builder

153.1k

Conjunto de ferramentas para criar artefatos HTML elaborados e multi-componentes para claude.ai, utilizando tecnologias web frontend modernas (React, Tailwind CSS, shadcn/ui). Use para artefatos complexos que exigem gerenciamento de estado, roteamento ou componentes shadcn/ui, não para artefatos HTML/JSX simples de arquivo único.

Design e Frontend #ai #css por anthropics

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Develop Platform Product Thinking

Purpose

Help teams apply platform product thinking to define a clear developer experience, extension model, and ecosystem strategy.

Skill type

Conceptual skill

Use this skill when

  • A product is evolving into a platform with external developers or partners
  • An API product needs developer experience strategy
  • A team is deciding how much to expose vs. internalize in a platform
  • An ecosystem or marketplace strategy needs to be defined

Do not use this skill when

  • The goal is technical API design (a technical, not product, skill)
  • The goal is internal tool or workflow automation

Required inputs

  • Product type and current capabilities
  • Developer or partner audience

Optional inputs

  • Current API or integration surface
  • Developer feedback
  • Competitive platform landscape
  • Business model for the platform

Upstream context

Works best when:

  • Product strategy is defined
  • Target developer segment is identified

Downstream handoff

Output can feed:

  • prioritize-architecture-aware (platform strategy informs architectural priorities)
  • develop-positioning-messaging (platform needs developer-facing positioning)

Instructions

  1. Define the platform layer: what does it expose, to whom, and why?
  2. Identify the developer/partner value proposition.
  3. Define the developer experience principles.
  4. Assess the extensibility model: open / controlled / hybrid.
  5. Identify ecosystem opportunities and risks.
  6. Define the build vs. partner vs. ecosystem boundary.

Output

Provide:

  • Platform layer definition
  • Developer/partner value proposition
  • Developer experience principles
  • Extensibility model recommendation
  • Ecosystem opportunity and risk assessment
  • Build vs. partner boundary decision
  • Open questions

Risks / caveats

  • Platform products have two customers: end users and developers — both must win
  • Over-opening a platform creates quality and support risks
  • Developer adoption requires excellent documentation — factor it into the platform plan
Compartilhar X LinkedIn