@kienmatu/inkos-core 0.1.0

package/genres/xuanhuan.md

@@ -0,0 +1,64 @@
+---
+name: 玄幻
+id: xuanhuan
+chapterTypes: ["战斗章", "布局章", "过渡章", "回收章"]
+fatigueWords: ["冷笑", "蝼蚁", "倒吸凉气", "瞳孔骤缩", "不可置信", "轰然炸裂", "满场死寂", "难以置信", "仿佛", "不禁", "宛如", "竟然"]
+numericalSystem: true
+powerScaling: true
+eraResearch: false
+pacingRule: "三章内必有明确反馈：打脸、收益兑现、信息反转、地位变化"
+satisfactionTypes: ["打脸", "升级突破", "收益兑现", "智斗碾压", "身份揭示", "底牌亮出"]
+auditDimensions: [1,2,3,4,5,6,7,8,9,10,11,13,14,15,16,17,18,19,24,25,26]
+---
+
+## 题材禁忌
+
+- 主角为推剧情突然仁慈、犯蠢、讲武德
+- 同质资源不写衰减默认全额结算
+- 用"暴涨""海量"跳过数值结算
+- 无铺垫的能力觉醒
+- 反派像木桩一样排队送死
+- 无铺垫强行让退场角色回归
+- 在没有铺垫的情况下突然塞入新体系、新地图、新外挂解决问题
+- 把所有章节都写成高爆裂战斗章
+- 拆解知识库反向污染正文，写成"似曾相识"的拼装文
+- 风格混入都市腔、科幻腔、游戏系统播报腔、轻小说吐槽腔
+
+## 数值规则
+
+- 设定不可吃书：前文确立的设定数值后文不可无升级过程地随意改变
+- 金手指四维约束：
+  - 能力上限：必须设定明确的能力天花板，不可无限升级
+  - 附加代价：使用伴随代价（寿命、体力、副作用），权衡利弊增强冲突
+  - 触发条件：激活与特定场景/事件关联，不可随时随地无条件使用
+  - 成长路径：随主角经历同步升级，解锁过程与剧情节点绑定
+- 同质资源重复吞噬必须写明衰减，不得默认全额结算
+- 同质吞噬衰减公式：收益 = 基础值 × max(0.3, 1 - 0.15×(N-1))
+- 不要用"暴涨""海量""难以估量"跳过数值结算
+- 期初值从账本取（不凭记忆），增量逐笔列出并注明来源
+- 消耗逐笔列出并注明用途，期末 = 期初 + 增量 - 消耗，不得跳步
+- 正文中出现的系统提示（如【气血值+X】）必须与POST_SETTLEMENT一致
+- 若正文写了"比A还高"这类比较句，必须数值验证后再保留
+- 数值连续性必须可追溯：同层级、同类型样本的增量不得无说明跨越一个数量级
+
+## 语言铁律
+
+- 力量体系的量级感用体感传达，不用抽象数字。✗"他的火元从12缕增加到24缕" → ✓"手臂比先前有力了，握拳时指骨发紧"
+- 同一高潮段（如吞火/突破/觉醒）中，同一意象域的渲染不超过两轮，第三轮必须切入新信息或新动作
+- 搜尸/清点/装备段落禁止清单式列举，必须带入角色判断或取舍：✗"他翻出粗盐、水囊、黑面饼" → ✓"水囊最值钱，剩下那点水比命轻不了多少"
+
+## 叙事指导
+
+以战斗和资源获取驱动剧情。主角行为由利益驱动，杀伐果断。
+金手指/能力系统必须有限制：使用频率、范围限制或使用代价。
+设定不可吃书：前文确立的数值后文不可无升级过程地随意改变。
+
+三章内应有明确反馈，但反馈可以是打脸、收益兑现、信息反转、地位变化，不限于杀人。
+涉及吞噬时，收益必须同时落到资源说明与具体增量，不能只写抽象提升。
+小冲突尽快兑现反馈；不要把爽点无限后置。
+
+核心对手必须有脑子，有试探、有误判、有反扑。
+可以留人、钓鱼、示弱、借刀杀人，但前提只能是利益更大，绝不能是心软。
+
+用动作、伤势、声音、重量、冲击、温度来落地"强"，少用空泛判断。
+每个场景至少推进一项：信息、地位、资源、伤亡、仇恨、境界。

