brand

Replaces project name tokens across a repository with derived variants.

Updated Feb 7, 2026

Search Tags:#branding #template-branding #token-replacement #project-name #codebase-customization

Ready to run

npx skills add https://github.com/pward17/site-template --skill brand

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brand
Source: https://github.com/pward17/site-template/tree/main/.claude/skills/brand
Command: npx skills add https://github.com/pward17/site-template --skill brand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-time personalization: replace template tokens throughout the codebase with your project's name.

Core Features & Use Cases

Automated derivation of project name variants (display name, kebab, infra) and propagation across repository files.
Systematic token replacement across environment/configuration files, deployment scripts, docs, and CI workflows.
Generates branding metadata and updates configuration to reflect the new branding state.

Quick Start

Run the /brand command and follow the prompts to provide your project's display name.

Frequently Asked Questions about brand

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

FAQPage Schema

How do I replace template tokens with my project name across a codebase?▼

To replace template tokens across a codebase, you can automate one-time project personalization by deriving display, kebab, and infra name variants and performing safe, idempotent replacements in target files and metadata.

What is the best way to automate project branding for initial repository setups?▼

Automating project branding for initial setups involves systematically replacing project name tokens across environment files, deployment scripts, docs, and CI workflows to ensure consistent personalization throughout the repository.

Does template branding apply to both frontend and backend configuration files?▼

Yes, template branding applies to both frontend and backend configuration files, systematically propagating derived project name variants across deployment scripts, docs, and CI workflows during the initial setup.

How do I generate branding metadata and update configuration files?▼

To generate branding metadata and update configuration, you run a token replacement process that derives your project's display name and applies idempotent token substitutions to reflect the new branding state across the repository.

Can I use token replacement for codebase customization on existing projects?▼

Token replacement for codebase customization is designed for one-time personalization during initial project setups, applying safe, idempotent replacements to target files and metadata rather than continuous updates.

Why does my template branding require deriving kebab and infra name variants?▼

Template branding requires deriving kebab and infra name variants to ensure the project name is correctly formatted and propagated across different system layers, including deployment scripts, environment configurations, and infrastructure metadata.