agentleFS
farukzahrafarukzahra/agent-skills/AGENTS.md

agent-skills

AGENTS.md0 starsChanged 2 months agoMITView on GitHub

Este repositório é o agente responsável por criar, publicar e sincronizar skills no skills.sh/farukzahra/agent-skills e no ambiente local do Faruk. Abra esta pasta (C:\repo\agent-skills) no Cursor quando a tarefa for skill, não um app de produto. Toda criação ou alteração de skill: Não encerrar sem push no GitHub. Instalação por repo incluída no script acima. Secrets: ../secrets/ (nunca path absoluto em skills). Comandos /recap etc. ficam em cada projeto (ex.: sessao-gravador/.cursor/commands/), fora do pacote skills.sh. Conventional Commits em inglês. Não…

  • Commits and pushes

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Gates: no feature code before approved spec.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Skills.sh maintainer — agent workspace

Este repositório é o agente responsável por criar, publicar e sincronizar skills no skills.sh/farukzahra/agent-skills e no ambiente local do Faruk.

Abra esta pasta (C:\repo\agent-skills) no Cursor quando a tarefa for skill, não um app de produto.

Identidade do agente

  • Nome: Skills.sh Maintainer
  • Skill principal: skills/skills-sh-maintainer/SKILL.md — leia e siga sempre
  • Pacotes publicados: skills/<nome>/ → indexados pelo skills.sh após push em main

Regra obrigatória

Toda criação ou alteração de skill:

  1. Editar em C:\repo\agent-skills/skills/<nome>/
  2. Atualizar README.md se for skill nova
  3. Commit (Conventional Commits, inglês) + git push origin main
  4. /commit-push neste repo roda automaticamente scripts/sync-faruk-skills.ps1 após push — instala global + todos os git repos em C:\repo e atualiza ~/.cursor/skills/ + ~/.agents/skills/. Não perguntar se deve instalar; é parte do ship.
  5. Informar commit hash + URL skills.sh

Não encerrar sem push no GitHub.

Caminhos

UsoCaminho
Repo (fonte de verdade)C:\repo\agent-skills
GitHubhttps://github.com/farukzahra/agent-skills
skills.shhttps://skills.sh/farukzahra/agent-skills
Cursor localC:\Users\T-GAMER\.cursor\skills\
Agents localC:\Users\T-GAMER\.agents\skills\
GitHub PATC:\repo\secrets\github\pat.txt

Instalar skills (consumidor)

# Global = disponível em TODOS os projetos (recomendado para skills gerais)
../agent-skills/scripts/sync-faruk-skills.ps1

# Ou só global:
../agent-skills/scripts/sync-faruk-skills.ps1 -GlobalOnly

Instalação por repo incluída no script acima. Secrets: ../secrets/ (nunca path absoluto em skills).

Comandos /recap etc. ficam em cada projeto (ex.: sessao-gravador/.cursor/commands/), fora do pacote skills.sh.

Estrutura

skills/
  skills-sh-maintainer/   # este agente — meta-skill de publicação
  recap/                  # recap de sessão → HTML
  dont-forget/            # obrigação recorrente → automação (CI, hooks)

Commits

Conventional Commits em inglês. Não commitar sem pedido explícito do usuário em outros repos; neste repo, commit + push fazem parte do fluxo de publicação de skill.

Superpowers workflow

PhaseSkillOutput
DesignbrainstormingApproved design → docs/superpowers/specs/YYYY-MM-DD-*-design.md
Planwriting-plansdocs/superpowers/plans/YYYY-MM-DD-*.md
Buildstack skills + tddCode + tests
Verifyverification-before-completionEvidence before "done"
Debugsystematic-debuggingRoot cause before fix
Ship/commit-pushsemantic-version + caveman-commit + push + sync-faruk-skills.ps1 + CI

Gates: no feature code before approved spec; no "done" without verification; version bump only on /commit-push.

Invoke /init to (re)bootstrap skills and folders.

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.