kami-research-frontier

Maps open research problems, evidence standards, and positioning rules for the kami-kakushi game project.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill kami-research-frontier-raynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kami-research-frontier
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/kami-research-frontier
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill kami-research-frontier-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on a long-running game project, it is hard to know which problems are genuinely open versus already solved, what evidence a claim needs before it can be stated, and how to avoid overselling results. This Skill provides a curated map of the kami-kakushi project's research frontier so agents and contributors pick ambitious work with clear falsifiable success criteria. ## Core Features & Use Cases - Frontier problem catalog: Documents open game problems (fun certification, CSS-only art direction under Andon Steel, authored narrative depth at T1+) with why generic approaches fail, existing in-repo assets, first concrete steps, and falsifiable result criteria. - Process asset registry: Inventories unusual working systems (shared-tree multi-agent protocol, 21-gate verify lattice, sim-priced design, narrative-gen pipeline, capture-to-drain loop) with pointers to their owning skills and evidence artifacts. - Evidence bar and no-oversell rules: Enforces a four-part methodology (predict numbers first, one mechanism explains all observations, adversarial refutation, checks must be able to fail) plus positioning rules that forbid unearned novelty or SOTA claims. - Use Case: When a session is about to claim something is novel or solved, or when choosing the next big bet, load this Skill to check the claim against the evidence bar and route the idea through brainstorm, plan, build, and verdict stages. ## Quick Start Ask the agent to load the kami-research-frontier skill and evaluate whether a proposed idea is a genuine frontier bet or routine work before writing it up.

Frequently Asked Questions about kami-research-frontier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide what ambitious work to pick up next in this project?

Load this Skill and read the frontier catalog: each entry lists why generic approaches fail, what in-repo assets exist, first concrete steps, and a falsifiable result criterion. Game-frontier items like fun certification and graphics direction are primary; process assets are secondary.

What evidence is required before claiming something is novel or solved?

Claims must clear a four-part bar: predict numbers before running, one mechanism must explain all observations including negatives, run an adversarial refutation pass via the battery skill, and the check must be capable of failing. Until then, use honest labels like open problem, candidate, or bet.

Can automated proxies certify that a game is fun?

No. Proxies like playcheck timing and balance simulations can only prove fun's absence by going red; only a closed human review item can certify fun's presence. The goal is to narrow the human's review burden, never to replace it.

When should I not use this research frontier skill?

Do not use it to execute graphics work, balance simulation, debugging, change control, or narrative authoring directly. Those belong to sibling skills like kami-cohesion-campaign, kami-balance-analysis-toolkit, kami-debugging-playbook, and kami-narrative-grammar.

How are research ideas tracked so they are not lost?

Ideas move through durable homes: brainstorms in project/brainstorms, plans in docs/plans via the write-plan skill, builds under change control, verdicts as HR/HD items, and retirement into project/archive or BACKLOG.md with the rationale recorded.