AlienMonster 👾

Strategy repository for your codebase — think before you vibe.

AlienMonster captures product strategy into structured primitives (user, problem, value proposition, business model, decisions, assumptions, risks) that your coding agents can read before they plan code. Ship from a shared picture instead of fighting drifted context.

Quick start

# Scaffold AlienMonster in a new or existing repo
npx alienmonster init my-project

# Sign in (opens browser, device flow)
npx alienmonster login

# List your projects
npx alienmonster projects

# Pull strategy content into .alienmonster/
npx alienmonster export

After init, your repo has a CLAUDE.md / AGENTS.md / .cursorrules managed section that tells coding agents to call get_feature_context before planning any feature.

Commands

| Command | What it does | |---|---| | alienmonster init [name] | Scaffold .alienmonster/ + managed agent-instruction section | | alienmonster login | Device-flow auth to alienmonster.ai | | alienmonster logout | Clear local credentials | | alienmonster whoami | Show current user | | alienmonster new <name> | Create a project server-side | | alienmonster projects | List your projects | | alienmonster status | Show strategy repo state | | alienmonster export [path] | Sync strategy from cloud to local disk | | alienmonster insights | Show recent strategy insights |

Facilitation

The CLI is a thin HTTP client — it scaffolds, authenticates, and syncs. Facilitation (brainstorming, strategy interviews) happens in your MCP client:

• Claude.ai (web): connect via alienmonster.ai/settings/mcp/claude-ai
• Claude Code (terminal): connect via alienmonster.ai/settings/mcp/claude-code
• Cursor: coming soon

With the MCP server connected, any of these clients can run a brainstorm or strategy interview against AlienMonster's facilitator, push primitives back, and keep your strategy repo in sync.

Docs

Full docs and product site: alienmonster.ai

License

MIT