package/package.json

@@ -0,0 +1,76 @@
+{
+  "name": "@kienmatu/inkos-core",
+  "version": "0.1.0",
+  "description": "InkOS pi-agent production harness for story creation, governed context, retrieval, review, and interactive worlds",
+  "keywords": [
+    "story-creation-ai-agent",
+    "story-agent",
+    "ai-novel-writing",
+    "ai-writing-agent",
+    "novel-generator",
+    "interactive-fiction",
+    "ip-content",
+    "continuity-audit",
+    "style-cloning",
+    "ai-fiction",
+    "creative-writing-ai",
+    "llm-agent",
+    "zod-validation"
+  ],
+  "type": "module",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./interactive-film/evaluator": {
+      "types": "./dist/interactive-film/evaluator.d.ts",
+      "import": "./dist/interactive-film/evaluator.js"
+    },
+    "./interactive-film/graph-schema": {
+      "types": "./dist/interactive-film/graph-schema.d.ts",
+      "import": "./dist/interactive-film/graph-schema.js"
+    },
+    "./forecast/schema": {
+      "types": "./dist/forecast/schema.d.ts",
+      "import": "./dist/forecast/schema.js"
+    }
+  },
+  "files": [
+    "dist",
+    "!dist/__tests__",
+    "genres",
+    "skills"
+  ],
+  "license": "AGPL-3.0-only",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/kienmatu/inkos.git",
+    "directory": "packages/core"
+  },
+  "dependencies": {
+    "@mariozechner/pi-agent-core": "0.67.1",
+    "@mariozechner/pi-ai": "0.67.1",
+    "@sinclair/typebox": "^0.34.49",
+    "dotenv": "^16.4.0",
+    "epub-gen-memory": "^1.0.10",
+    "jszip": "3.10.1",
+    "js-yaml": "^4.1.1",
+    "undici": "6.21.3",
+    "unpdf": "^1.6.2",
+    "zod": "^3.25.76"
+  },
+  "devDependencies": {
+    "@types/js-yaml": "^4.0.9",
+    "typescript": "^5.8.0",
+    "vitest": "^3.0.0"
+  },
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsc --watch",
+    "test": "vitest run",
+    "typecheck": "tsc --noEmit"
+  }
+}

package/skills/inkos-interactive-film/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: inkos-interactive-film
+description: 互动影游的剧情树、变量旗标、可拍节点、多结局与资产连续性方法。Used for creation and authoring of interactive-film projects.
+---
+# Interactive film creation
+
+Apply this method when creating or editing an interactive film/game-script deliverable.
+
+- Preserve the user's confirmed premise, audience, format, budget, visual direction, and adaptation boundary. Unspecified choices remain adjustable rather than becoming hidden defaults.
+- Build choices around materially different intentions, costs, information, relationships, or consequences. Cosmetic wording changes are not branches.
+- Make every branch legible: entry condition, player choice, state change, later consequence, merge/no-return behavior, and reachable ending.
+- Variables and flags serve story causality. Use relationships, knowledge, evidence, items, identities, promises, secrets, and ending gates as needed; never impose generic RPG stats or fixed numeric systems.
+- Keep nodes playable and producible: a clear situation, visible action, performable dialogue, meaningful choice, state effects, and a valid destination.
+- Maintain character voice and known state across nodes. A later node cannot forget facts, injuries, items, relationships, or prior choices that still apply.
+- Storyboards and image prompts must preserve character, location, prop, era, lighting, and visual-contract continuity. Do not invent a visual style the user did not choose.
+- Each ending should express the accumulated path, not a last-minute label attached to the same outcome.

package/skills/inkos-interactive-film/references/branch-state-craft.md

