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
- Distinctive: line 148
When working with instances:
- Distinctive: line 152
Use enabled skills: - Don't use disabled skills
- Distinctive: line 154
Know the keywords: - Use approved terminology
≈ “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.
Files
<claude-mem-context>
# Instances Directory - Project ConfigurationsThis 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 configurationInstance 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.jsonCreating a New Instance
- Copy template:
cp -r instances/_template instances/my-project - Edit config.json:
- Change name, slug
- Set brand voice
- Enable/disable skills
- Configure workflows
- 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:
- Project directory name - Matches instance slug
- Manual override - Specify in configuration
- Default instance - Falls back to frankx
Brand Voice Configuration
| Setting | Description | Options |
tone | Overall voice | professional, casual, authoritative, friendly, provocative |
personality | Traits | innovative, helpful, reliable, cutting-edge, etc. |
keywords | Approved terms | ["AI", "automation", "workflow"] |
avoidKeywords | Terms to avoid | ["spammy", "clickbait"] |
For AI Agents
When working with instances:
- Check the instance - Know which project you're working on
- Respect brand voice - Match the configured tone
- Use enabled skills - Don't use disabled skills
- Follow evaluation rules - Strict mode = higher standards
- 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 objectRelated Directories
| Directory | Purpose |
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>
In this repository131 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/commands/monitoring/agents.mdAGENTS.md
- .claude/skills/gstack/AGENTS.mdAGENTS.md
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/commands/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/skills/agentic-orchestration/CLAUDE.mdCLAUDE.md
- .claude/skills/cacos/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- .claude/skills/frankx-daily-execution/CLAUDE.mdCLAUDE.md
- .claude/skills/gstack/CLAUDE.mdCLAUDE.md
- .claude/skills/memory-guardian/CLAUDE.mdCLAUDE.md
- .claude/skills/newsletter/CLAUDE.mdCLAUDE.md
- .claude/skills/oci-services-expert/CLAUDE.mdCLAUDE.md
- .claude/skills/oracle-ai-architect/CLAUDE.mdCLAUDE.md
- .claude/skills/oracle-diagram-generator/CLAUDE.mdCLAUDE.md
- .claude/skills/research/CLAUDE.mdCLAUDE.md
- .claude/skills/swarm-advanced/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- drafts/CLAUDE.mdCLAUDE.md
- hub-generator/CLAUDE.mdCLAUDE.md
- mcp-servers/CLAUDE.mdCLAUDE.md
- outputs/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- workflows/CLAUDE.mdCLAUDE.md
- acos-metaSkill
- agentic-jujutsuSkill
- agentic-orchestrationSkill
- AI Architect NewsletterSkill
- ai-architectureSkill
- algorithmic-artSkill
- apod-to-shortSkill
- arxiv-space-paper-to-briefSkill
- book-publishingSkill
- brand-guidelinesSkill
- brand-voiceSkill
- cacosSkill
- canvas-designSkill
- Claude SDK ExpertSkill
- cosmic-mythic-overlaySkill
- creator-productivitySkill
- descript-operatorSkill
- doc-coauthoringSkill
- docxSkill
- excellence-book-writingSkill
- Framer ExpertSkill
- frankx-brandSkill
- FrankX Daily Execution SystemSkill
- frontend-designSkill
- game-developmentSkill
- github-code-reviewSkill
- github-multi-repoSkill
- github-project-managementSkill
- github-release-managementSkill
- github-workflow-automationSkill
- Greek PhilosopherSkill
- grok-harnessSkill
- gstackSkill
- The first 60 shown.
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.

