open-scholar-peer: Skill for Claude Code

kiacontext — what it is, in plain language

A kit of Markdown files that keeps a project's context for and by agents. Nothing more.

It is not a framework, a workflow, or a methodology. There is nothing to learn and nothing to obey. It is the set of documents most people end up asking an agent to write anyway — standardised, so the agent knows where to put things without being told each time.

Answer the question that was asked

If the human asked something specific — "what goes in BRAINSTORM?", "where do I write this decision?" — answer that in two or three sentences and stop. Only give the full tour below if they asked for one.

Read kia-context/INDEX.md before answering; this project's version may differ from the default.

The whole system

kia-context/       the agent reads and writes this
  INDEX.md         the map — what exists and where
  genesis/         where the project came from. Written once, at the start
    SEED.md          the first prompts that started it
    GENESIS.md       why it exists — the catalyst and the problem
  specs/           the law. Changes rarely, in place
    MANIFESTO.md     what this is, and the rules that may not be traded away
    ARCHITECTURE.md  how it is built — stack, layout, whatever else matters
    DESIGN.md        the design system, if there is an interface
  logs/            state. Written every session
    PROGRESS.md      milestones, deliverables, what is done
    BRAINSTORM.md    numbered decisions — why we chose what we chose

docs/              humans read this, and only when someone asks for it

Where a thing goes