SillyTavern Card Pipeline

Shared communication

Apply TW plain-language and guidance rules to user-facing work. Explain terms in context; preserve the user's chosen 新人/入门/熟练/老手 level without inferred changes. 新人 and 入门 receive detailed explanations; every level receives needed and bug explanations unless the user explicitly waives that scope. Soul and prose modes never disable this baseline. Load the shared reference for task entry, level management, or explanation decisions.

Drive the target repository's workflow without pretending this skill ships a build engine. Discover and verify the project's own tools, map them to a small adapter contract, and keep configuration, source, and artifacts in distinct layers.

Before a write, build, or package action, use $consult-tavernweave-library with the sillytavern-card-pipeline route. Read A0 and the returned build/deployment guides, then keep the route receipt beside the preflight evidence.

Record capability-specific evidence with acceptance-ledger.md. Keep source, automated, offline artifact, browser, real SillyTavern, human, and release gates separate; automation never writes driver-accepted.

Confirm the requested gate

Classify the request before running any mutating command: