convez.ai
MCP Server
shengdabai

everything-claude-code

shengdabai/everything-claude-code

Ver no GitHub
BomPluginScore · de 0 a 100

Curated, battle-tested Claude Code toolkit: 9 agents, 11 skills, 15 commands, rules, hooks & 15 MCP configs — install as a plugin or copy in.

Instalação

$npx convez-ai shengdabai/everything-claude-code

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
85%
Último commit
há 1 semana
Versão
—
Issues abertas
0
Contribuidores
6

README

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

everything-claude-code

Curated, battle-tested Claude Code toolkit: 9 agents, 11 skills, 15 commands, rules, hooks & 15 MCP configs — install as a plugin or copy in.

Business Context

  • Category: AI workflow infrastructure
  • Audience: AI builders, creators, independent developers, and small teams that want repeatable local AI workflows.
  • Repository status: Public repository. Keep examples, docs, and issues free of credentials, private data, and machine-specific paths.
  • Topics: agents, ai, awesome, claude, claude-code, hooks, mcp, skills, slash-commands

What This Project Is For

  • Curated, battle-tested Claude Code toolkit: 9 agents, 11 skills, 15 commands, rules, hooks & 15 MCP configs — install as a plugin or copy in.
  • Package repeatable AI workflows into reusable local assets.
  • Reduce one-off prompt work with versioned skills, guardrails, and handoff files.

Where It Fits

This repository is part of a broader AI local-workbench operating model: reusable skills, local automation, auditable configuration, and repeatable delivery workflows.

Technical Overview

  • Primary language: JavaScript
  • Detected stack: JavaScript
  • Default branch: main
  • Visibility: PUBLIC
  • License: MIT License

Repository Map

  • scripts
  • tests
  • .claude-plugin
  • .claude
  • CONTRIBUTING.md
  • LICENSE
  • README.md
  • SECURITY.md
  • agents
  • commands
  • contexts
  • examples

Quick Start

No universal setup command is declared yet. Start by inspecting the repository map above and the project-specific scripts or docs committed with the code.

Operating Notes

  • Keep real credentials out of the repository. Use local environment files, GitHub repository secrets, or the deployment platform secret manager.
  • If a .env.example file exists, treat it as documentation only; never commit filled-in .env files.
  • Before publishing screenshots, demos, or client examples, remove private names, internal paths, account IDs, and API endpoints.
  • The Repository Hygiene workflow is a lightweight guardrail, not a replacement for product-specific tests.

Delivery Checklist

  • README describes the user, business outcome, and operating boundary.
  • Setup or preview commands are current and do not rely on private machine state.
  • No real secrets, private user data, or machine-local state are tracked.
  • Screenshots, demos, or sample outputs are safe to share publicly when the repository is public.
  • Product-specific tests or smoke checks are documented before production use.

Roadmap

  • Tighten the fastest path from clone to useful demo.
  • Add project-specific screenshots, sample outputs, or a short walkthrough where useful.
  • Promote repeated manual steps into scripts, tests, or documented workflows.
  • Keep security, privacy, and licensing boundaries explicit as the project evolves.

Maintainer Notes

Maintained by Tony Sheng. This README is written as a business-facing handoff: it should help a future collaborator, client, or reviewer understand why the repository exists, how to inspect it, and what must be true before it is reused or shipped.

Ver o original no GitHub

Bom para

Relacionados