kimi-agent-kit

Opt a project into palette (the product-intent outer loop). Scaffolds the _palette/ backlog through a light intake and asks about git handling. Use when the user wants to start managing a project or roadmap with palette, or accepts the offer to set palette up. Does not scope a phase — the palette loop does that afterward.

Pull-only palette helper. Produce project rules (_palette/project-rules.rst) — components, patterns, architecture, accessibility — when the user wants project conventions on file. Not part of the default palette loop; invoke only when explicitly asked, or when a phase needs shared conventions defined before stories.

Pull-only palette helper. Produce a technical spec (_palette/tech-spec.rst) for the current phase when the user wants that depth. Not part of the default palette loop; invoke only when explicitly asked, or when a phase clearly needs stack / data-model / API decisions settled before stories.

Pull-only palette helper. Produce a visual design brief (_palette/design-brief.rst) and an optional design-preview.html for the current phase when the user wants that depth. Not part of the default palette loop; invoke only when explicitly asked, or when a phase needs a visual language defined before stories.

Pull-only palette helper. Produce a UX flow (_palette/ux-flow.rst) — screens, navigation, flow sequence — for the current phase when the user wants that depth. Not part of the default palette loop; invoke only when explicitly asked, or when a phase's screens and navigation need defining before stories.