Receber por email
← Voltar para o catálogo

evolve

Transforme um padrão de falha repetido em uma melhoria do sistema. Gera uma proposta concreta para restrições, documentação ou automação.

556estrelas
Atualizado há 2 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add majiayu000/claude-skill-registry

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/evolve/svg)](https://www.skillteca.com.br/skills/evolve)

Skills relacionadas

Ver todas de Pesquisa e Web →

Alerta por categoria

Receba novas skills de Pesquisa e Web toda segunda

1 email curto, só com as skills novas de Pesquisa e Web. 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

Evolve

Convert repeated mistakes into rules or automation. Requires 2+ occurrences with evidence.

Inputs

Ask the user for:

  • What happened (describe the failure)
  • How many times (must be 2+ across sessions or PRs)
  • Evidence (PR/issue links or excerpts)
  • Where it should have been caught (tooling, docs, invariant)

Decision hierarchy (smallest effective change)

  1. Automate — Can tooling enforce it (lint rule, CI check, pre-commit hook)? If yes, propose automation first.
  2. Tier 1 constraint — Applies to all code, critical to enforce? Add to AGENTS.md invariants.
  3. Tier 2 guidance — System-specific, helpful but not critical? Add to the relevant doc in docs/.
  4. Reference only — Best practice but not enforceable? Add as a comment or reference doc.

Output format

## System Evolution Proposal
### Failure Pattern
What: <description>
Frequency: <X> times across <Y> PRs/sessions
Evidence: <links or excerpts>
### Decision: AUTOMATION | TIER 1 | TIER 2 | REFERENCE
Rationale: <1-2 sentences>
### Proposed Change
Location: <exact file path + section>
Proposed addition:
  <exact text to add — use positive constraints>
### Implementation Steps
1. <what to modify>
2. <validation needed>
3. <PR creation>

Notes

  • Use positive language ("Do X", not "Don't do Y").
  • Do not modify files until the user approves the proposal.
  • Prefer automation when possible — enforced beats documented.
Compartilhar X LinkedIn