agentleFS
frankxaifrankxai/agentic-creator-os/instances/CLAUDE.md

agentic-creator-os / instances

CLAUDE.md10 starsChanged 7 months agoApache-2.0View on GitHub

This directory contains project-specific configurations that customize Agentic Creator OS behavior. Instances define how Agentic Creator OS behaves for different projects: - Brand voice and tone - Enabled skills and workflows - Evaluation settings - Integration preferences Each instance has a config.json with: Settings: - Tone: Provocative, visionary - Brand: FrankX - Skills: All enabled - Evaluation: Strict mode, benchmark against top performers Use for: Creating FrankX-branded content Settings: - Tone: Friendly, educational - Brand: Demo Brand - Skills: content,…

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When working with instances:

    line 148
  2. Distinctive:

    Use enabled skills: - Don't use disabled skills

    line 152
  3. Distinctive:

    Know the keywords: - Use approved terminology

    line 154

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md
<claude-mem-context> # Instances Directory - Project Configurations

This directory contains project-specific configurations that customize Agentic Creator OS behavior.

What Are Instances?

Instances define how Agentic Creator OS behaves for different projects:

  • Brand voice and tone
  • Enabled skills and workflows
  • Evaluation settings
  • Integration preferences

Directory Structure

instances/
├── CLAUDE.md              ← YOU ARE HERE
├── _template/             ← Template for new projects
│   ├── config.json        ← Template configuration
│   └── config.ts          ← Config utilities
├── frankx/                ← FrankX project
│   └── config.json        ← FrankX configuration
└── demo-project/          ← Demo project
    └── config.json        ← Demo configuration

Instance Configuration

Each instance has a config.json with:

{
  "name": "Project Name",
  "slug": "project-slug",
  "version": "1.0.0",
  "brand": {
    "name": "Brand Name",
    "voice": {
      "tone": "professional",
      "personality": ["trait1", "trait2"],
      "keywords": ["word1", "word2"],
      "avoidKeywords": ["word3"]
    },
    "colors": {
      "primary": "#123456",
      "secondary": "#654321",
      "accent": "#abcdef"
    }
  },
  "directories": {
    "workflows": "workflows",
    "templates": "templates",
    "skills": "skills",
    "mcpServers": "mcp-servers"
  },
  "integrations": {
    "opencode": true,
    "claudeCode": true,
    "gemini": false
  },
  "skills": {
    "enabled": ["content", "marketing"],
    "custom": []
  },
  "workflows": {
    "enabled": ["social-media", "content"],
    "custom": []
  },
  "evaluation": {
    "enabled": true,
    "strictMode": false,
    "benchmarkAgainst": "industry-average"
  }
}

Available Instances

frankx

Purpose: FrankX brand content

Settings:

  • Tone: Provocative, visionary
  • Brand: FrankX
  • Skills: All enabled
  • Evaluation: Strict mode, benchmark against top performers

Use for: Creating FrankX-branded content

demo-project

Purpose: Demo and testing

Settings:

  • Tone: Friendly, educational
  • Brand: Demo Brand
  • Skills: content, marketing only
  • Evaluation: Standard mode

Use for: Testing workflows, learning the system

_template

Purpose: Template for new projects

Use for: Creating new project instances

How to use:

cp -r instances/_template instances/my-new-project
# Edit instances/my-new-project/config.json

Creating a New Instance

  1. Copy template:
    cp -r instances/_template instances/my-project
  2. Edit config.json:
    • Change name, slug
    • Set brand voice
    • Enable/disable skills
    • Configure workflows
  3. Use the instance: The system will automatically detect which instance to use based on your project.

Instance Selection

The system selects an instance based on:

  1. Project directory name - Matches instance slug
  2. Manual override - Specify in configuration
  3. Default instance - Falls back to frankx

Brand Voice Configuration

SettingDescriptionOptions
toneOverall voiceprofessional, casual, authoritative, friendly, provocative
personalityTraitsinnovative, helpful, reliable, cutting-edge, etc.
keywordsApproved terms["AI", "automation", "workflow"]
avoidKeywordsTerms to avoid["spammy", "clickbait"]

For AI Agents

When working with instances:

  1. Check the instance - Know which project you're working on
  2. Respect brand voice - Match the configured tone
  3. Use enabled skills - Don't use disabled skills
  4. Follow evaluation rules - Strict mode = higher standards
  5. Know the keywords - Use approved terminology

Loading Instances

import { getInstanceConfig, listInstances } from './instances/_template/config.ts';

// List all instances
const instances = await listInstances();
// Returns: [{ name, description, path }]

// Load specific instance
const config = await getInstanceConfig('frankx');
// Returns: ProjectConfig object

Related Directories

DirectoryPurpose
skills/Skills customized by instance
workflows/Workflows customized by instance
templates/Templates customized by instance
mcp-servers/Tools customized by instance

Instances personalize Agentic Creator OS for each project. Know your instance, respect its rules. </claude-mem-context>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.