Match Jclaus Style

Match Jclaus Style

Overview

Use this skill as a preference layer for coding tasks, not as a replacement for reading the current repository. The active repo and nearby code always win when they conflict with this profile.

Workflow

1. Identify the active repo and task surface.
2. Read nearby files, package scripts, tests, and config before editing.
3. Read references/repo-corpus.md to confirm whether the repo should influence Joseph's style profile.
4. Read references/coding-style.md before making implementation choices.
5. For React work, inspect existing component folders and test setup before choosing file layout or test tools.
6. Make the smallest coherent change that fits the local owner module.
7. Verify with the repo's existing scripts when practical, and report any command that could not be run.

Style Priorities

• Preserve the local repo's module system, formatting, quotes, and testing style.
• Prefer direct, feature-local implementation over broad abstraction.
• Use descriptive domain names and practical helper functions.
• Keep unrelated refactors and formatting churn out of the diff.
• In React projects, add React Testing Library functional coverage and Playwright e2e coverage when the app can reasonably run in-browser.
• Give backend and server-side changes unit tests at minimum.
• Put React components in their own files and organize UI folders in the same style as Joseph's other React projects.
• Comment larger or non-obvious blocks so a human reader can quickly see what the block achieves.

Reference Files

• references/repo-corpus.md: included and excluded repositories for style inference.
• references/coding-style.md: concrete implementation preferences extracted from the selected repos.