@@ -0,0 +1,13 @@
+# Branch and state craft
+
+## Choices change state
+
+Every meaningful choice changes knowledge, relationship, access, risk, resources, or route. Avoid choices that differ only in wording and immediately collapse to the same result without a visible consequence.
+
+## Variables express story memory
+
+Use variables and flags for facts the later story must remember. Define who sets them, what they mean, and which nodes consume them. Keep the set small enough for an author to inspect.
+
+## Reachable endings
+
+Every ending must have a traceable route and explicit conditions. Branches may reconverge when prior choices still affect dialogue, available actions, or consequences. Never hide an unreachable ending behind contradictory flags.

package/skills/inkos-long-market-research/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: inkos-long-market-research
+description: 长篇网文市场、榜单、平台趋势与对标研究。Use for evidence-based long-form fiction market research, not for ordinary drafting.
+---
+# Long-form market research
+
+Use this skill when the user wants current market evidence, platform differences, comparable works, audience expectations, or topic selection for a long-form project.
+
+- Clarify the market, platform, audience, language, and time window only when they materially affect the answer.
+- Use `research_web` for current claims. Separate observed evidence, interpretation, and creative recommendation.
+- Use `ingest_material` for user-provided reports or URLs and `retrieve_material` for already archived evidence.
+- Do not treat rankings, popularity, or one successful book as a writing formula. Extract mechanisms and uncertainty.
+- Research never mutates book canon. If the user later wants a source available during chapter writing, archive it and explicitly bind it with `manage_book_reference` in the active book.
+- Respond in the user's language.
+
+For a detailed evidence and deliverable rubric, load `references/research-rubric.md` with `use_skill` only when needed.

package/skills/inkos-long-market-research/references/research-rubric.md

@@ -0,0 +1,19 @@
+# Long-form market research rubric
+
+## Evidence
+
+- Record source, publication date, observation window, platform, and whether a number is first-party, third-party, or inferred.
+- Distinguish durable reader needs from a temporary chart pattern.
+- Compare at least two sources when making a market-level claim.
+- State missing evidence rather than filling it with genre common sense.
+
+## Deliverable
+
+1. Market boundary and user objective.
+2. Observed signals with sources.
+3. Audience and reading-context implications.
+4. Transferable story mechanisms.
+5. Risks, saturation, and counter-signals.
+6. Two or three differentiated directions, not a single mandatory formula.
+
+Do not copy titles, character configurations, signature scenes, or wording from a comparable work.

package/skills/inkos-long-story-analysis/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: inkos-long-story-analysis
+description: 长篇小说拆稿、文风分析与可迁移机制提炼。Use when analyzing a full novel or long sample without copying its expression.
+---
+# Long-form story analysis
+
+Use this skill when the user asks to deconstruct, compare, learn from, or continue from a long novel or substantial sample.
+
+- Preserve the source as traceable material with `ingest_material` when it comes from a file, PDF, URL, or upload.
+- Analyze semantic mechanisms: reader promise, conflict escalation, character motivation, information release, scene function, emotional payoff, volume rhythm, prose behavior, and continuity load.
+- Keep source evidence pointers. Separate direct observation from inference.
+- Extract reusable craft, not names, wording, scene order, or signature combinations.
+- If the user explicitly wants the active book to consult this source later, call `manage_book_reference(action="bind")` with the user's natural-language purposes. Binding is guidance, never canon.
+- If the user only asks a question, answer it; do not start writing or editing a book.
+- Respond in the user's language.
+
+Load `references/analysis-lens.md` only for a full decomposition or comparison deliverable.

package/skills/inkos-long-story-analysis/references/analysis-lens.md

@@ -0,0 +1,16 @@
+# Long-form decomposition lens
+
+## Layers
+
+- Promise: what continuing experience the reader expects.
+- Story engine: the repeatable pressure, choice, consequence, and reward loop.
+- Structure: opening contract, arc transitions, volume goals, midpoint changes, and payoff placement.
+- Character: desire, fear, tactic, relationship movement, voice, and irreversible choices.
+- Information: what the reader, protagonist, and opposition know at each stage.
+- Scene craft: entry pressure, concrete action, evidence, turn, consequence, and exit tension.
+- Prose behavior: viewpoint distance, sentence movement, dialogue subtext, detail selection, and paragraph rhythm.
+- Long-horizon state: facts, promises, hooks, unresolved costs, and continuity burdens.
+
+## Output discipline
+
+Anchor important claims to a chapter or excerpt. End with transferable principles, failure conditions, and several recombination options. Never output a disguised rewrite of the source.

package/skills/inkos-long-writing/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: inkos-long-writing
+description: 长篇小说的场景构造、人物因果、信息释放与连载节奏。Used by InkOS long-form workers as their shared craft method.
+---
+# Long-form narrative craft
+
+Apply this method inside the active architect, writer, auditor, or reviser operation.
+
+- Turn the chapter goal into scenes with an immediate objective, resistance, a meaningful turn, and consequences that survive the scene.
+- Let character choices follow what each person wants, knows, fears, and can afford. Relationships change through events, not author explanation.
+- Reveal setting and backstory through action, evidence, dialogue, and sensory particulars. Do not replace a scene with a synopsis or analysis.
+- Every passage must alter conflict, evidence, emotion, relationship, knowledge, position, or future consequence. Remove padding rather than stretching to a number.
+- Control information deliberately: answer some active reader questions, deepen others through concrete evidence, and do not manufacture twists by hiding facts the viewpoint should know.
+- Preserve the user's voice, viewpoint, prohibitions, proportions, and current direction. Genre convention is only a default when the governed context is silent.
+- End a chapter after a material change or fresh pressure, not with a mechanical cliffhanger formula. Show the after-effect of major payoffs before starting another escalation cycle.
+- Use references as evidence for craft or facts only. Do not reproduce source wording, names, scene order, or signature combinations.
+- During review or revision, diagnose and repair the smallest layer that actually causes the problem. A formatting failure is not evidence that the prose is bad.

package/skills/inkos-long-writing/references/reader-contract-and-progression.md

@@ -0,0 +1,13 @@
+# Reader contract and progression
+
+## Keep promises visible
+
+The opening establishes what kind of pleasure, tension, or question the story will repeatedly deliver. Later chapters may vary pace, but they must keep feeding that contract through concrete events. A hook is not maintained by mentioning it; someone must act on evidence, pay a cost, make a choice, or change their understanding.
+
+## Progress on more than one axis
+
+A useful chapter changes at least one primary axis and one supporting axis: plot position, knowledge, relationship, status, danger, resources, or self-understanding. Quiet chapters still need a durable change. Climaxes need aftermath before the next escalation.
+
+## Preserve causal ownership
+
+Consequences come from character choices under constraints. Do not solve pressure through coincidence, unexplained competence, or an antagonist becoming careless. When a new fact changes the route, show how it was discovered and why it matters now.

package/skills/inkos-long-writing/references/scene-dialogue-and-length-budget.md

@@ -0,0 +1,13 @@
+# Scene, dialogue, and length budget
+
+## Build length before prose
+
+Treat the chapter target as a scene budget, not a request to pad or trim a finished chapter. Assign the available words or characters to two to five scenes according to dramatic work. A scene earns space through action, resistance, discovery, relationship change, or consequence. If the plan cannot spend the budget on real events, fix the plan before drafting.
+
+## Dialogue carries pressure
+
+In a confrontation, each meaningful reply changes leverage, reveals a constraint, creates a debt, or forces a choice. Remove exchanges that only restate known positions. Let subtext arise from what a character risks by speaking, withholding, or changing the subject.
+
+## Repair measured drift
+
+When a draft misses its hard range, repair the scenes responsible for the drift. Expand a missing action, consequence, or reaction beat; compress recap, repeated interiority, and duplicated description. Preserve established facts and the chapter's intended turn. Never rewrite the whole chapter merely to hit a number.

