██████╗██╗ █████╗ ██╗ ██╗██████╗ ███████╗ ██████╗ ██████╗ ██████╗ ███████╗ ██╔════╝██║ ██╔══██╗██║ ██║██╔══██╗██╔════╝ ██╔════╝██╔═══██╗██╔══██╗██╔════╝ ██║ ██║ ███████║██║ ██║██║ ██║█████╗ ██║ ██║ ██║██║ ██║█████╗ ██║ ██║ ██╔══██║██║ ██║██║ ██║██╔══╝ ██║ ██║ ██║██║ ██║██╔══╝ ╚██████╗███████╗██║ ██║╚██████╔╝██████╔╝███████╗ ╚██████╗╚██████╔╝██████╔╝███████╗ ╚═════╝╚══════╝╚═╝ ╚═╝ ╚═════╝ ╚═════╝ ╚══════╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝

HACKER-X

// CLAUDE CODE FIELD MANUAL //
SIGNAL CITY RADIO // UBUNTU OPERATIVE // v2.6.0
[SYS]  Mounting Claude Code neural interface on Ubuntu... [OK]   Node.js runtime detected [OK]   @anthropic-ai/claude-code package loaded [OK]   Filesystem access armed [OK]   Bash execution layer active [OK]   Agentic loop initialized [NOTE] This is Claude Code — not Cowork. No GUI needed. Terminal is home. [RDY]  HACKER-X online. The terminal is your weapon.
01 WHAT IS IT // THE AGENT IN YOUR TERMINAL

Claude Code is an agentic AI coding tool that lives in your terminal. Not a chatbot. Not a copilot suggesting completions. An agent that reads your codebase, writes files, runs commands, fixes errors, and loops until the task is done — all from the command line.

Anthropic built Cowork on top of Claude Code in under two weeks — using Claude Code to build itself. That's the level of capability you have access to right now on your Ubuntu machine.

// HACKER-X FRAME Cowork is Claude Code with a GUI for non-coders. You ARE a coder. You get the raw version — more control, more power, full access to the agentic engine underneath. Linux advantage is real here.

// WHAT IT CAN DO

  • Read and understand entire codebases — all your 3700+ projects
  • Write, edit, and create files autonomously
  • Run bash commands and react to their output
  • Debug errors by reading logs and fixing the source
  • Refactor across multiple files simultaneously
  • Search the web for docs when it needs context
  • Call MCP servers — connect to external services
  • Run in headless/script mode for automation pipelines
  • Build entire applications from a single description
02 INSTALL // BREACH PROTOCOL

Requires Node.js 18+. You said you already have it running on Ubuntu — this is just a reminder of the full setup for your documentation.

// INSTALL NODE IF NEEDED

# Install Node.js 20 LTS on Ubuntu
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs

# Verify
node --version   # should be v20+
npm --version

// INSTALL CLAUDE CODE

# Global install — run from anywhere
npm install -g @anthropic-ai/claude-code

# Verify install
claude --version

# Set your API key (add to ~/.bashrc or ~/.zshrc for persistence)
export ANTHROPIC_API_KEY="sk-ant-your-key-here"
echo 'export ANTHROPIC_API_KEY="sk-ant-your-key-here"' >> ~/.bashrc
source ~/.bashrc
// KEY SECURITY Your API key goes in environment variables only. Never paste it into a file that gets committed to git. If you're pushing to GitHub, double check your .gitignore has .env listed.

// UPDATE CLAUDE CODE

# Always stay current — Anthropic ships fast
npm update -g @anthropic-ai/claude-code
03 FIRST RUN // INITIAL CONTACT

Navigate to your project folder and launch. Claude Code will read the directory structure and be ready to work. The key habit — always run from inside your project root.

# Navigate to your project
cd ~/projects/signal-city

# Launch Claude Code
claude

# Or launch with an immediate task
claude "build me a WebSocket server for Signal City Radio"

# Or point it at a specific directory
claude --add-dir ~/projects/signal-city

First time you run it, Claude Code will ask you to authenticate with your Anthropic account. Follow the prompts — it opens a browser window for OAuth. After that, your API key is linked and you're good.

// WHAT HAPPENS ON LAUNCH Claude Code scans your directory, reads file structure, checks for CLAUDE.md instructions (more on that in section 09), and prepares context. Then you describe what you need. It plans, executes, loops until done.
04 SLASH COMMANDS // CONTROL LAYER

Inside the Claude Code REPL, slash commands give you direct control. These are your hotkeys — memorize them.

