novel-setup

To install novel writing toolkits into a specific project, this skill copies the complete distribution of novel agents, commands, and templates from the global package directly into the project's .claude directory. This ensures project-local isolation and seamless onboarding for independent operation.

Project-local isolation for Claude Code workflows prevents global namespace pollution by deploying versioned tooling assets, such as agents and templates, directly into the project's local .claude directory. This enables per-project versioning and consistent, independent workflow execution.

Yes, you need a global distribution installed because this skill copies the seven novel agents, four commands, one skill, and four templates from the global package into the project's .claude directory to configure the automated workflow.

Yes, you can use this automated configuration to update novel tooling across multiple projects. It supports project-level configuration and versioned deployment to maintain a consistent workflow while keeping each project's assets isolated within its own .claude directory.

The best way to prevent global namespace pollution when distributing novel templates is to use project-scoped isolation. This skill copies the four templates and seven agents from the global distribution into the local project .claude directory, ensuring independent operation without affecting global configurations.