package/skills/inkos-play-world/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: inkos-play-world
+description: 品类中立的开放世界与分支互动推进方法。Used by InkOS Play workers for coherent action, state, time, and scene progression.
+---
+# Interactive world play
+
+Apply this method inside an active InkOS Play operation.
+
+- Treat the user's world contract as authority. Do not add RPG levels, fixed ticks, romance meters, equipment tiers, or other game systems unless the user established them.
+- Advance one adjacent dramatic beat from the player's literal action. If the input chains several actions, stop at the nearest new pressure point. Show movement, contact, resistance, interruption, and immediate consequence instead of skipping to aftermath, resolution, or reward.
+- Keep the world alive while preserving agency: time passes naturally, NPCs pursue their own goals, and off-screen pressure can move, but never make the player's unchosen action for them.
+- Preserve negation exactly. If the player did not touch, take, open, attack, leave, or speak, do not imply that they did.
+- Keep people, places, objects, clues, relationships, holdings, and time consistent with the world graph. Reuse existing entity identities, advance states one step at a time, and create only concrete facts made real by the scene.
+- Render a playable novel beat, not a system log. Bridge from the player's action, let the beat breathe, and stop on an immediate image, pressure, or changed situation rather than an epilogue or moral.
+- Observation, waiting, idle conversation, and stillness are valid turns. Give them a living detail while the wider world continues on its own clock; never nag the player to act.
+- Open worlds accept free input. Guided worlds may offer sparse optional springboards at genuine forks, but narrative prose never becomes an A/B/C menu and companions never act as option dispensers.
+- Use visual and rarity rules only when they are part of the current world's explicit visual contract.

package/skills/inkos-play-world/references/world-turn-continuity.md

@@ -0,0 +1,13 @@
+# World turn continuity
+
+## One turn, one adjacent consequence
+
+Start from the player's literal action and carry it through contact with the world. Stop after the nearest meaningful consequence or new pressure. Do not skip the requested action and narrate only its aftermath.
+
+## Synchronized time
+
+Elapsed time follows the action and the world's contract. A glance may take seconds, a journey hours, and cultivation years. Advance NPC goals, environmental pressure, and ongoing processes by the same elapsed interval without choosing the player's next action.
+
+## State and prose agree
+
+Every concrete person, object, clue, holding, relationship, location, and time change made real in prose must have a compatible graph fact. Reuse existing identities. Do not create duplicate entities for aliases, and do not let the renderer invent a state-changing object that the mutation omitted.

package/skills/inkos-script-writing/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: inkos-script-writing
+description: 小说、创意与大纲到可演剧本的改编方法。Used for confirmed script and short-drama production.
+---
+# Script writing
+
+Apply this method inside a confirmed script-creation operation.
+
+- Follow the user's chosen script format and adaptation boundary. Do not silently turn faithful adaptation into commercial rewriting or vice versa.
+- Convert interiority into behavior, dialogue, blocking, props, evidence, sound, or visible consequences. Action lines contain only what can be performed or perceived.
+- Build scenes around an objective, resistance, turn, and consequence. Dialogue must change conflict, relationship, information, or emotion rather than explain the premise.
+- Preserve the source's characters, relationships, causal spine, key events, viewpoint constraints, and taboos unless the user explicitly authorizes a change.
+- For episodic or vertical short drama, give each episode a complete dramatic movement and a concrete reason to continue; do not replace scenes with plot summaries.
+- Keep production constraints explicit and usable, but do not let budget shorthand flatten character logic or story coherence.
+- Deliver clean Markdown in the requested production format without process commentary.

package/skills/inkos-script-writing/references/episode-scene-craft.md

@@ -0,0 +1,13 @@
+# Episode and scene craft
+
+## Dramatic units
+
+Each scene has a playable objective, resistance, turn, and exit condition. Convert exposition into visible action, dialogue, props, or blocking. Preserve the source's causal spine when adapting, but change the delivery to fit performance.
+
+## Episode budget
+
+Allocate duration before writing. Reserve time for action and reaction, not only plot facts. A short episode should end on a changed situation, decision, discovery, or pressure that follows from the episode rather than a generic teaser.
+
+## Production clarity
+
+Keep locations, cast, props, and difficult effects legible. If the user supplies budget or staging constraints, solve creatively inside them instead of silently discarding required beats.

