Skip to content

MCamner/atlas-one

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

109 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

[A] Atlas Studio

Adaptive prompt system for structured thinking and decision-making.

Status: v1.5.0 β€” public repo hygiene and prompt-pack maturity

Prompt & docs checks

πŸ‘‰ Live demo: https://mcamner.github.io/atlas-one/


Atlas Studio is a local-first adaptive prompt system that turns raw intent into structured thinking workflows.

Instead of writing prompts ad-hoc, you:

  • define intent
  • select a reasoning mode
  • generate a structured prompt
  • copy or hand off cleanly to ChatGPT

Visual flow

Input
  ↓
Route selection (auto-classify mode)
  ↓
Workflow (analysis / architecture / strategy)
  ↓
Structured prompt pipeline
  ↓
ChatGPT execution   OR   mq-agent execution (plan / review / audit / signal)

UI overview

The interface runs entirely in the browser β€” no install required.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ [A] Atlas Studio                              v1.5.0    β”‚
β”‚ ─────────────────────────────────────────────────────── β”‚
β”‚  SIDEBAR              β”‚  MAIN PANEL                     β”‚
β”‚  ─────────────────    β”‚  ─────────────────────────────  β”‚
β”‚  Type: Architecture   β”‚  Goal input                     β”‚
β”‚  Search modes…        β”‚  > Design a secure remote       β”‚
β”‚                       β”‚    access architecture          β”‚
β”‚  Library              β”‚                                 β”‚
β”‚  > Atlas One Core     β”‚  Prompt type + reasoning route  β”‚
β”‚                       β”‚  Requirements β†’ Options β†’ Rec.  β”‚
β”‚  Modes (13)           β”‚                                 β”‚
β”‚  > Analyze            β”‚  Final prompt output            β”‚
β”‚  > Architect          β”‚  ChatGPT-ready structured text  β”‚
β”‚  > Debug              β”‚                                 β”‚
β”‚  > …                  β”‚  [ Generate ] [ Copy ] [ β†’ ]    β”‚
β”‚                       β”‚                                 β”‚
β”‚  Packs                β”‚                                 β”‚
β”‚  > mq-mcp Safety      β”‚                                 β”‚
β”‚  > Release Readiness  β”‚                                 β”‚
β”‚  > Systems Thinking   β”‚                                 β”‚
β”‚  > …                  β”‚                                 β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Keyboard shortcuts: Ctrl+Enter generate Β· / focus command Β· s focus search Β· Esc clear


Screenshot

Interface preview from the GitHub Pages build:

Atlas Studio UI

Try it

πŸ‘‰ https://mcamner.github.io/atlas-one/

No install. Runs in your browser β€” no Java required.


Why it matters

Most AI usage today is unstructured, inconsistent and hard to repeat. Atlas Studio adds structure to thinking, consistency to execution and repeatability to workflows β€” a system for thinking and execution, not another prompt box.


What it does

Atlas Studio turns intent into structured AI workflows:

  • Adaptive prompt modes β€” switch between analysis, architecture, research, strategy, decision, problem solving, execution and writing
  • Quick action controls β€” pick /atlas, /research, /write, /strategy and other modes without rewriting the prompt
  • System reasoning preview β€” see the selected problem type, route, pipeline and rationale before you generate
  • Structured prompt library β€” reusable prompts loaded from web/prompts.json, with source prompts kept in docs/prompts/
  • Local-first execution β€” runs entirely on 127.0.0.1, no external dependencies
  • ChatGPT handoff β€” copy the final prompt and open ChatGPT in one action
  • mq-agent execution β€” run the routed goal directly via mq-agent (plan, review, audit, signal) when the Java backend is running; results appear inline, the panel takes a repo path, and unmapped modes show as mode β†’ plan (fallback)

Example flow

User input:
"Design a secure remote access architecture"

↓

Prompt type selected:
Architecture

Route:
Requirements and Constraints β†’ Design Options β†’ Review and Recommendation

↓

Generated output:
ChatGPT-ready structured prompt

Architecture

Atlas One is the prompt and interaction layer in the local mq ecosystem. It packages reasoning modes, prompt packs and handoff patterns. It does not own runtime validation or review decisions.

Current role split:

