auctra-i18n-workspace-router

Routes Auctra localized workspace configuration, migration, and display-path requests to real CLI commands.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/yeisme/auctra-novel-skills --skill auctra-i18n-workspace-router-yeisme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auctra-i18n-workspace-router
Source: https://github.com/yeisme/auctra-novel-skills/tree/main/auctra-runtime/auctra-i18n-workspace-router
Command: npx skills add https://github.com/yeisme/auctra-novel-skills --skill auctra-i18n-workspace-router-yeisme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auctra projects with localized workspaces (such as zh-CN chinese-novel layouts) mix human-facing display directories like 章节/ and 大纲/ with a machine-owned .auctra/ source of truth. Without clear routing, agents may hand-edit .auctra files, misuse display_path fields, or run the wrong CLI commands during project setup, migration, import, and export. ## Core Features & Use Cases - Workspace Routing: Decides whether a request needs project init, layout plan/apply, directory explanation, import/export, or handoff to a creative writing skill. - Real CLI Command Guidance: Provides verified commands such as auctra project init --locale zh-CN --layout chinese-novel --json and auctra project layout plan/apply with confirmation gates. - Boundary Enforcement: Prevents direct writes to .auctra/project.yaml, .auctra/runs, .auctra/review, SQLite rows, and review decisions, keeping machine state CLI-owned. - Use Case: A user asks to migrate a legacy novel project to Chinese display directories; the Skill routes them to run auctra project layout plan first, then only suggests apply --yes --json after explicit confirmation. ## Quick Start Ask the agent to check whether your Auctra project needs a zh-CN chinese-novel layout and which CLI command to run next.

Frequently Asked Questions about auctra-i18n-workspace-router

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

FAQPage Schema
How do I create a Chinese novel project with the Auctra CLI?▼

Run auctra project init with the --locale zh-CN and --layout chinese-novel flags plus --json, for example: auctra project init ./chichao --title "赤巢备案" --genre "玄幻悬疑" --locale zh-CN --layout chinese-novel --json. Then hand off first-round material and chapter planning to the project starter skill.

How do I migrate a legacy Auctra project to Chinese display directories?▼

First run auctra project layout plan with --locale zh-CN --layout chinese-novel --json to preview the change. Only after the user explicitly confirms should you suggest auctra project layout apply with --yes --json.

What is the difference between display directories and the .auctra folder?▼

Directories like 章节/, 大纲/, 设定/, 人物/, 素材/, 伏笔/, 审稿/, and 导出/ are human-facing display directories, while .auctra/ is the machine source of truth. Agents must never hand-write .auctra files, SQLite rows, or review evidence.

Can I import chapters and materials using Chinese display paths?▼

Yes, display paths are allowed for import and export, such as auctra chapter import markdown ./章节 or auctra material add --from 素材/备案制度.md. Chapter export defaults to the 导出/ directory.

Does a localized workspace mean the Auctra scenario is fully supported?▼

No, a localized workspace does not imply scenario first-support or maturity. Readiness still depends on gates, review evidence, export and handoff results, and integration evidence.