dcjanus-preferences_skill

Overview

This skill documents DCjanus's preferred third-party libraries and typical usage scenarios across Python, Rust, and Go. It serves as a single reference for dependency selection, replacement, and tooling choices when developing to DCjanus's preferences. The skill is meant to be consulted before proposing or adding libraries so choices align with those preferences.

How this skill works

The skill first confirms the target programming language, then reads the corresponding reference file for that language to obtain ranked preferences and recommended use cases. When proposing to add or replace a dependency, it prioritizes items on the preference list and flags conflicts or gaps. If a language is not covered or there is an unresolved conflict, the skill prompts the user and updates the language reference file with any confirmed additions.

When to use it

• Choosing a third-party library for a new feature in Python, Rust, or Go.
• Replacing an existing dependency and wanting to respect DCjanus's preferences.
• Performing a technical comparison and needing a preferred shortlist to evaluate.
• Onboarding or enforcing a consistent set of libraries across a project that follows DCjanus's tastes.
• Adding support for a new language or filling missing guidance in the references.

Best practices

• Always confirm the target language before consulting the preference list.
• Default to items listed in the language reference unless a clear technical reason favors otherwise.
• Prompt the user when the language is not covered or the preference list conflicts with requirements.
• Record any confirmed additions or changes to the appropriate language reference file.
• Prefer minimal, well-maintained libraries that match the documented use cases.

Example use cases

• Selecting a HTTP client library for a Python microservice while aligning with DCjanus's preferences.
• Comparing serialization crates in Rust and choosing the preferred option from the reference file.
• Swapping a Go logging library to the one listed as preferred to maintain consistency across projects.
• Adding a new language reference when the team starts using a language not yet documented.