documentation-paste_analysis_unit_class_method

Generate canonical Analise/ unit and class documentation scaffolds as {ClassName}.md placeholders.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill documentation-paste-analysis-unit-class-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-paste_analysis_unit_class_method
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/documentation-paste_analysis_unit_class_method_V1.2.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill documentation-paste-analysis-unit-class-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides canonical scaffolding for the Analise/ directory's class and unit documentation, ensuring an idempotent structure that can be extended by subsequent content generation.

Core Features & Use Cases

  • Generates a single {ClassName}.md per class (merging I and T content) to enforce canonical naming and domain-scoped organization.
  • Creates domain subfolders under Analise/ derived from src/ with placeholder READMEs to guide documentation creation.
  • Idempotent by design, allowing safe re-runs and integration with documentation generators for detailed body content.

Quick Start

Run this skill to generate the canonical ClassName.md scaffolds in the appropriate Analise/ domain.

Frequently Asked Questions about documentation-paste_analysis_unit_class_method

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

FAQPage Schema
How do I generate class documentation scaffolding from source code automatically?

Class documentation scaffolding is generated by deriving canonical unit and class structures from source code, creating {ClassName}.md placeholder files mapped to canonical domains under the Analise/ directory.

What is the best way to keep unit and class documentation consistent across multiple runs?

Unit and class documentation consistency is maintained through an idempotent scaffolding design that safely merges interface and test content into a single file per class, allowing safe re-runs without duplicating or overwriting existing structures.

How do I organize source code units into domain-specific documentation folders?

Source code units are organized by mapping them to canonical domains, automatically creating domain subfolders under the Analise/ directory derived from the src/ structure with placeholder READMEs to guide documentation creation.

Can I merge interface and test documentation into a single class file?

Interface and test documentation can be merged into a single {ClassName}.md file per class, enforcing canonical naming and domain-scoped organization to ensure structural consistency across the documentation directory.

Does class documentation scaffolding validate existing directory structures before generating files?

Class documentation scaffolding validates existing directory structures before generating files, ensuring the canonical Analise/ structure remains intact and idempotent across subsequent content generation runs.

What should I use to generate detailed documentation body content after scaffolding?

Detailed documentation body content generation should be handled by a documentation-class-analysis-generator, which follows the canonical scaffolding to populate the {ClassName}.md placeholder files with comprehensive analysis.