convez.ai
SkillProdutividadeIntermediário
FelipeOFF

My Claude Code Skills

FelipeOFF/my-claude-code-skills

Marketplace modular de skills Claude — instale apenas o que precisa

Ver no GitHub
InicialPluginScore · de 0 a 100

Marketplace curado de 130+ skills para Claude Code, organizado em pacotes temáticos instaláveis (design, copy, marketing, programming, workflow). Cada pacote contém skills vendorizados prontos para uso imediato, sem overhead de token ao carregar apenas o necessário para seu trabalho atual.

Instalação

$npx convez-ai FelipeOFF/my-claude-code-skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 3 meses
Versão
—
Issues abertas
0
Contribuidores
2

Casos de uso

  • Instalar skills especializadas por contexto de trabalho (design, marketing, programação)
  • Reutilizar guardrails e padrões de código (n-plus-one, race conditions, tdd)
  • Executar workflows com MCP servers auto-configuráveis (code-review-graph, chrome-devtools)
  • Otimizar uso de tokens carregando pacotes relevantes em vez de 130+ skills de uma vez

Veredito

Repositório bem estruturado e pragmático: marketplace modular que reduz desperdício de tokens ao permitir instalação seletiva por pacotes temáticos. Ideal para equipes que já usam Claude Code e querem reutilizar skills especializadas sem ruído; exige familiaridade com instalação de plugins e configuração local (Python 3.12, Node.js, git).

README

A tradução para o português deste README ainda está na fila.

MySkills

🇧🇷 Versão em Português

Personal Claude Code skills marketplace, curated by Felipe Oliveira and organized into themed packages installable individually.

Why packages? Loading 200+ skills every session burns tokens for no reason. Here you install only the niche relevant to your current work.

Quick install

# Once per machine
/plugin marketplace add FelipeOFF/my-claude-code-skills

# Per work context — install only what you need now
/plugin install design@myskills
/plugin install copy@myskills
/plugin install marketing@myskills
/plugin install programming@myskills
/plugin install workflow@myskills

Requirements

This marketplace is self-contained: skills are vendored (real content lives in each skill folder), so after /plugin install the skills are available immediately — no per-skill download step. A few skills shell out to local runtimes, so to use everything you need:

RuntimeVersionUsed by
Python3.12 (tested on 3.12.1; 3.10+ works)code-review-graph MCP, and the pytest/hypothesis test harnesses in n-plus-one-guard and race-condition-guard
Node.js18+skills that run via npx (render-plans-to-html, find-skills, ui-ux-pro-max) and the auto-configured MCP servers
git + ghany recentcloning standalone sources and the author's PR/branch workflow

Recommended: manage Python with asdf/pyenv and pin 3.12.1. The code-review-graph MCP expects a stable interpreter path — see programming/README.md for the .mcp.json fix.

How to use

  1. Add the marketplace once and install only the package(s) for your current work (above) — loading every skill each session wastes tokens.
  2. Vendored skills are ready on install. Their full instructions ship inside plugins/<pkg>/skills/<skill>/SKILL.md; Claude loads them on demand when the task matches the skill's description. You don't run a setup step.
  3. Optional external setup. A handful of skills can't be vendored (npm global binaries, MCP servers, large 3rd-party bundles). Each package exposes a /<package>-setup command that installs only those — it's optional and listed in the package README.
  4. Dependencies & MCPs auto-configure. Cross-marketplace plugin deps and MCP servers declared in each plugin.json install/configure automatically; personal credentials stay in your env vars (never committed).

Packages

PackageScopeWhat's insideDetails
designUI/UX, design system, taste, mockupsStitch (Google Labs), Huashu, frontend-design plugin, image generation, style packs, 21st.dev Magic MCP→ design/README.md
copyCopywriting, headlines, persuasive writingscaffold (no curated skills yet)→ copy/README.md
marketingSEO, CRO, paid traffic, email, socialTopRank (SEO)→ marketing/README.md
programmingBackend, frontend web/mobile, testing, debugging, infraStack patterns (api-design, backend/frontend-patterns, postgres-patterns, e2e-testing), vendored skills (tdd, obscura, render-plans-to-html), guardrails (n-plus-one-guard, race-condition-guard), code-review-graph MCP, Stripe, Firebase, Agent SDK, Rust LSP, MCPs (chrome-devtools, react-grab, hostinger)→ programming/README.md
workflowPlanning, memory, multi-phase, autonomous loops, multi-agentsuperpowers, claude-mem, octo, codex, ralph-specum, sleepwell, GSD bundle (64 skills), find-skills, 1password→ workflow/README.md

Why these skills?

This is active personal curation, not an exhaustive catalog. Every skill listed here was selected because the author actually uses it in real projects. Reasons cluster into:

  • Override LLM defaults: design-taste skills, frontend-patterns, code-reviewer — LLMs default to generic outputs; these skills inject opinionated rules.
  • Cross-session memory: claude-mem — long projects lose context without persistent memory.
  • Multi-phase planning: GSD, ralph-specum, superpowers — features that span days need structure (PLAN.md, REVIEW.md, milestones).
  • MCP integrations: chrome-devtools, hostinger, magic — tools the author uses daily get auto-configured (env vars stay personal).
  • Stack patterns: Anthropic SDK, Postgres, REST design — opinionated patterns, not generic boilerplate.

Each package README explains why each included skill is in the curation.

Philosophy and rules

Every "which skill goes in which package" decision follows a written constitution: docs/CONSTITUTION.md.

Summary:

  • Rule A — Single location. One skill, one package.
  • Rule B — Top-level by default. Mid-level only with >15 skills + ≥5 cohesive cluster.
  • Rule C — Frontmatter declares origin. authored | vendored | dependency | standalone-setup.
  • Rule D — Standardized package README.
  • Rule E — The Constitution is the source of truth.

Author's PT-BR/Jira workflow (repo root)

The directories agents/, commands/, and rules/ at the root are not part of any package. They're consumed via ~/.claude/CLAUDE.md global and support the author's personal workflow (Conventional Commits + Jira DTP-###, branches <type>/<JIRA>/<slug>, PRs in PT-BR).

  • agents/ — commit-crafter, jira-linker, pr-writer
  • commands/ — /branch, /commit, /pr, /review, /wt
  • rules/ — branches, commits, context7, language, workflow

Contribute / curation

This is a personal curation. Issues with suggestions are welcome, but inclusion follows Constitution criteria. To open a PR adding a skill, read docs/CONSTITUTION.md first.

Ver o original no GitHub

Bom para

Relacionados