flowchart TD
    U([User goal]) --> AO

    subgraph AO["Atlas One β€” think / prompt / route"]
      R[Mode routing + prompt packs] --> HO[Handoff text]
    end

    HO -->|copy| EXT[ChatGPT / external LLM<br/>execute externally]
    HO -->|run| AG[mq-agent<br/>execute / orchestrate]

    AG --> MC[mq-mcp<br/>review / risk / validation / memory contracts]
    AG -. optional provider .-> OL[Ollama<br/>local model, never a decision authority]
    MC --> OB[(mqobsidian<br/>persist / source of truth)]
    R -. Save to brain .-> OB
Loading
  • Atlas One β€” prompts, mode routing, interaction patterns and handoff text
  • mq-agent β€” orchestration and command execution flow
  • mq-mcp β€” review, risk, validation, safety classes and memory contracts
  • mqobsidian β€” durable memory: persists decisions and curated context (Save to brain)
  • Ollama β€” optional local model provider, never a decision authority
atlas-one/
β”œβ”€β”€ docs/prompts/     # Core prompt, modes, and seed prompt packs
β”œβ”€β”€ docs/             # GitHub Pages and prompt library docs
β”œβ”€β”€ src/              # Java server (API + static hosting)
β”œβ”€β”€ web/              # UI (routing, prompts, visualization)
β”œβ”€β”€ archive/legacy/   # Retired prototype source (not built)
β”œβ”€β”€ build_and_run.sh  # Local dev runner
β”œβ”€β”€ package_mac_app.sh
└── run_mac.command

Backend

  • Java HTTP server on 127.0.0.1:8766
  • Serves UI + API endpoints:
    • /api/prompts
    • /api/health
    • /api/execute β€” routes goal β†’ mq-agent CLI command

Frontend

  • Vanilla JS application
  • Handles:
    • routing logic
    • prompt generation
    • UI state
    • local storage

Prompt library

Atlas One v0.2.0 adds a file-based prompt library:

docs/prompts/
β”œβ”€β”€ atlas-one.md
β”œβ”€β”€ modes/
└── packs/

Core docs:

Canonical modes:

Analyze
Decide
Architect
Research
Explain
Teach
Edit
Coach
Plan
Debug
Review
Summarize
Create

Run locally (Java backend)

Requires Java 17+. Runs the full server version at http://127.0.0.1:8766.

./build_and_run.sh

Or as a macOS app bundle:

./package_mac_app.sh

Design principles

  • Local-first β€” no cloud dependency
  • Structured thinking over raw prompting
  • Repeatability over improvisation
  • Separation of intent and execution
  • Composable workflows

Roadmap

Current: v1.5.0 shipped. Next: v2.0.0 β€” Atlas as a full local prompt/workflow studio (direction; not yet scoped). See ROADMAP.md for the full release map.


Use cases

  • Architecture design
  • Technical decision-making
  • Problem analysis
  • Structured research
  • Workflow standardization
  • Prompt engineering at scale

Status

Stable prompt operating system with mq ecosystem prompt packs and a documented execution boundary. Current public alignment target: v1.5.0.


Security

Atlas Studio runs locally. No data is sent anywhere unless you configure an external AI provider.

Do not commit API keys or credentials. Use environment variables or ignored local files for sensitive values.


License

MIT


Author

Mattias Camner IT Architect β€” building practical systems where infrastructure, automation, and usability work together


Final note

Atlas Studio brings structure, repeatability and system thinking to how we use AI.

macOS helper scripts

The repository supports helper scripts for macOS packaging and running. To keep these portable:

  • Prefer setting MQ_ROOT environment variable to your repo root:

    export MQ_ROOT="$(pwd)"

    Or rely on the scripts' autoprobe (they try MQ_ROOT, git rev-parse, then a script-relative fallback).

  • Create Claude local settings from the example:

    cp .claude/settings.local.example.json .claude/settings.local.json
    # Edit .claude/settings.local.json and replace <MQ_ROOT> with your path (or set MQ_ROOT env var)
  • Packaging requires jpackage (JDK 16+ or a JDK distribution with jpackage). If jpackage is missing, package_mac_app.sh will fail with a clear message.

Releases

Packages

Contributors

Languages