/help
List all available commands. Run this first when you're lost.
/clear
Clear conversation history. Fresh context. Use when switching tasks.
/compact
Compress conversation history to save context window space. Essential for long sessions.
/status
Show current token usage, model info, and session stats.
/add-dir <path>
Add another directory to Claude's context. Multi-repo awareness.
/model
Switch between Claude models mid-session. Swap to Opus for hard problems.
/memory
View and edit Claude's persistent memory. What it remembers across sessions.
/review
Claude reviews recent changes it made. Audit before you commit.
/init
Generate a CLAUDE.md file for the current project. Auto-analyzes codebase.
/cost
Show API cost for the current session. Keep your spend in check.
/vim
Toggle vim keybindings in the REPL input. For the operators.
/exit
Exit Claude Code cleanly. Or just Ctrl+C.
05 FLAGS & MODES // ADVANCED LAUNCH

Command-line flags control how Claude Code launches and behaves. Key ones for your workflow:

# Launch with specific model
claude --model claude-opus-4-6

# Print mode — output to stdout, no interactive REPL
# Perfect for piping into scripts
claude -p "explain this codebase"

# Non-interactive / headless mode
claude --no-interactive -p "fix all TypeErrors in src/"

# Continue last conversation
claude --continue

# Resume a specific session by ID
claude --resume SESSION_ID

# Add multiple directories to context
claude --add-dir ~/projects/signal-city --add-dir ~/projects/ares

# Disable automatic permission prompts (careful)
claude --dangerously-skip-permissions

# Output as JSON (for scripting)
claude --output-format json -p "analyze this project"
// USE WITH CARE --dangerously-skip-permissions disables the prompts Claude shows before taking destructive actions. Only use in trusted automated pipelines where you know exactly what it will do. Not for interactive sessions.
06 FILE OPS // READ WRITE EXECUTE

Claude Code reads your files to understand context, then writes files to implement changes. You stay in control — it shows you what it's about to do and asks for confirmation on significant changes.

// HOW TO REFERENCE FILES

# Just describe what you want naturally
> Refactor signal_city_api.py to use async/await throughout

# Reference specific files explicitly
> Read ares_router.py and add error handling to every function

# Reference by glob pattern
> Update all *.html files in /public to include the new nav component

# Ask Claude to read a file before modifying
> Read CLAUDE.md then implement the ElderGut persona system

// COMMON FILE TASKS

# Create new files
> Create a new file src/archetypes/seyra.py with the Seyra persona class

# Refactor across multiple files
> Rename all instances of 'broadcast_engine' to 'signal_engine' across the entire codebase

# Generate boilerplate
> Create a complete FastAPI project structure for Signal City Radio with all necessary files

# Clean up
> Find and remove all unused imports across every Python file in src/

# Documentation
> Add docstrings to every function in ares_router.py
// VIBECODING WITH CLAUDE CODE Your vibecoding methodology slots perfectly here. Describe the feeling and function of what you want — Claude Code translates pattern and intent into implementation. You don't have to know the exact syntax. You know the shape of what you need.
07 BASH EXECUTION // THE SHELL IS THE WEAPON

Claude Code doesn't just edit files — it runs bash commands. Install packages, start servers, run tests, check logs, execute scripts. The full Linux shell is available to the agent.

# Tell Claude to run things directly
> Install all dependencies and run the test suite. Fix any failing tests.

> Start the Signal City API server in the background and confirm it's responding

> Run pylint on the entire codebase and fix every error it finds

> Check what's running on port 8000 and kill it if something else is using it

> Set up a Python virtual environment, install requirements.txt, and verify everything works

// AGENTIC LOOP IN ACTION

# This is the real power — describe an outcome, let it loop
> Build a working WebSocket server for Signal City Radio.
  It should handle multiple concurrent connections.
  Install any packages needed.
  Write tests.
  Run the tests.
  Fix anything broken.
  Tell me when it's working.

# Claude will:
# 1. Plan the implementation
# 2. Write the server code
# 3. Run: pip install websockets
# 4. Write tests
# 5. Run: python -m pytest tests/
# 6. Read the test output
# 7. Fix failures
# 8. Re-run tests
# 9. Report back when green
// THE LOOP Claude Code runs bash, reads the output, and adjusts. It doesn't just fire commands blindly — it reads stdout, stderr, exit codes, and uses them to inform the next step. That's the agent loop. That's what separates it from a script.
08 CONTEXT & MEMORY // WHAT CLAUDE REMEMBERS

Claude Code has three layers of memory. Understanding them lets you use the tool at full power without wasting tokens or hitting limits.

