/ Verzeichnis / Playground / ai-first-toolkit
● Community techwolf-ai ⚡ Sofort

ai-first-toolkit

von techwolf-ai · techwolf-ai/ai-first-toolkit

A skills pack that audits, re-engineers, and bootstraps projects following AI-first design principles.

ai-first-toolkit is a multi-skill bundle for Claude Code and Codex that looks at your project through an AI-first lens: is the codebase easy for an agent to navigate, edit, and reason about? It includes skills for AI-readiness audits, refactoring toward clear structure, and bootstrapping new projects with the right scaffolding from day one.

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

ai-first-toolkit-skill.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "ai-first-toolkit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/techwolf-ai/ai-first-toolkit",
        "~/.claude/skills/ai-first-toolkit"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "ai-first-toolkit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/techwolf-ai/ai-first-toolkit",
        "~/.claude/skills/ai-first-toolkit"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "ai-first-toolkit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/techwolf-ai/ai-first-toolkit",
        "~/.claude/skills/ai-first-toolkit"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "ai-first-toolkit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/techwolf-ai/ai-first-toolkit",
        "~/.claude/skills/ai-first-toolkit"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "ai-first-toolkit-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/techwolf-ai/ai-first-toolkit",
        "~/.claude/skills/ai-first-toolkit"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json
{
  "context_servers": {
    "ai-first-toolkit-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/techwolf-ai/ai-first-toolkit",
          "~/.claude/skills/ai-first-toolkit"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add ai-first-toolkit-skill -- git clone https://github.com/techwolf-ai/ai-first-toolkit ~/.claude/skills/ai-first-toolkit

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: ai-first-toolkit

How to audit a codebase for AI-agent readiness

👤 Tech leads preparing a codebase for heavy AI-assisted work ⏱ ~45 min intermediate

Wann einsetzen: Before the team commits to doing a lot of feature work through Claude or Codex.

Voraussetzungen
  • Skill cloned — git clone https://github.com/techwolf-ai/ai-first-toolkit ~/.claude/skills/ai-first-toolkit
Ablauf
  1. Run the audit
    Audit this repo for AI-agent readiness. Score each dimension and list the top 5 friction points.✓ Kopiert
    → Dimension scores + specific files to fix
  2. Prioritize fixes
    Which of those fixes would give the biggest agent-effectiveness lift per hour of work?✓ Kopiert
    → Ranked list with effort/impact
  3. Apply the top fix
    Apply fix #1 end-to-end — edit files, update docs, add tests.✓ Kopiert
    → Diff + confirmation

Ergebnis: A concrete improvement plan and at least one applied fix making the repo friendlier to AI agents.

Fallstricke
  • Audit turns into a generic 'improve docs' blob — Ask for file:line level findings, not abstract advice
Kombinieren mit: filesystem · github

Bootstrap a new AI-friendly project

👤 Founders or ICs starting a new repo ⏱ ~30 min beginner

Wann einsetzen: Day zero of a new project, before you pick bad defaults that will haunt you.

Ablauf
  1. State the project
    Bootstrap a new TypeScript API project using ai-first-toolkit defaults. Purpose: internal billing API.✓ Kopiert
    → Proposed folder structure, tsconfig, scripts, README skeleton
  2. Scaffold the files
    Create the files. Include AGENTS.md and CLAUDE.md with the relevant codebase notes.✓ Kopiert
    → Repo files materialized
  3. First commit
    Initialize git and make the first commit with a clean message.✓ Kopiert
    → Clean initial repo

Ergebnis: A new repo that's friendly to both humans and AI agents from commit 0.

Fallstricke
  • Scaffolding imports dependencies you don't want — Ask Claude to list dependencies before installing — accept each one
Kombinieren mit: github · filesystem

Re-engineer a messy module for AI readability

👤 Engineers paying down tech debt one module at a time ⏱ ~60 min advanced

Wann einsetzen: You've isolated a module that Claude keeps getting wrong — usually a sign its structure isn't agent-legible.

Ablauf
  1. Diagnose the module
    Look at src/billing/. What about this code makes it hard for an agent to edit safely?✓ Kopiert
    → Specific red flags: indirection, hidden state, long functions
  2. Plan the refactor
    Propose a 3-step refactor that improves agent-legibility without changing public API.✓ Kopiert
    → Stepwise plan with diff sketches
  3. Execute step 1
    Apply step 1. Keep tests green.✓ Kopiert
    → PR-sized diff

Ergebnis: A module that Claude can actually reason about on the next iteration.

Fallstricke
  • Over-refactor and break behaviors you didn't mean to — Insist on public API stability and run tests after each step
Kombinieren mit: filesystem · github

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

ai-first-toolkit-skill + filesystem

Audit scans the repo; filesystem is needed to actually read it

Walk the repo and score AI-readiness; report findings file-by-file.✓ Kopiert
ai-first-toolkit-skill + github

Open a PR with the proposed AGENTS.md / CLAUDE.md additions

Apply the audit's top 3 fixes and open a PR titled 'AI-first improvements'.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
ai-readiness-audit repo root Pre-investment in AI-heavy workflows 0
ai-first-bootstrap project spec (lang, purpose, stack) Greenfield projects 0
re-engineer-module module path + goals When a module resists agent edits 0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
none beyond your LLM provider
Tokens pro Aufruf
5–20k for an audit of a medium repo
Kosten in €
free, open source
Tipp
Scope audits to a subtree rather than the whole monorepo

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: none
Datenabfluss: none beyond what filesystem/github tools do

Fehlerbehebung

Häufige Fehler und Lösungen

Audit is too abstract

Re-prompt with a concrete dimension: 'evaluate just the test layout' or 'just the module boundaries'.

Bootstrap picks wrong language

Always state language+runtime+build tool in the first prompt.

Alternativen

ai-first-toolkit vs. andere

AlternativeWann stattdessenKompromiss
init (built-in)You just need a CLAUDE.md and don't care about the restNarrower scope
antivibe-skillYou want the opposite lens — critique of AI-shaped sludgeDiagnostic, not prescriptive

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen