// GUIDES

How to Use


How to Use

The skillsets are plain markdown — every modern AI coding assistant accepts them in some form. The pattern is always the same: tell the assistant where the files live, and it uses them as authoritative reference whenever you ask about Isabyte.

The examples below use isabyte-react-skillsets.zip; substitute your bundle's name (isabyte-vue-…, isabyte-angular-…, isabyte-reactnative-…, isabyte-flutter-…, or isabyte-claude-skillsets.zip for the master deep-dive bundle).

With Claude Code (CLI)

Claude Code automatically loads skill files from your project's .claude/skills/ directory.

unzip isabyte-react-skillsets.zip -d .claude/skills/

Tip — place skill files in ~/.claude/skills/ to make them available across all your projects.

With Claude Projects (claude.ai)

  1. Open your Claude project at claude.ai
  2. Go to Project Knowledge
  3. Upload the .md files from the zip

With ChatGPT (Custom GPTs / Projects)

  1. Create a Project (or a Custom GPT in the GPT Builder)
  2. Open the project's Files panel
  3. Upload all .md files from the zip — ChatGPT indexes them for retrieval

With Cursor / Windsurf / VS Code agents

IDE-integrated assistants pick up project documentation automatically. Drop the .md files anywhere in the workspace (a docs/isabyte/ folder is common) and reference them in chat. For Cursor, add them as global Rules.

With any LLM API directly

For custom integrations, include the relevant skill file contents in your system prompt or as context documents. Works with the Claude API, OpenAI API, Gemini API, or any other LLM endpoint.

Want a zero-setup option? The Isabyte MCP Server ships the same corpus as a Docker image exposing the Model Context Protocol — connect any MCP-aware client and skip the file-shuffling step entirely.

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please reload the page.