package/skills/inkos-short-market-research/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: inkos-short-market-research
+description: 商业短篇市场、平台样本、标题与移动端阅读趋势研究。Use for evidence-based short-fiction market research.
+---
+# Short-fiction market research
+
+Use this skill when the user asks what short fiction is working, how platforms differ, or which commercial direction to test.
+
+- Use `research_web` for current platform and market claims; archive user-provided samples with `ingest_material`.
+- Study titles, openings, pressure chains, evidence chains, emotional gaps, reversals, payoffs, chapter titles, and mobile-reading density.
+- Separate a durable mechanism from a temporary surface trend.
+- Do not turn benchmark research into plagiarism detection or a fixed tag table.
+- Recommend several recombinations with different characters, causes, evidence, and consequences.
+- Research does not authorize generation. If the user wants a short produced, move through the normal confirmation flow.
+- Respond in the user's language.
+
+Load `references/short-market-rubric.md` for a full benchmark report.

package/skills/inkos-short-market-research/references/short-market-rubric.md

@@ -0,0 +1,16 @@
+# Short-fiction benchmark rubric
+
+Evaluate real samples on:
+
+- title promise and mobile thumbnail readability;
+- first-screen pressure and unanswered question;
+- protagonist desire expressed through action;
+- antagonist or pressure-source motivation;
+- evidence, misunderstanding, and information asymmetry;
+- emotional deficit before payoff;
+- causal setup before reversal;
+- scene-by-scene anti-padding value;
+- chapter-end continuation pressure;
+- ending payoff and residual emotion.
+
+The report should explain why a mechanism works, when it fails, and how to recombine it without preserving the source's expression.

package/skills/inkos-short-story-analysis/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: inkos-short-story-analysis
+description: 商业短篇拆稿、情绪链、证据链和反转机制分析。Use to deconstruct a short story into transferable craft.
+---
+# Short-story analysis
+
+Use this skill when the user supplies a complete short story or sample and asks why it works, how it is structured, or what can be learned from it.
+
+- Read the whole supplied story when possible; do not infer the ending from the opening.
+- Preserve traceability with `ingest_material` for uploaded files, PDFs, URLs, or long text assets.
+- Analyze the story core, character motivation, pressure chain, evidence chain, emotional movement, information gap, reversal setup, payoff, opening, chapter titles, and mobile prose density.
+- Quote sparingly and point to evidence. Extract methods rather than replacement prose.
+- Do not silently turn analysis into a new short-fiction run.
+- Respond in the user's language.
+
+Load `references/deconstruction-template.md` for a complete Markdown analysis.

package/skills/inkos-short-story-analysis/references/deconstruction-template.md

@@ -0,0 +1,14 @@
+# Short-story decomposition template
+
+1. One-sentence story core and reader promise.
+2. Character table: desire, wound, tactic, misbelief, cost, and change.
+3. Opening hook: concrete event, pressure, and missing answer.
+4. Scene chain: input pressure, action, new evidence, emotional movement, consequence.
+5. Evidence and information chain.
+6. Reversal chain: setup, reader expectation, reveal, causal validity, payoff.
+7. Emotional curve and reader deficit/reward.
+8. Title and chapter-title functions.
+9. Prose mechanics and mobile readability.
+10. Transferable mechanisms, anti-patterns, and original recombination directions.
+
+Do not reduce the result to labels. Each conclusion needs source evidence and an explanation of causality.

package/skills/inkos-short-writing/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: inkos-short-writing
+description: 12–18章商业短篇的构思、一次写完、整篇审改与包装。Use for confirmed standalone short-fiction production.
+---
+# Short-fiction writing
+
+Use this skill when the user wants a complete standalone commercial short story, not a long serial or a discussion-only answer.
+
+- Preserve the user's premise, emotional target, taboo, viewpoint, and ending preference. Ask only for a missing choice that would materially change the story.
+- In chat or short mode, use the normal proposal and confirmation flow before `short_fiction_run` or cover generation.
+- Build one main line and at most one supporting reversal line. Prefer 12–18 focused chapters and complete scenes over a synopsis montage.
+- Express personality and values through action. Every scene must move conflict, causality, evidence, emotion, payoff, or relationship.
+- Set up reversals and rewards through visible evidence; do not use sudden stupidity or unexplained luck.
+- Treat title, chapter titles, opening, full manuscript, synopsis, selling points, and cover direction as one coherent product.
+- Report partial failures honestly; a cover failure must not erase a successful manuscript.
+- Respond in the user's language.
+
+Load `references/production-checklist.md` before a full production run or whole-story revision.

