brand-identity-core

Enforce company voice, tone, and formatting standards across technical documentation and outputs.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/narcisolcf/skills_claude_narciso --skill brand-identity-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brand-identity-core
Source: https://github.com/narcisolcf/skills_claude_narciso/tree/main/brand-identity-core
Command: npx skills add https://github.com/narcisolcf/skills_claude_narciso --skill brand-identity-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines the semantic constitution for branding and documentation, ensuring consistent voice, tone, and formatting.

Core Features & Use Cases

  • Voice Rules: Enforce authoritative, concise, constructive communication.
  • Formatting Standards: Guidance for lists, code blocks, and typography in documentation.

Quick Start

Apply the voice and formatting guidelines to technical docs and README comments.

Frequently Asked Questions about brand-identity-core

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

FAQPage Schema
How do I enforce consistent brand voice and tone across documentation and code comments?

Brand voice enforcement establishes authoritative, concise communication standards applied uniformly to technical documentation, code comments, external communications, and internal announcements. This Skill defines and applies your company's voice, tone, and formatting rules to ensure consistency across all outputs.

What formatting standards should I apply to technical documentation?

Formatting standards include consistent terminology usage, bold emphasis for key concepts, bullet-list formatting for itemized content, ISO 8601 date representations, and properly labeled code blocks. These rules ensure documentation readability and professional presentation across your organization.

Can I use this for style guide compliance across multiple output types?

Yes. This Skill satisfies terminology compliance, formatting standards, and style rules across technical documentation, code comments, external communications, internal announcements, and related outputs, enforcing your brand standards everywhere they appear.

How do I ensure consistent terminology usage in my documentation?

Terminology compliance is enforced through defined voice and formatting rules that standardize how terms appear throughout documentation and communications. Apply these standards to guarantee consistent terminology usage across all outputs.

What's the difference between voice rules and formatting standards?

Voice rules enforce authoritative, concise, constructive communication patterns for your brand. Formatting standards provide guidance for lists, code blocks, and typography. Together they ensure both the tone and presentation of your documentation remain consistent.