Mock2 Standards loading…

One command. Every workspace.

These are the development standards for AI-assisted work in VS Code (GitHub Copilot and Claude). The installer puts them at user level, so every folder you open — new repo, old repo, empty folder — already has the constitution, the scoped rules, the stage prompts, the two agents and the hooks. The SessionStart hook checks this site for updates each time you start a chat.

Install (Windows, PowerShell)

Open PowerShell (no admin needed), paste, press Enter:

irm https://mock2.fractionate.ai/install.ps1 | iex

Prefer to read it first? Open install.ps1 · then paste it into PowerShell.

macOS / Linux
curl -fsSL https://mock2.fractionate.ai/install.sh | bash

What the installer does

  1. Downloads manifest.json and writes each listed file into your home folder: ~/.claude/ (constitution + rules), ~/.copilot/ (prompts, agents, hooks, MCP config) and ~/.mock2/ (hook scripts, repo templates, version marker).
  2. Never touches anything outside your home folder. Never overwrites your mcp-config.json if you already have one.
  3. Installs the GitHub Copilot and Copilot Chat extensions if the code command is on your PATH.
  4. Safe to re-run; that is also how the SessionStart hook applies updates.

After install

Check it landed

  1. Restart VS Code.
  2. Command Palette → Chat: Open Customizations. You should see the Mock2 entries under Instructions, Prompts, Agents and Hooks.
  3. Start any chat. The first thing the agent knows is “Mock2 standards loaded (v…)” — that line comes from the hook.

Daily use

  1. New or existing repo: type /mock2-init.
  2. New feature: /mock2-concept → approve the mockup → /mock2-define → confirm rules → /mock2-build.
  3. Pick the Mock2 Concept or Mock2 Build agent from the agent dropdown when you want the guardrails enforced by tool access, not just by instruction.

Files

Everything the installer writes, exactly as it will land on your machine. Click a file to read it.

Select a file
Loading manifest…

How it works

User level, not repo level. VS Code reads ~/.claude/CLAUDE.md, ~/.claude/rules/, ~/.copilot/prompts, ~/.copilot/agents and ~/.copilot/hooks for every workspace. Claude Code reads the same ~/.claude files. So the shared standards live once, on the machine, and repositories only carry what is specific to them (.github/copilot-instructions.md, state/).

Hooks make the check automatic. Instructions ask the model to do something; hooks are code that runs every time. SessionStart fetches manifest.json, re-runs the installer if the version changed, and injects the loaded version into the chat context. Stop appends a line to ~/.mock2/ledger.jsonl (session, folder, latest change record) and, when MOCK2_API is set, posts it to the standards server.

Updating the standards means editing the files on this site and bumping version in manifest.json. Every developer gets the change at their next chat. Priority when instructions conflict is personal → repository → organization, so the shared layer is written as policy and stack specifics stay in the repo file.

Phase 2 (planned): an MCP endpoint at /mcp with get_rules, search_learnings and propose_rule, plus a session feed and a proposals inbox on this site. The reserved entry is already in mcp-config.json.

Copied