cst-core-protect

Guard core CaptainSkillTree files from unauthorized edits and enforce separate file implementations.

1|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-core-protect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cst-core-protect
Source: https://github.com/KorCaptain/Valheim_Captain_SkillTree/tree/main/.claude/skills/cst-core-protect
Command: npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-core-protect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental or unauthorized modifications to the core SkillTree plugin code to preserve stability and predictable behavior during development and maintenance.

Core Features & Use Cases

  • Guards critical files such as Plugin.cs and SkillTreeInputListener.cs from direct edits and risky patches.
  • Enforces a policy to implement new features in separate files or classes, avoiding changes to core logic.
  • Provides clear guidelines for engineers and moderators to maintain integrity across updates and deployments.

Quick Start

Do not modify Plugin.cs or SkillTreeInputListener.cs; implement changes in a new, separate file instead.

Frequently Asked Questions about cst-core-protect

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

FAQPage Schema
How do I prevent accidental edits to core mod files during development?

Preventing unauthorized edits to core mod files involves enforcing separation of concerns and using guarded entry points, requiring all new features to be implemented in separate files rather than modifying core logic directly.

Why should I avoid modifying Plugin.cs and SkillTreeInputListener.cs directly?

Avoiding direct modifications to Plugin.cs and SkillTreeInputListener.cs preserves core stability and predictable behavior, ensuring that essential plugin logic remains intact during maintenance and updates.

What is the best way to add new features without changing core mod logic?

The best way to add features without altering core mod logic is to implement changes in a new, separate file or class, adhering to a policy of separation of concerns to maintain code integrity.

Can I use code protection rules for CaptainSkillTree modding across different environments?

Code protection rules apply to editing Plugin.cs and related core components across development environments, requiring explicit file separation and code review to ensure safe updates and core integrity.

When do I need explicit file separation for mod development?

Explicit file separation is needed when implementing new SkillTree plugin features, ensuring that changes are isolated from guarded entry points to prevent unauthorized patches and maintain safe deployments.