Companies

Summarize Victoria 3 company definition workflows and validation rules.

21|8|Updated Jun 23, 2025
One-click install
npx skills add https://github.com/mattia2110/tech-and-res --skill companies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Companies
Source: https://github.com/mattia2110/tech-and-res/tree/main/.agents/skills/companies
Command: npx skills add https://github.com/mattia2110/tech-and-res --skill companies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides guidance for creating, editing, or reviewing Victoria 3 company definitions across common/company_types, including new types, vanilla overrides, dynamic naming, AI behavior, and prestige goods support.

Core Features & Use Cases

  • Ensures consistent placement and references to vanilla and modded company files.
  • Outlines workflow for adding or overriding companies, including validation of building types, icons, and localization.
  • Provides a structured process to inspect related files and maintain naming and scope rules.

Quick Start

Follow the workflow to add or modify a company in common/company_types and validate all references.

Frequently Asked Questions about Companies

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

FAQPage Schema
How do I add new company definitions in Victoria 3?▼

To add new company definitions in Victoria 3, place files in the common/company_types directory, validate building types and icons, and enforce naming consistency across regional files to ensure proper localization.

What is the workflow for overriding vanilla companies in Victoria 3?▼

Overriding vanilla companies in Victoria 3 requires editing files in common/company_types, validating references to building types and icons, and maintaining YAML keys and frontmatter to ensure scope rules.

How do I validate localization consistency for Victoria 3 company mods?▼

To validate localization consistency for Victoria 3 company mods, inspect referenced files, enforce naming rules across regional files, and verify that YAML keys and triggers align with your company definitions.

Do I need frontmatter and YAML keys for Victoria 3 company types?▼

Yes, frontmatter presence and YAML keys are required for Victoria 3 company types to define triggers, validate building types, and maintain AI behavior and prestige goods support.

Can I modify Victoria 3 company definitions for prestige goods and AI behavior?▼

Yes, you can modify Victoria 3 company definitions to support prestige goods and adjust AI behavior by editing common/company_types files and validating building types, icons, and localization references.

Why are my Victoria 3 company overrides not working?▼

Victoria 3 company overrides may fail if frontmatter is missing, YAML keys are incorrect, or building types, icons, and localization references are not properly validated across regional files.