package/skills/inkos-short-writing/references/production-checklist.md

@@ -0,0 +1,19 @@
+# Short-fiction production checklist
+
+## Before writing
+
+- Core conflict can sustain a complete short story.
+- Protagonist has an active desire and constrained tactic.
+- Pressure source has a credible interest, fear, or misunderstanding.
+- Opening creates a concrete emotional or practical deficit.
+- Evidence and setup exist before each major reversal.
+- Ending delivers the promised emotional result and cost.
+
+## During whole-story review
+
+- No scene exists only to explain.
+- Later chapters do not collapse into summary.
+- Chapter transitions preserve causality.
+- Names, facts, objects, and evidence remain consistent.
+- Mobile paragraphs remain readable without turning prose into fragments.
+- Title and synopsis promise only events the manuscript actually delivers.

package/skills/inkos-story-cover/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: inkos-story-cover
+description: 根据作品、平台与用户视觉要求设计或生成封面。Use for story-cover direction and confirmed cover generation.
+---
+# Story cover
+
+Use this skill when the user wants cover strategy, a cover prompt, generation, or regeneration.
+
+- Start from the actual work: title, genre, protagonist, central conflict, emotional promise, platform, and display size.
+- Treat the user's visual instructions as authoritative. Do not impose a fixed InkOS house style, watermark, frame, collage, typography, or text prohibition.
+- Distinguish a mobile book cover, cinematic key art, interactive-world scene image, character image, and item image. They serve different purposes.
+- In chat, discuss or propose the action. Generate only through the available `generate_cover` confirmation path.
+- Do not promise textual accuracy from an image model. If deterministic title layout is available, separate background generation from typography.
+- Keep the cover faithful to the finished content; do not advertise events absent from the story.
+- Respond in the user's language.
+
+Load `references/cover-brief.md` when converting a manuscript into a production-ready visual brief.

package/skills/inkos-story-cover/references/cover-brief.md

@@ -0,0 +1,16 @@
+# Cover brief
+
+Capture only decisions supported by the user or work:
+
+- artifact type and target platform;
+- aspect ratio and thumbnail context;
+- title treatment requirements, if any;
+- focal subject, expression, pose, and viewpoint;
+- one central conflict signal;
+- one or two legible genre objects;
+- palette, material, lighting, and atmosphere;
+- prohibited elements;
+- continuity references for recurring characters or places;
+- whether typography is image-generated or applied deterministically later.
+
+Evaluate at final size and thumbnail size. A beautiful image that hides genre, conflict, or title hierarchy may still be a poor cover.

package/skills/inkos-story-deslop/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: inkos-story-deslop
+description: 识别并修复空泛、模板化、总结腔和其他AI写作痕迹，同时保留作者声音。Use for semantic prose cleanup, not keyword deletion.
+---
+# Semantic prose cleanup
+
+Use this skill when the user says prose feels generic, mechanical, over-explained, repetitive, or AI-generated.
+
+- Diagnose by reading function and effect, not by counting banned words or applying global replacements.
+- Distinguish a real defect from a legitimate voice choice. Repetition can be rhythm; abstraction can be intentional; short sentences can be pressure.
+- Look for unsupported conclusions, emotion labels without scene evidence, generic transitions, symmetrical canned phrasing, repeated interpretation, decorative detail, summary replacing scenes, and dialogue that only transfers information.
+- In an active book, audit first when scope is unclear. Use the reviser for an authorized rewrite; do not paste a replacement chapter into chat and claim it was saved.
+- Preserve plot facts, viewpoint, character voice, evidence, pacing function, and strong original lines.
+- Respond in the user's language.
+
+Load `references/semantic-cleanup.md` for a passage-level diagnosis or revision brief.

package/skills/inkos-story-deslop/references/semantic-cleanup.md

