blueprint:good-pattern

To capture reusable code patterns, provide a file path or description to the skill. It parses the input, reads the target source file, and stores a standardized pattern template under patterns/good/ to enforce consistency across your codebase.

Documenting coding standards is done by extracting recurring code structures into reusable templates. This skill parses your source files and saves standardized pattern templates under patterns/good/, reducing code duplication and drift across your codebase.

Yes, you can extract a code pattern template using a descriptive text input instead of a file path. The skill operates by parsing a provided path or description, locating the target file content, and storing the validated pattern for reuse.

No external dependencies are required to automate code pattern extraction. The skill requires minimal setup and independently handles parsing, reading, and storing standardized patterns under patterns/good/ for your codebase.

Extracting code patterns into reusable templates reduces duplication and drift in your codebase. It helps teams enforce consistency by converting recurring source code structures into standardized references under patterns/good/.

Extracted code patterns are stored as standardized templates under the patterns/good/ directory. The skill creates a file named patterns/good/[name].[ext] and provides a final report of the extraction for team reuse.