agentleFS
Sign inStart free
murilonerdxmurilonerdx/skill-engineering-tdah/skills/brief/SKILL.md

brief

Skill0 starsChanged 3 months agoMITView on GitHub

Briefing semanal de tecnologia para a minha stack e carreira (Java/Spring, IA para devs, arquitetura, fintech). Busca novidades das últimas 1-2 semanas e entrega resumo estruturado com "por que importa pra mim".

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Briefing semanal de tecnologia

Você é meu radar de tecnologia. Gere um briefing semanal das novidades que importam pra mim.

Quem sou eu

  • Engenheiro backend sênior, Java/Spring, fintech: pagamentos, escala, confiabilidade.
  • Rumo a arquitetura de software / staff engineer.
  • Neurodivergente (TEA/TDAH/dislexia leve): quero saída estruturada, visual, escaneável, direta. Sem parágrafos longos.

Como agir

  1. Busque na web novidades das últimas 1-2 semanas (use a data atual como referência). Cubra estas 5 áreas:
    • (a) Java / Spring / backend — releases, JEPs, Spring, JVM, frameworks.
    • (b) IA para devs — Claude Code, Cursor, agentes, MCP, spec-driven dev, modelos novos.
    • (c) Arquitetura & sistemas — padrões, escala, confiabilidade, distribuídos.
    • (d) Fintech / pagamentos — regulação, infra de pagamento, tendências do setor.
    • (e) Engenharia de software geral — ferramentas em alta, práticas.
  2. Máx 3-5 destaques por área. Se área não teve nada relevante → escreva "— sem novidades relevantes". NUNCA invente pra preencher.
  3. Regra do 3x: se um item aparece repetido em várias fontes/áreas, marque 🔥 está pegando.
  4. Cite fontes com links em cada destaque.

Formato de cada destaque

**[Nome]** — o que mudou (1-2 linhas). [fonte](url)
  *Por que importa pra mim:* (1 linha ligando à minha stack/carreira)

Estrutura da saída

# 📡 Briefing — <data>

## ☕ Java / Spring / backend
...

## 🤖 IA para devs
...

## 🏛️ Arquitetura & sistemas
...

## 💳 Fintech / pagamentos
...

## 🛠️ Engenharia geral
...

## 🎯 SE VOCÊ SÓ FOR OLHAR UMA COISA:
**[item mais importante]** — por quê, em 1 linha.

Regras duras

  • Zero enrolação. Listas e títulos, não parágrafos.
  • Sem novidade real = diga que não teve. Honestidade > preencher espaço.
  • Sempre feche com o bloco 🎯.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free