docs

Enforce consistent voice and structure across Tale documentation pages.

20|5|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/tale-project/tale --skill docs-tale-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/tale-project/tale/tree/main/.claude/skills/docs
Command: npx skills add https://github.com/tale-project/tale --skill docs-tale-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tale's docs historically drifted in voice and structure across pages and locales, making it hard for readers to trust the guidance. This skill defines a single narrator, standard openings and closings, and explicit rules that apply to English content while coordinating with translation workflows.

Core Features & Use Cases

  • Establishes a unified voice and page-shape for docs/ (opening, body, closing) and the role of tests to enforce consistency.
  • Provides companion guidance for cross-locale work via the translation skill to keep EN, DE, FR aligned.
  • Covers page-types playbooks, worked examples, mechanics, screenshots, and the docs build workflow.

Quick Start

Open a docs page and apply the Tale voice rules to craft a compliant opening, body, and closing.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I maintain a consistent documentation voice across multiple pages?

To maintain a consistent documentation voice, define a single narrator with standard openings, bodies, and closings. This skill enforces those structure rules through tests, ensuring uniform style across all pages and eliminating narration drift.

How do I keep translated documentation aligned with the English source?

Keep translated documentation aligned by applying cross-locale rules that coordinate English, German, and French content. This skill provides companion guidance for translation workflows to ensure structural and stylistic parity across all locales.

What is the best way to enforce markdown frontmatter and page structure in docs?

The best way to enforce markdown frontmatter and page structure is through automated tests. This skill defines standard page shapes and uses testing to validate frontmatter, ensuring every documentation page meets compliance requirements.

Can I use this documentation skill for localized pages and navigation builds?

Yes, you can use this documentation skill for localized pages and navigation builds. It applies consistency rules to all content under the docs directory, covering multi-locale pages, navigation elements, and the build workflow.

Why do my documentation pages sound inconsistent across different sections?

Documentation pages sound inconsistent when they lack a unified voice and standard structural rules. Without enforced page shapes and a single narrator, voice drift occurs naturally across different sections and translations.