Define repository documentation standards with YAML frontmatter and Markdown guidance.
npx skills add https://github.com/pirog/me --skill tanaab-documentation
Please help me install this Agent Skill. Skill: tanaab-documentation Source: https://github.com/pirog/me/tree/main/skills/tanaab-documentation Command: npx skills add https://github.com/pirog/me --skill tanaab-documentation
Guides teams on repository documentation strategy, README structure, inline code and API documentation standards, and the escalation path to fuller documentation under the Tanaab coding structure.
Run the tanaab-documentation skill to outline repository documentation standards and mapping to the project’s docs strategy.
High-intent search queries and answers about installing and using this skill.
Repository documentation standards depend on project type to determine whether to use a full README, a docs wrapper, or a dedicated documentation site. This approach maps content to different user journeys, aligning onboarding, contributor guidance, and durable reference surfaces across multiple repositories.
You establish README structure conventions and API documentation policies by applying durable repository documentation standards. This process defines inline code guidelines and API documentation policies, creating an escalation path to fuller documentation under the Tanaab coding structure.
A dedicated docs site is needed when project complexity exceeds standard README capacity. You decide whether to use a full README, a docs wrapper, or a dedicated docs site by applying documentation strategy standards that map content to specific user journeys and contributor guidance.
Yes, the documentation governance approach requires a YAML frontmatter containing name and description fields. It also requires a Markdown body with actionable instructions to satisfy frontmatter-based discovery and structured documentation guidance across repository documentation.
You align onboarding and contributor guidance across multiple repositories by enforcing durable documentation standards. This strategy establishes consistent README structures, inline code guidelines, and API documentation policies, ensuring durable reference surfaces are mapped correctly for all project types.
Markdown templates for API documentation are limited when project complexity requires a full documentation site. The documentation strategy defines an escalation path, guiding teams on when to transition from standard READMEs or docs wrappers to dedicated documentation sites for comprehensive API guidance.
tomhouleDefine and validate SKILL.md frontmatter files for agent capability discovery.
kivo360Generate standardized CLAUDE.md project guidance templates with QA validation.
pirogEnforce shared coding doctrine across the Tanaab coding stack.
JotJuniorScaffold numbered documentation directories with template READMEs from config.json.
