Standardize ikigai project documentation with YAML frontmatter and structured guidelines.
npx skills add https://github.com/multicam/ikigai-rev --skill docs-multicam
Please help me install this Agent Skill. Skill: docs Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/docs Command: npx skills add https://github.com/multicam/ikigai-rev --skill docs-multicam
Guidelines for writing user-facing documentation in the ikigai project help teams produce consistent and high-quality materials, reducing ambiguity and improving usability.
Draft a complete documentation page following these guidelines.
High-intent search queries and answers about installing and using this skill.
To write consistent project documentation, include YAML frontmatter with name and description fields, followed by a three-section body covering the problem solved, core features, and a concise Quick Start instruction.
User-facing documentation guidelines require a three-section description format: what problem is solved, core features and use cases, and a single-sentence Quick Start that triggers an immediate action without code.
Create a Quick Start instruction by writing a single, concise sentence that triggers an initial action, such as drafting a complete documentation page, without including any code snippets.
Yes, YAML frontmatter with name and description fields is required for architecture notes and project docs to enable consistent authoring and discovery across the documentation.
Standardize documentation authoring by applying structured guidelines that require consistent frontmatter, a three-section description layout, and a single-sentence Quick Start across all user-facing materials.
No, the Quick Start section must be a concise single-sentence instruction that triggers an initial action without relying on code snippets to guide immediate use.
yu13130122297Identify uncertainties in research framing, datasets, metrics, and baselines.
lbliiiMigrates static site and Markdown content to Bengal format.
NVIDIAEnforce ASCII-only, bold-free Markdown documentation style across NVCF repos.
Avi977Apply concise writing rules to documentation drafts and generate structured descriptions.