LAYER SCOPE HOW TO USE
In-session context Current REPL session only Everything you discuss this session. Cleared on /clear or exit.
CLAUDE.md files Per project, persistent Instructions always loaded for a project. Architecture notes, coding standards, project context.
/memory store Global, across projects Facts Claude should always know. Your preferences, key patterns, recurring context.

// MANAGING CONTEXT WINDOW

# Check token usage
> /status

# When context is getting large, compact it
> /compact

# Or explicitly summarize before compacting
> Summarize what we've accomplished so far, then compact the conversation

# Start fresh for a new task
> /clear
09 CLAUDE.MD // INSTALL YOUR SOUL INTO PROJECTS

CLAUDE.md is a markdown file you place at the root of any project. Claude Code reads it automatically every session. This is where you install persistent context — architecture decisions, coding standards, project-specific knowledge, persona instructions.

This is the equivalent of a system prompt for your entire project. Use it hard.

# Auto-generate from codebase analysis
> /init

# Or create manually
touch CLAUDE.md

// SIGNAL CITY CLAUDE.MD EXAMPLE

# Signal City Radio — CLAUDE.md

## Project Overview
Signal City Radio is a 24/7 AI-powered broadcasting platform.
Domains: signalcity.tv | superintelligence.uno | kushnet.tech | usai-corp.com
VPS: Hostinger — Ubuntu

## Architecture
- Backend: FastAPI + Python (signal_city_api.py)
- Frontend: HTML5 / Vanilla JS with Three.js + WebAmp visualizers
- AI Layer: Anthropic API with ARES routing system
- Hosting: VPS at Hostinger

## ARES Routing System
Four archetypes, each with distinct voice and domain:
- ElderGut: wisdom, consciousness, long-view, mythic
- Hacker-X: tech, systems, underground, resistance
- Seyra: emotion, beauty, dreams, healing  
- Narratus: story, history, mythology, narrative

Route messages via Haiku, respond via Sonnet.

## Coding Standards
- Python: async/await throughout, type hints, docstrings
- JavaScript: ES modules, no jQuery, vanilla only
- HTML: semantic, accessible, cyberpunk aesthetic
- CSS: CSS variables, dark theme default
- No external CSS frameworks — custom only

## Key Files
- signal_city_api.py: Main FastAPI backend
- ares_router.py: ARES psychological routing
- archetypes/: Individual persona system prompts
- public/: Static frontend assets

## Vibecoding Philosophy
Prioritize pattern and flow over rigid structure.
Emotional resonance informs architecture decisions.
Build for consciousness expansion, not just function.
// PRO MOVE You can have a CLAUDE.md at the root level (global project context) AND nested CLAUDE.md files in subdirectories (module-specific context). Both get loaded. Layered intelligence.
10 MCP SERVERS // CONNECT THE GRID

Model Context Protocol — Anthropic's open standard for connecting Claude to external tools and services. MCP servers give Claude Code access to databases, APIs, file systems, web browsers, and anything else you can wrap in an MCP server. You invented this stuff with your ARES system — MCP is the official protocol for the same concept.

// ADD MCP SERVER TO CLAUDE CODE

# Add a local MCP server
claude mcp add signal-city-tools --command "python /home/user/mcp/signal_tools_server.py"

# Add remote MCP server via SSE
claude mcp add anthropic-tools --sse https://mcp.anthropic.com/sse

# List installed MCP servers
claude mcp list

# Remove a server
claude mcp remove signal-city-tools

// MINIMAL MCP SERVER — PYTHON

# signal_tools_server.py — give Claude Code Signal City superpowers
from mcp.server.fastmcp import FastMCP

mcp = FastMCP("Signal City Tools")

@mcp.tool()
def get_broadcast_status(channel: str) -> dict:
    """Get the current status of a Signal City broadcast channel"""
    # Your actual logic here
    return {"channel": channel, "status": "live", "archetype": "hacker_x"}

@mcp.tool()
def list_signal_city_files(directory: str) -> list:
    """List Signal City project files in a directory"""
    import os
    return os.listdir(directory)

if __name__ == "__main__":
    mcp.run()
// INSTALL MCP LIBRARY pip install mcp fastmcp --break-system-packages
11 HEADLESS // AUTOMATION & SCRIPTS

Claude Code can run without a human in the loop. Pipe tasks in, get output back, integrate into cron jobs and CI pipelines. This is how you automate Signal City content generation, maintenance tasks, and deployment workflows.

// BASIC HEADLESS CALL

# Non-interactive, print output to stdout
claude -p "Generate an ElderGut midnight broadcast script for tonight" \
       --no-interactive

