For vibecoders shipping with Cursor, Claude Code, and Copilot
AlienMonster turns your product thinking into a .alienmonster/ directory in your repo. Your coding agents read it as context.
Open source · MCP-native · EU-hosted
THE ARTIFACT
.alienmonster/ lives next to your code. It's git-versioned, plain markdown, and structured so coding agents can parse it. When you run a session — facilitated, interview, or atomic push — content lands here. When your agent reads it, your strategy becomes its context.
.alienmonster/ ├── context.md ← short steering file your agent reads first ├── strategy.md ← full prose: who, what, why, how ├── assumptions.md ← what's true, what's risky, what's validated ├── decisions.md ← architectural decision records ├── tasks.md ← prioritized actionable next steps ├── strategy.json ← machine-readable strategy snapshot ├── powers/ ← domain-scoped agent context │ ├── target-user.md │ ├── value-prop.md │ └── ... ├── views/ ← rendered framework views (PVB, BMC, OST) ├── architecture/ ← system + technical decisions ├── plans/ ← roadmap and milestone plans └── statements/ ← brainstorm summaries and tensions
.alienmonster/ ├── context.md ├── strategy.md ├── assumptions.md ├── decisions.md ├── tasks.md ├── strategy.json ├── powers/ │ ├── target-user.md │ ├── value-prop.md │ └── ... ├── views/ ├── architecture/ ├── plans/ └── statements/
Same shape every time. Your agents know where to look.
THE MOMENT OF TRUTH
Your coding agent has access to your repo. When .alienmonster/ is in there, it has access to your strategy. Watch what happens.
PROMPT
Add a pricing page that fits our positioning.
.alienmonster/I'll create a pricing page. A few questions first: - What pricing tiers do you want? - Who's the target customer? - Should I match the rest of your site's tone? Once I know, I'll scaffold the page.
.alienmonster/Reading .alienmonster/strategy.md ... your target user is solo vibecoders shipping with AI agents. From decisions.md: "MIT-licensed across the stack. Vibecoders are the wedge audience." From context.md: "Tone: README written by someone who respects the reader's time." Scaffolding /pricing matching your existing marketing voice. Starting now.
Illustrative example. Real session recordings coming as we open up access.
HOW STRATEGY GETS IN
Different moments call for different inputs. Pick the one that fits where you are.
Open the web app or npx alienmonster. Pick a framework (Product Vision Board, OST, Business Model Canvas). Run a structured session, solo or with your team. Primitives land in .alienmonster/ when you're done.
Best for: Starting from scratch. Aligning a co-founder.
Connect AlienMonster to Claude.ai (one click, OAuth). Claude conducts a natural conversation. Behind the scenes, it pushes structured primitives into your repo via MCP. You talk. The repo fills.
Best for: You already think out loud. You hate forms.
Anywhere you have an MCP client — Cursor, Claude Code, Claude.ai — push a single insight, decision, or assumption into your repo with one tool call. It lands in the right file. Your repo updates.
Best for: Capturing the things you'd otherwise lose.
All three write to the same .alienmonster/. Same shape, same agent-readable contract.
WHO'S THIS FOR
You live in Cursor. Claude Code is open in another tab. Your prompts are getting better but your agents still drift — they forget who you're building for, re-ask the same context every session, and ship code that's technically correct but strategically wrong.
.alienmonster/ is the missing layer. Your strategy, in your repo, in a format your agents already know how to read.
Strategy stops here. Your tickets live in Linear, Kiro, or Jira.
.alienmonster/ directory — git-versioned, agent-readablenpx alienmonster initTHE NON-NEGOTIABLES
Hetzner servers, Brussels-built. Your data doesn't leave Europe unless you choose.
Bring your own Anthropic, OpenAI, or self-hosted model key. We don't gate the AI behind our pricing.
The directory format that lives in your repo is yours forever — even if we disappear.
Self-host coming. Run the whole stack on your own infrastructure. In progress.
The cloud is convenient. The repo-native directory is the durable asset.