@kienmatu/inkos-core 0.1.0

package/skills/inkos-storyboard/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: inkos-storyboard
+description: 剧本与叙事文本到可拍、可画、可生图分镜的视觉拆解方法。Used for storyboard and image-prompt production.
+---
+# Storyboard creation
+
+Apply this method inside a confirmed storyboard operation.
+
+- Translate narrative beats into visible shots; do not turn the storyboard into a prose summary.
+- Each shot needs a dramatic purpose, visual subject, action, spatial relation, shot size or camera behavior, and continuity with the shots around it.
+- Preserve screen direction, character appearance, location, props, time, weather, lighting, and emotional progression unless the source deliberately changes them.
+- Use fewer, stronger shots when they communicate the beat. Do not split every sentence mechanically or add decorative coverage with no storytelling function.
+- Image prompts must be generation-ready: subject, action, setting, composition, lighting, mood, and key props are explicit, while unconfirmed visual constraints remain open.
+- Separate what the camera sees from dialogue, captions, sound, and production notes so the result stays editable and shootable.
+- Respect the requested aspect ratio, visual style, granularity, and shot cap.

package/skills/inkos-storyboard/references/shot-continuity.md

@@ -0,0 +1,13 @@
+# Shot continuity
+
+## Shots serve the beat
+
+Use a new shot when information, power, attention, spatial understanding, or emotion changes. Do not convert every sentence into a shot and do not collapse a full dramatic turn into one decorative image.
+
+## Visual continuity
+
+Track screen direction, character position, eyelines, props, lighting, time, and location identity across adjacent shots. Repeated locations should preserve stable visual anchors unless the story explicitly changes them.
+
+## Image prompts remain executable
+
+Describe the visible moment, subjects, composition, camera, environment, light, and required continuity anchors. Avoid abstract story summaries. The prompt should depict the selected beat without adding text, characters, or objects not present in the storyboard.

package/skills/inkos-translation/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: inkos-translation
+description: 长文任意语言互译、术语一致性、分段续跑与章节审校方法。Used by InkOS translation workers.
+---
+# Long-form translation
+
+Apply this method during translation and translation review.
+
+- Preserve meaning, omissions, names, pronouns, chronology, paragraph order, dialogue ownership, formatting intent, tone, and register. Never summarize or expand to make the text easier.
+- Translate for natural target-language reading without erasing the source voice. Resolve ambiguity conservatively and record a note when it materially affects meaning.
+- Treat the project glossary as persistent authority. Reuse established names and terms; add a glossary entry only when it helps later consistency.
+- Keep segment boundaries operational, but read neighboring segments and chapter context as one passage so references and cadence survive batching.
+- During review, check fidelity, missing content, added content, terminology, referents, names, numbers, and target-language readability with concrete evidence.
+- A parser or provider failure is not a translation-quality verdict. Preserve completed segments and resume from the first unfinished segment.

package/skills/inkos-translation/references/long-form-consistency.md

@@ -0,0 +1,13 @@
+# Long-form translation consistency
+
+## Preserve meaning and function
+
+Translate what a passage does as well as what it says: voice, implication, pacing, humor, status, and genre convention. Do not improve, censor, summarize, or continue the source unless the user explicitly requests adaptation.
+
+## Maintain a living glossary
+
+Reuse established names, titles, pronouns, invented terms, and recurring phrases. When context changes the correct rendering, update the glossary with a note rather than allowing silent variation.
+
+## Segment without breaking thought
+
+Keep sentences and tightly connected dialogue turns together when possible. Review at chapter scope so local fluency does not break character voice, references, or terminology across segments.