github.com/ds17f/andropolis (link)

commit signals (171)

source signals (8)

• .claude/skills/qwen-dispatch/SKILL.mdvia unspecified

  ---
  name: qwen-dispatch
  description: Dispatch a task spec to the local qwen executor with pi, then review the diff and iterate. Use when you delegate a coding unit of the Micropolis Android port to qwen instead of writing the code yourself — when the plan says "qwen owns" a task, or the user asks to give a task to qwen, to the local model, or to pi.
  ---
  
  # qwen-dispatch
  
  Give one task spec to the local **qwen** executor. Use `pi` and the Ollama box at
  `worklaptop.home.silberg.cloud`. Then **review the dif

• .agentsdirectoryvia unspecified
• AGENTS.mdvia agents-md

  # Agent house rules (pi loads this file automatically)
  
  You are the **executor** for a native Android port of Micropolis. A planner
  (Claude or Opus) gives you one task spec at a time. Do what that spec asks. Do no
  more and no less. Then show that your work is correct.
  
  ## Rules
  
  1. Do only what the current task spec asks. Do not change, rename, or improve
     code that is not in the *Files in scope* list.
  2. Do not change the C++ engine sources in `MicropolisCore/`. The one exception
     is a file that the sp

• CLAUDE.mdvia claude-code

  # CLAUDE.md — micropolis-port
  
  Full design & method: `DESIGN.md`.
  
  ## How we work here — READ FIRST
  
  This project runs a **local open-weights model (qwen, via `pi`) as the executor**
  for the coding volume. Opus (Claude) is the **planner / architect / reviewer ONLY**.
  
  **Default to delegating to qwen. Do NOT spend Opus tokens on work qwen can do.**
  That means not just feature code but the legwork around it: researching the
  codebase, searching, sourcing and copying assets, and boilerplate. Put the whole
  j

• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code

ignorefile signals (1)