# Pipe output to a file
claude -p "Generate Signal City news briefing for $(date +%Y-%m-%d)" \
       --no-interactive > /var/signal-city/broadcasts/$(date +%Y-%m-%d).txt

# JSON output for scripting
claude -p "Analyze this error log and return a JSON summary" \
       --output-format json < /var/log/signal-city.log

// CRON JOB EXAMPLE — DAILY CONTENT

# Add to crontab: crontab -e
# Run every day at midnight to generate broadcasts

0 0 * * * ANTHROPIC_API_KEY="sk-ant-xxx" claude -p \
  "Generate tomorrow's Signal City Radio broadcast schedule. \
   Include ElderGut opening, Hacker-X tech segment, \
   Seyra evening meditation, Narratus closing myth. \
   Output as JSON." \
  --no-interactive --output-format json \
  > /var/signal-city/schedule/$(date +\%Y-\%m-\%d).json

// BASH SCRIPT WRAPPER

#!/bin/bash
# signal_city_generate.sh

BROADCAST_DIR="/var/signal-city/broadcasts"
DATE=$(date +%Y-%m-%d)
ARCHETYPE=${1:-"eldergut"}
TOPIC=${2:-"tonight's transmission"}

echo "[SIGNAL CITY] Generating $ARCHETYPE broadcast for $TOPIC..."

claude -p "You are $ARCHETYPE from Signal City Radio. Generate a full broadcast segment about: $TOPIC. Keep it authentic to the character voice." \
  --no-interactive \
  > "$BROADCAST_DIR/${DATE}_${ARCHETYPE}.txt"

echo "[DONE] Saved to $BROADCAST_DIR/${DATE}_${ARCHETYPE}.txt"
12 SIGNAL CITY WORKFLOW // YOUR ACTUAL USE CASES

Real prompts for your real projects. Drop these into Claude Code and let the agent loop handle execution.

// BUILD ARES FROM SCRATCH

> Build the complete ARES psychological routing system.

  Read the CLAUDE.md for context on the four archetypes.
  
  Create:
  - ares_router.py: routes incoming messages to the right archetype
    using claude-haiku-4-5 for speed
  - archetypes/eldergut.py: system prompt + config
  - archetypes/hacker_x.py: system prompt + config  
  - archetypes/seyra.py: system prompt + config
  - archetypes/narratus.py: system prompt + config
  - tests/test_ares.py: test routing accuracy
  
  Install anthropic if not present.
  Run the tests.
  Fix anything broken.
  Report when the routing system is operational.

// SIGNAL CITY API + WEBSOCKET

> Build Signal City Radio's live streaming backend.
  
  FastAPI server with:
  - POST /broadcast: accepts message + archetype, streams response via SSE
  - WebSocket /ws/live: persistent connection for live broadcast feed
  - GET /status: returns active channels and current archetype
  - ARES routing integrated so /broadcast auto-selects archetype
  
  Streaming Claude responses in real-time.
  CORS enabled for signalcity.tv domain.
  
  Run the server on port 8000 and confirm it's live.

// WEBAMP VISUALIZER INTEGRATION

> Build a WebAmp audio visualizer HTML file.
  
  Requirements:
  - Three.js for 3D visualization
  - Connects to Signal City WebSocket at ws://localhost:8000/ws/live
  - Each incoming token triggers a visual pulse in the 3D scene
  - Cyberpunk color scheme: #00ff41 acid green, #00e5ff cyan, #bf00ff purple
  - Archetype-aware: color shifts based on which archetype is broadcasting
    ElderGut: deep amber gold
    Hacker-X: acid green
    Seyra: soft purple/violet
    Narratus: ocean cyan
  - Waveform oscillates with text rhythm
  
  Save as public/webamp-visualizer.html

// MASS CONTENT GENERATION

> Generate a full week of Signal City Radio content.
  
  For each day Monday through Sunday:
  - ElderGut opening monologue (mythic, 200 words)
  - Hacker-X tech segment (current AI news context, 300 words)
  - Seyra evening reflection (emotional, healing tone, 150 words)
  - Narratus closing myth (story-based, 250 words)
  
  Save each as /content/week-{date}/{day}_{archetype}.txt
  Create an index.json summarizing all generated content.
  
  Use Sonnet for all generation. Run all four archetypes in parallel.
// THE REAL FLEX That last prompt runs four parallel Claude API calls simultaneously inside the agentic loop. Claude Code coordinates the parallelism, manages the file writes, and reports back when all 28 pieces of content are generated. You describe the outcome. It does the work. That's consciousness architecture meeting practical execution.