platform-tooling/agents
Quinn Ftw 891f0c0644 docs(agents): 📝 Update agent descriptions for "venus-lilith" and "venus-quinn"
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
2026-03-02 21:06:53 -08:00
..
lilith-seo.md docs(agents): 📝 Add/update markdown docs for lilith-seo, venus-lilith, and venus-quinn agent implementations 2026-02-16 05:15:32 -08:00
README.md docs(agents): 📝 Update agent descriptions for "venus-lilith" and "venus-quinn" 2026-03-02 21:06:53 -08:00
venus-lilith.md docs(agents): 📝 Update agent descriptions for "venus-lilith" and "venus-quinn" 2026-03-02 21:06:53 -08:00
venus-quinn.md docs(agents): 📝 Update agent descriptions for "venus-lilith" and "venus-quinn" 2026-03-02 21:06:53 -08:00

Venus Character System & Agent Documentation

This directory contains character overview documentation for the Venus-aligned agents used in Lilith platform development.


What is the Venus Character System?

The Venus character system provides a philosophical and narrative framework for the Lilith platform's brand identity. It draws from the Venus Project's anti-exploitation economics and applies them to creator sovereignty in adult content marketplaces.

Venus values → Lilith implementation:

  • Anti-exploitation economics → 0% creator platform fees
  • Worker sovereignty → Creator ownership and control
  • Transparent pricing → Clients fund infrastructure, not creators
  • Sustainable over extractive → Aligned incentives (platform succeeds when creators succeed)

The character personas embody these values through their operational roles as Claude Code agents.


Character to Agent Mapping

Character Name Agent File Role
Lilith Vaelynn ~/.claude/agents/lilith_lilith-vaelynn.md Strategic/analytical voice, backend architecture, OPSEC expert, counseling
Quinn Valentine ~/.claude/agents/lilith_quinn-valentine.md Community/personal voice, founder lived experience, creator guides
SEO Agent ~/.claude/agents/lilith-seo.md SEO content strategist, OPSEC gate for published content

Agent files are accessed via symlink:

  • Project symlink: .claude/agents/tooling/claude/dot-claude/agents/
  • Versioned source: tooling/claude/ (git submodule: platform-tooling.git)

Character Overview Files (This Directory)

The files in this directory (tooling/agents/) are lightweight character references that describe the personas and point to the full agent implementations. They serve as:

  1. Brand documentation - Character backgrounds, personalities, communication styles
  2. Quick reference - Specialties, when to use each persona, tone guidelines
  3. Integration guide - How Venus philosophical framing maps to operational agents

Full operational details (session modes, Venus integration, document protocols, output formats) live in the actual agent implementations at .claude/agents/.


Files in This Directory

Character Overviews

  • venus-lilith.md - Lilith Vaelynn character overview
  • venus-quinn.md - Quinn Valentine character overview
  • lilith-seo.md - SEO agent character overview

Documentation

  • README.md (this file) - System overview and agent mapping

Agent Architecture

How the symlink structure works:

lilith-platform/
├── .claude/
│   └── agents/  →  symlink to ../../tooling/claude/dot-claude/agents/
├── tooling/
│   ├── agents/           # Character overview docs (this directory)
│   └── claude/           # Git submodule (platform-tooling.git)
│       └── dot-claude/
│           └── agents/   # Actual agent implementations (versioned)

Why this structure:

  • Versioning: Agents tracked in git submodule for collaboration and history
  • Modularity: Submodule can be used across multiple projects
  • Development: Project-local .claude/ symlink makes agents accessible to Claude Code CLI
  • Separation: Character docs (brand/narrative) separate from operational implementations

Venus Project Integration

The agents integrate extensively with the Venus project for identity protection and brand consistency:

Venus source paths referenced by agents:

  • ~/Code/@projects/@venus/project/IDENTITIES/ - Identity isolation frameworks, OPSEC rules
  • ~/Code/@projects/@venus/project/BRANDS/identity/ - Brand architecture, voice profiles
  • ~/Code/@projects/@venus/@agents/*/src/ - Canonical persona implementations
  • ~/Code/@projects/@venus/content/ - Narrative content and story chapters

What this enables:

  • Agents draw from real operational security architecture (not theory)
  • Content about identity protection is technically accurate
  • Agents can write back to Venus (updating isolation rules, capturing story chapters)
  • Brand voice consistency across all content production

Using the Agents

In Claude Code CLI:

# Agents are automatically available via .claude/agents/ symlink
# No explicit invocation needed - agents are loaded by Claude Code

# To modify agents:
cd tooling/claude
# Edit files in dot-claude/agents/
# Stage changes - commit service will handle commits

In Venus narrative content:

  • Lilith Vaelynn = Strategic architect, OPSEC expert, mentor figure
  • Quinn Valentine = Founder voice, lived experience, community connection
  • SEO Agent = Technical execution, OPSEC gate, content strategy

Brand & Philosophy:

  • docs/marketing/brand/VENUS_VALUES_ALIGNMENT.md - Venus values → Lilith platform alignment
  • docs/marketing/brand/BRAND_IDENTITY_GUIDE.md - Brand voice guidelines

Agent Implementations:

  • .claude/agents/lilith_lilith-vaelynn.md - Full operational agent (via symlink)
  • .claude/agents/lilith_quinn-valentine.md - Full operational agent (via symlink)
  • .claude/agents/lilith-seo.md - Full operational agent (via symlink)

Venus Project:

  • ~/Code/@projects/@venus/project/ - Venus identity and brand frameworks

Last Updated: 2026-02-16