Strategic Thinking + Execution.

Jules helps frame decisions, preserve context, and execute across code, research, publishing, reporting, and handoffs with reviewable evidence.

🦊 Jules

Thinks with you

Strategy, decisions, challenging assumptions, decomposition. Socratic dialogue, adversarial review, and a written trail for what changed.

  • Surfaces blind spots and second-order effects
  • Disagrees when it sees a better path
  • Connects today's work to long-term goals

Then executes

Software, content, research, deploys, reporting — one system, same context. Decisions flow from thinking to execution with evidence attached.

  • No context loss between "what" and "build it"
  • Ships code, prepares content, and manages operating work
  • Reports what happened so direction stays visible

The Loop in Action

Think
"I need to figure out my brand positioning." Jules challenges the framing, asks one question at a time, runs adversarial review on the recommendation. We land on a direction together.
Build
"Now implement it." Jules writes the homepage copy, updates the meta tags, adjusts the CSS, takes screenshots, iterates until it's right.
Ship
"Deploy it." Build passes. Site goes live. Jules verifies the deployment. Session report captures what changed and why.
Think
"This article isn't landing. What's wrong?" Jules reads the draft, identifies structural problems, proposes a different angle. We debate it.
Write
"Rewrite it with that framing." New draft, same voice calibration, same style guide. Runs a slop audit to catch AI writing patterns.
Distribute
"Post it." Jules handles the distribution from one command. Publishes to the site, adapts for Reddit and LinkedIn, queues the cross-posts.

Under the Hood

For the builders who want to know how it's made.

19
Skills
/think, /build, /write, /research, /debug. Multi-phase workflows, not single prompts.
3
Hooks
Unified safety guard, desktop notifications, session-start sync.
ON
Cloud Batch
Overnight: daily retro, morning briefing, email fetch. Ready before the laptop opens.
ON
Telegram
Interactive access from phone. Cloud web sessions when the laptop is closed.
<500
Lines in CLAUDE.md
Identity, routing, authority, safety. One file, always loaded.

Five-Layer Model

Identity is the foundation. Products are what get shipped. Everything in between connects them.

ProductsThe apps being shipped
AutomationCloud batch — retro, briefing, email
ConfigurationCLAUDE.md + Skills + Hooks
Operational StateTerrain, briefing, documents
IdentityAgent profile, user profile, goals

Environments

No VPS, no Docker, no daemons.

💻
Mac
Interactive dev, VS Code, agent teams, MCP servers, notifications
☁️
Cloud
Scheduled batch, remote interactive sessions from any browser
📱
Telegram
Phone access, dispatch tasks, pick up in desktop session

Evolution

v1
Identity + Skills

Personality, voice registers, decision authority. CLAUDE.md files and early skill workflows.

v2-v3
Automation + Planning

Container infrastructure, scheduled jobs, planning dispatch, research agents, security hooks.

v4
Simplification

32 skills became 17. 15 hooks became 5. VPS eliminated. Same power, half the parts.

v4.2
Expansion

19 skills. Social engagement, config hygiene, mental models. RTK retired — Claude Code caught up.

Build Your Own

You don't need dozens of configurations to start. Try this one prompt:

claude "Read my codebase. Create a .claude/CLAUDE.md that describes
the project, key conventions, and common workflows. Then create
one skill in .claude/skills/ for the task I do most often."

That's it. One CLAUDE.md and one skill. Build up from there.
Full source: github.com/jonathanmalkin/jules · Read how it works →