feat: refactor 30+ skills to Anthropic progressive disclosure pattern

- All SKILL.md files now <500 lines (avg reduction 69%)
- Detailed content extracted to references/ subdirectories
- Frontmatter standardised: only name + description (Anthropic standard)
- New skills: brand-guidelines, spec-coauthor, report-templates, skill-creator
- Design skills: anti-slop guidelines, premium-proposals reference
- Removed non-standard frontmatter fields (triggers, version, author, category)

Plugins affected: infraestrutura, marketing, dev-tools, crm-ops, gestao,
core-tools, negocio, perfex-dev, wordpress, design-media

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-03-12 15:05:03 +00:00
parent 9404af7ac9
commit 6b3a6f2698
397 changed files with 67154 additions and 17257 deletions

View File

@@ -0,0 +1,83 @@
# Product - Metricas de Produto
## AARRR Pirate Metrics
| Fase | Metrica | Target |
|------|---------|--------|
| **Acquisition** | Signups/semana | +20%/mes |
| **Activation** | Setup completo | > 40% |
| **Retention** | D7 retention | > 30% |
| **Revenue** | Conversion free->paid | > 3% |
| **Referral** | NPS | > 40 |
## Product Health
### Engagement
- DAU/MAU ratio (stickiness): > 20%
- Session duration: Sector-dependent
- Features usado/session: > 3
### Adoption
- Time to first value: < 10 min
- Feature adoption (30 dias): > 30%
- Power users (5+ dias/semana): > 10%
### Quality
- Error rate: < 1%
- Support tickets/100 users: < 5
- CSAT: > 4/5
## Outcomes vs Outputs
```
ERRADO (Output-driven):
"Lancar 10 features este trimestre"
CERTO (Outcome-driven):
"Aumentar retention D30 de 20% para 35% (via engagement features)"
Medir:
- North Star Metric (ex: DAU/MAU)
- Leading indicators (ex: time-to-value)
- Lagging indicators (ex: churn)
```
## Discovery - Pain Points
```
Perguntas a fazer:
1. O que frustra o utilizador actualmente?
2. Que workarounds usa hoje?
3. Quanto tempo/dinheiro perde com o problema?
4. Qual a frequencia do problema?
5. O que tentou fazer para resolver?
Evidencia:
- [ ] 5+ entrevistas com users
- [ ] Analytics de uso (onde abandonam?)
- [ ] Tickets de suporte relacionados
- [ ] Pesquisa concorrencia (como resolvem?)
```
## Validation Framework
### Desirability (Users querem?)
- Problem interviews (10+)
- Solution interviews (5+)
- Survey (50+ respostas)
- Prototype test (usability)
- Evidence: X% users pagaria, Y% usaria diario
### Viability (Negocio faz sentido?)
- Market size (TAM/SAM/SOM)
- Revenue model claro
- Unit economics positivos
- Payback period aceitavel
- Target: ROI > 3x em 12 meses
### Feasibility (Conseguimos construir?)
- Technical spike completo
- Dependencies mapeadas
- Resources disponiveis
- Timeline realista
- Risk assessment: Alto/Medio/Baixo