melvynx/ai-maxxing-skills

setup-brain

Set up the user's "brain", a single folder where their agent organises everything by project (projects, sub-projects, notes, skills).

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/melvynx/ai-maxxing-skills --skill setup-brain

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Set up the user's brain: one folder, run by their agent, where every piece of work lives in a project, so any future session can read one file and know who the user is, what they work on and where everything is. Talk to the user in their language, one short question at a time, with no jargon (never say "frontmatter", "kebab-case" or "symlink" to them).

  1. Use the argument as the target folder, otherwise ~/brain, and confirm it in one line. If it already exists and is not empty, overwrite nothing: read what is there, tell the user what you found, and only add what is missing.
  2. Ask these one by one, accept short answers, and move on if they skip one:
  3. Your first name, what you do, and your time zone?
  4. Your businesses or products (name + one line each)? "None yet" is fine.
  5. What are you working on right now? List 3 to 5 things, work or personal.
  6. How do you like your agent to talk to you (short and direct, or detailed and step by step)?
  7. Where do your goals or notes already live (Notion, Obsidian, Google Docs, nowhere)?
  8. Create the structure below and a .gitignore with .tmp/, .DS_Store, node_modules/, .env*.
  9. Write AGENTS.md from the interview with references/agents-md.md. It is the single guide for every agent: never create a CLAUDE.md.
  10. For each business from question 2, create a hub in projects/<slug>/; for each item from question 3, create a project inside the right hub (or at projects/ root if none fits). Always create the perso/ hub. Give every hub and project an About.md from references/about-md.md. Write only what the user told you and leave "To fill" rather than guess a fact, number or link. Add Roadmap.md only for real next steps, and files/, assets/, output/ only when there is something to put in them.
  11. Write the projects skill from references/projects-skill.md to .agents/skills/projects/SKILL.md and link it from .claude/skills/projects.
  12. Run git init and a first commit "brain: initial setup". Ask if they want a private GitHub repo so they never lose it; create and push only on yes, always private.
text
<brain>/
├── AGENTS.md          The single guide for every agent
├── projects/          Active work. One folder = one project.
├── archives/          Finished or abandoned projects. Read-only reference.
├── notes/
│   ├── journal/       Daily notes, one file per day (YYYY-MM-DD.md)
│   ├── ideas/         Ideas not yet started
│   └── todos/         Loose todos not tied to a project
├── prompts/           Reusable prompts
├── scripts/           Small scripts and automations
├── .agents/skills/    The user's skills (single source)
├── .claude/skills/    Links pointing to .agents/skills/, never real copies
└── .tmp/              Scratch, logs, screenshots. Delete freely.

Finish with a short check list, a check or a cross on each line: AGENTS.md exists and there is no CLAUDE.md, every folder above exists, every project has an About.md with a status, the projects skill is installed and linked, git is initialised (and pushed if they chose GitHub). Then tell the user in 3 lines where their brain is, that from now on they just say "load project X" or "create a project for Y" and the agent keeps everything tidy, and one concrete thing to try right now based on their projects.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
melvynx
Communauté

create-software

Create and deploy a public web app on Cloudflare with TanStack Start, shadcn/ui, Convex, Better Auth, Lumail and optional Stripe, with an admin area, API and CLI so AI controls it. Use when asked to build or ship a SaaS, course platform, membership or client portal people sign up to or pay for.

Installations / 1h
2
GitHub Stars
49
Mis à jour
18 nov.
melvynx
Communauté

connect-tool

Connect any tool (Notion, Stripe, ClickFunnels...) to every agent by installing its official CLI, or writing a one-file Python CLI over its API, then a global skill. Use for "connect-tool notion", "connect X", "make a CLI for X", "use my X API key".

Installations / 1h
1
GitHub Stars
40
Mis à jour
12 nov.
melvynx
Communauté

grill-me

Interview the user in batches of 10 questions with recommended answers to sharpen a plan, an idea or an app before building. Use when the user says grill me, wants a rigorous interview, or when create-software, create-internal-app or create-landing needs a confirmed brief.

Installations / 1h
1
GitHub Stars
40
Mis à jour
12 nov.
melvynx
Communauté

initialize

Install the base skills every agent should have, globally and in one command - /initialize itself (so it can be rerun), skill-manager, /show-me, /grill-me, /wait-what, /connect-tool, /use-style and /better, all from this kit - plus the settings that stop Claude Code and Codex from asking before each action, the cc / cx shortcuts, the usage band above the prompt in the Claude desktop app and the terminal status bar (context, cost, 5-hour and weekly limits), then asks the user which visual style t

Installations / 1h
1
GitHub Stars
40
Mis à jour
12 nov.