Receber por email
← Voltar para o catálogo

inits

Analise uma base de código e crie ou melhore um arquivo AGENTS.md para futuras instâncias de agente. Use ao integrar-se a um repositório e capturar convenções, restrições e justificativas difíceis de redescobrir.

27estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add OutlineDriven/odin-claude-plugin

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

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

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

Init - AGENTS.md Generator

Analyze this codebase and create or improve an AGENTS.md file for future ODIN Code Agent instances.

Core principle

Only encode knowledge that is expensive to rediscover. An agent can fd, rg, ast-grep, and read files in seconds. If the information is one search away, omit it.

Objective guard

AGENTS.md is for priming and guiding future agents with conventions, constraints, and rationale. It is not a repository summary.

What to include

  1. Cross-cutting conventions and boundaries that span multiple files.
  2. Implicit contracts and operational constraints that are easy to miss in quick code exploration.
  3. Non-obvious command guidance only when hidden constraints matter (required ordering, flags, env vars, caveats).
  4. For each included item, state:
  5. the rule or constraint
  6. why it exists (rationale)

What to omit (the agent can discover these)

  • File trees, per-directory descriptions, or component inventories.
  • Dependency/version tables.
  • Generic development best practices.
  • Information that is easily discoverable via search/read.
  • Fabricated filler sections such as "Common Development Tasks", "Tips", or "Support".
  • Any summary-style prose that restates code organization without conventions or rationale.

Workflow

  • If AGENTS.md already exists, suggest targeted improvements instead of rewriting.
  • Do not repeat yourself. Each fact appears once.
  • Every statement must be grounded in files you actually read. Never invent.
  • If uncertain, omit the claim rather than speculate.
Compartilhar X LinkedIn