@@ -0,0 +1,13 @@
+# Semantic cleanup rubric
+
+Ask of every suspect passage:
+
+1. What story function should this passage perform?
+2. Is that function visible through action, image, evidence, choice, or consequence?
+3. Does the narrator explain an emotion already demonstrated?
+4. Could the sentence fit any character or story unchanged?
+5. Is detail carrying evidence, relationship, pressure, or voice?
+6. Is dialogue motivated, or is it disguised exposition?
+7. Does sentence rhythm match the scene's physical and emotional movement?
+
+Repair by restoring concrete cause and character-specific behavior. Do not mechanically delete transitions, metaphors, three-part lists, or every occurrence of a flagged word.

package/skills/inkos-story-import/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: inkos-story-import
+description: 导入已有小说、逆向重建设定与续写工程，并区分母本参考。Use for importing manuscripts or attaching external canon safely.
+---
+# Story import and reconstruction
+
+Use this skill when the user wants an existing manuscript to become an editable, continuable InkOS project.
+
+- Determine the user's intent before acting:
+  - `import_chapters`: the text becomes real chapters in the active book and InkOS reconstructs state.
+  - `ingest_material`: the text remains reference material only.
+  - `manage_book_reference`: an archived source should guide future chapters for user-stated purposes.
+- Preserve chapter order with natural chapter-number ordering. Confirm the continuation point when the active book already has chapters.
+- Never treat a user's own manuscript as an imitation target by default.
+- After import, report imported chapter count, detected gaps, reconstructed facts, uncertainties, and the next safe continuation point.
+- Do not invent missing canon to make the project look complete. Mark uncertainty for later confirmation.
+- Respond in the user's language.
+
+Load `references/reconstruction-rubric.md` for large or inconsistent manuscripts.

package/skills/inkos-story-import/references/reconstruction-rubric.md

@@ -0,0 +1,13 @@
+# Manuscript reconstruction rubric
+
+Reconstruct only what the text supports:
+
+- chapter order and titles;
+- character identity, voice, goals, relationships, and last known state;
+- world rules and exceptions;
+- timeline and location changes;
+- revealed facts versus reader-facing uncertainty;
+- planted, advanced, resolved, and dormant hooks;
+- current conflict, unresolved costs, and immediate continuation pressure.
+
+For contradictions, retain both evidence pointers and mark the conflict. Do not silently choose one version. Imported chapter prose is authoritative unless the user explicitly requests a rewrite or retcon.

package/skills/inkos-story-review/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: inkos-story-review
+description: 按题材、目标读者和用户标准审稿，展示具体问题并协作修订。Use for chapter or manuscript review with transparent criteria.
+---
+# Story review
+
+Use this skill when the user wants diagnosis, scoring, comparison, approval, or revision advice for existing prose.
+
+- First identify the applicable standard from genre, target audience, tone, platform, and explicit user preference. Everyday comedy, literary fiction, romance, mystery, and commercial serials should not share one logic-density threshold.
+- In an active book, use the auditor for persisted chapters. Show concrete issue descriptions, severity, evidence, and likely reader impact.
+- A parser or model-format failure is an audit failure, not evidence that the prose is bad and not permission to rewrite it.
+- Do not revise merely because an audit failed. Revise when the user asks, or when the confirmed workflow authorizes it; report whether the revised artifact was actually applied.
+- Preserve the user's voice and successful passages. Prefer the smallest scope that resolves the real defect.
+- Respond in the user's language.
+
+Load `references/review-matrix.md` for a full review or when standards are disputed.

package/skills/inkos-story-review/references/review-matrix.md

@@ -0,0 +1,21 @@
+# Adaptive review matrix
+
+Always inspect:
+
+- user intent and durable constraints;
+- continuity and causal coherence;
+- character motivation and voice;
+- scene function and consequence;
+- information and evidence consistency;
+- prose clarity and viewpoint stability;
+- promised versus delivered emotion.
+
+Adjust by form:
+
+- Comedy may accept coincidence or exaggeration when setup, rhythm, and character logic support the joke.
+- Romance prioritizes relationship movement, subtext, and emotional credibility.
+- Mystery requires evidence visibility, fair inference, and controlled information release.
+- Commercial serials require continuation pressure without sacrificing scene completeness.
+- Literary work may trade plot velocity for perception, language, or thematic movement, but not for empty repetition.
+
+For every blocking issue, include evidence, impact, and a repair direction. Separate objective contradiction from taste preference.