Setup logo

Setup

CommunityPopular
Shpigford
setup

Get a new developer up and running with the Chops codebase — prerequisites, build, architecture, and common tasks.

Overview

PublisherShpigford
Repositorychops
Skill namesetup
Stars
1.9K
Forks
124
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Shpigford on GitHub. Read the source before you install it.

Installation

Install the Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Shpigford/chops/tree/main/.claude/skills/setup
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Shpigford/chops.git /tmp/chops
mkdir -p .claude/skills
cp -r /tmp/chops/.claude/skills/setup .claude/skills/setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Set up the Chops development environment and orient a new contributor to the codebase.

Instructions

Step 1: Check prerequisites

Verify these are installed. If any are missing, tell the user what to install and stop.

  1. macOS 15+ — sw_vers -productVersion (must be ≥ 15.0)
  2. Xcode CLI tools — xcode-select -p (if missing: xcode-select --install)
  3. Homebrew — which brew (if missing: direct them to https://brew.sh)
  4. xcodegen — which xcodegen (if missing: brew install xcodegen)

Step 2: Generate Xcode project

bash
xcodegen generate

This reads project.yml (the source of truth for all Xcode project settings) and generates Chops.xcodeproj. Re-run this anytime project.yml changes. Never edit the .xcodeproj directly.

Step 3: Build and run

bash
xcodebuild -scheme Chops -configuration Debug build

Or open in Xcode and hit Cmd+R:

bash
open Chops.xcodeproj

Step 4: Orient the developer

Share this architecture overview:

Entry point: Chops/App/ChopsApp.swift — sets up SwiftData ModelContainer (Skill + SkillCollection), starts Sparkle updater, injects AppState into environment.

State: Chops/App/AppState.swift — @Observable singleton holding UI state (selected tool, selected skill, search text, sidebar filter).

Models (SwiftData):

  • Chops/Models/Skill.swift — a discovered skill file, uniquely identified by resolved symlink path
  • Chops/Models/Collection.swift — user-created groupings of skills
  • Chops/Models/ToolSource.swift — enum of supported tools with display names, icons, colors, and filesystem paths

Services:

  • Chops/Services/SkillScanner.swift — probes tool directories, parses frontmatter, upserts into SwiftData. Deduplicates via resolved symlink paths.
  • Chops/Services/FileWatcher.swift — FSEvents via DispatchSource, triggers re-scan on file changes
  • Chops/Services/SkillParser.swift — dispatches to FrontmatterParser (.md) or MDCParser (.mdc)
  • Chops/Services/SearchService.swift — in-memory full-text search

Views: Three-column NavigationSplitView (Sidebar → List → Detail). Editor wraps NSTextView for native text editing. Cmd+S save via FocusedValues.

Key design decisions:

  • No sandbox — the app needs unrestricted filesystem access to read dotfiles across ~/
  • Symlink dedup — same file in multiple tool dirs shows as one skill with multiple tool badges
  • No test suite — validate manually by building, running, and observing

Scanned tool paths:

ToolPaths
Claude Code~/.claude/skills/, ~/.agents/skills
Cursor~/.cursor/skills/, ~/.cursor/rules
Windsurf~/.codeium/windsurf/memories/, ~/.windsurf/rules
Codex~/.codex
Amp~/.config/amp

Copilot and Aider detect project-level skills only (no global paths).

Common tasks to be aware of

Add a new tool: Add a case to ToolSource enum in Chops/Models/ToolSource.swift. Fill in displayName, iconName, color, globalPaths. Update SkillScanner if the tool uses a non-standard file layout.

Modify parsing: Frontmatter → Chops/Utilities/FrontmatterParser.swift. Cursor .mdc → Chops/Utilities/MDCParser.swift. Dispatch logic → Chops/Services/SkillParser.swift.

Change UI: Views are in Chops/Views/ (Sidebar/, Detail/, Settings/, Shared/). Main layout is Chops/App/ContentView.swift.

Important Rules

  • project.yml is the source of truth for Xcode settings — never edit .xcodeproj directly
  • Sparkle (auto-updates) is the only external dependency — pulled automatically via SPM
  • There is no test suite — always validate changes by building and running the app manually
  • The app runs without sandbox — this is intentional and required

Frequently asked questions

What does the Setup AI skill do?

Get a new developer up and running with the Chops codebase — prerequisites, build, architecture, and common tasks.

Why use Setup on TypingMind?

Because you install it once and use it with any model. Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Shpigford/chops/tree/main/.claude/skills/setup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Setup?

As many as you like. As long as a model supports skills, you can use Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Setup AI skill free?

It is published on GitHub by Shpigford. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