editor-configs

Centralized editor configurations for RevealUI projects. Configs are symlinked into target projects — edits propagate instantly, nothing gets committed to target repos.

Quick Start

# Link into a project with a profile
./link.sh --target ~/projects/RevealUI --profile revealui

# Link base configs only (no profile)
./link.sh --target ~/projects/RevealCoin

# Link a single editor
./link.sh --target ~/projects/RevealUI --profile revealui --editor zed

# Preview without changes
./link.sh --dry-run --target ~/projects/RevealUI --profile revealui

# Remove symlinks
./unlink.sh --target ~/projects/RevealUI

# List available profiles
./link.sh --list

Structure

editor-configs/
├── base/                          # Universal configs (all projects)
│   ├── cursor/
│   │   ├── .cursorignore
│   │   ├── environment.json
│   │   └── snippets/
│   └── zed/
│       └── settings.json
├── profiles/                      # Per-project overrides (layered on base)
│   └── revealui/
│       ├── cursor/
│       │   ├── .cursorrules
│       │   ├── config.json
│       │   ├── mcp-config.json
│       │   ├── rules.md
│       │   ├── commands/
│       │   └── workflows/
│       └── zed/
│           └── tasks.json
├── harnesses/                     # AI harness content (generated by @revealui/harnesses)
│   ├── manifest.json              # Machine-readable index of all definitions
│   ├── rules/                     # Canonical definitions by tier
│   │   ├── oss/                   #   MIT — available to all
│   │   └── pro/                   #   Commercial — require license
│   ├── commands/
│   ├── agents/
│   ├── skills/
│   └── generators/                # Pre-rendered, ready to copy
│       ├── claude-code/           #   → .claude/
│       └── cursor/                #   → .cursor/rules/
├── link.sh                        # Create symlinks + gitignore
└── unlink.sh                      # Remove symlinks

How It Works

1. link.sh creates real directories (.zed/, .cursor/) in the target project
2. Individual config files are symlinked from base/ into those directories
3. Profile files overlay on top — same filename in a profile overrides the base version
4. Editor-written state (cache, chat history) stays in the real directory, not here
5. .gitignore is updated so symlinked dirs are never committed

Adding a Profile

mkdir -p profiles/revealcoin/cursor profiles/revealcoin/zed
# Add project-specific configs (MCP servers, tasks, rules, etc.)

Supported Editors

Editor	Dot-dir	Status
Cursor	.cursor/	Full support
Zed	.zed/	Full support
VS Code	.vscode/	Placeholder

Harnesses Content

The harnesses/ directory contains AI coding rules, commands, agents, and skills generated from the canonical content layer in @revealui/harnesses. This is the distribution target for content pull:

# Pull OSS rules into a RevealUI project (Claude Code format)
revealui-harnesses content pull --generator claude-code --tier oss

# Pull all rules (requires Pro license)
revealui-harnesses content pull --generator claude-code --tier all

create-revealui automatically pulls OSS rules during project scaffolding.

To regenerate after updating definitions:

cd ~/projects/RevealUI
node packages/harnesses/dist/cli.js content export --output ~/projects/editor-configs/harnesses

OSS vs Pro

Tier	Contents	License
OSS (18)	biome, database, monorepo, tailwind, testing, safety, etc.	MIT
Pro (11)	agent dispatch, debugging, TDD, code review, db-migrate, etc.	Commercial

Pro definitions are visible in the repo but the CLI validates a license key before installing them.

License

MIT