Coding Fingerprint Wizard

Create a reusable coding fingerprint from example projects.

The goal is not to infer formatter trivia or generic "clean code" advice. The goal is to identify the decisions that make a person's work recognisable: how they shape modules and repositories, where they validate, what they test, what they document, how they use frameworks, what they refuse to abstract, and which trade-offs they make repeatedly.

The output is a coding-fingerprint-[name]/SKILL.md file that another agent can apply when planning, writing, reviewing, or refactoring code.

When To Apply

Use this skill when the user wants to capture a person's:

• coding style
• engineering principles
• repo-shaping preferences
• architectural tendencies
• testing and validation habits
• abstraction thresholds