write-for-ai

Generate template-driven README, CLAUDE.md, AGENTS.md, commit messages, and PR bodies.

50|2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/subinium/vibesubin --skill write-for-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-for-ai
Source: https://github.com/subinium/vibesubin/tree/main/plugins/vibesubin/skills/write-for-ai
Command: npx skills add https://github.com/subinium/vibesubin --skill write-for-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-ready project documentation creation to help future AI sessions understand a repo by providing consistent, template-driven docs.

Core Features & Use Cases

  • Template-driven document generation: applies the project-wide templates in templates/ to README, CLAUDE.md / AGENTS.md, commit messages, and PR bodies.
  • Invariant- and template-based governance: structures docs to preserve rules and verification steps for future sessions.
  • Safe, surgical edits: rewrites existing docs without losing critical information, preserving structure and references.
  • AI-friendly repo map and provenance: produces clear, navigable pointers and standardized layouts to ease AI comprehension.

Quick Start

Apply the templates in templates/ to generate AI-friendly README, CLAUDE.md/AGENTS.md, commit messages, and PR bodies for this repository.

Frequently Asked Questions about write-for-ai

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

FAQPage Schema
How do I generate AI-friendly project documentation for a new repository?

Generate AI-friendly project documentation by applying template-driven layouts to README.md, CLAUDE.md, and AGENTS.md files. This enforces machine-readable structures and frontmatter validity, helping future AI sessions understand the repository state.

What is the best way to write commit messages and PR bodies for AI comprehension?

Writing AI-friendly commit messages and PR bodies involves applying standardized templates from a repository's templates directory. This enforces consistent, machine-readable structures that preserve invariants and verification steps for future AI sessions.

How can I rewrite existing README files without losing critical references?

Rewrite existing documentation safely using surgical edits that apply template-driven layouts while preserving structure, critical information, and references. This ensures AI-friendly repo maps maintain their provenance without losing prior context.

Does this template-based documentation approach work for cold starts?

Yes, template-based documentation works for cold starts by applying project-wide templates to generate README, CLAUDE.md, and AGENTS.md files. This creates standardized, navigable pointers that ease AI comprehension during initial repository interactions.

When do I need to enforce frontmatter validity and invariants in AI docs?

Enforce frontmatter validity and invariants when generating AI documentation to preserve rules and verification steps for future sessions. This template-based governance ensures consistent, machine-readable structures across README files and PR descriptions.