Assess a third-party package before adding, updating, or removing it. Check whether it is needed, its security and maintenance history, install scripts, license, dependency tree, and shipped size, then place and pin it according to the project’s rules.
- Evaluating a package before installing it
- Comparing a library with a small custom implementation
- Checking risks before bumping a dependency version
kromatv/kroma☆ 81Updated Nov 17, 2026
Decide when and where to split an oversized or mixed-purpose code file. Use practical size guidance, natural boundaries, dependency direction, and project conventions to place code in a module that keeps one clear responsibility.
- Choosing where a new function or module belongs
- Splitting a file that has grown too long
- Reviewing whether a file has multiple responsibilities
kromatv/kroma☆ 69Updated Oct 31, 2026
Choose clear names and locations for files, directories, tests, and symbols by learning a project's existing conventions. Get guidance on language-specific casing, platform and test suffixes, component folders, and names that obscure purpose or version history.
- Choosing a name and location for a new file
- Naming a test or platform-specific variant
- Renaming a symbol to clarify its purpose
kromatv/kroma☆ 69Updated Oct 31, 2026
Use this skill to review comments in a specified file or diff, verify reported issues, and fix accepted findings within scope. It can also propose enforcing claimed constraints through types, runtime checks, tests, or CI lint, then report remaining work.
- Reviewing comments in a code diff
- Removing comments that hide correctness or safety issues
- Turning a code constraint into a test or lint rule
kromatv/kroma☆ 69Updated Oct 31, 2026
Turn pull requests since the previous release into concise, user-facing notes that explain what people can now do. The skill prioritizes noticeable changes, respects a length budget, writes each language from the intended meaning, and traces every note to its source PR.
- Prepare notes when cutting a release
- Fill a GitHub Release description
- Write an app store or in-app what's new entry
kromatv/kroma☆ 69Updated Oct 31, 2026
Use this skill when editing Rust code, shaping a crate’s public API, handling errors, or writing Tokio async code. It offers practical guidance on types, borrowing, safety, testing, and linting to help keep invalid states and common runtime mistakes out of a project.
- Reviewing Rust code for idiomatic patterns
- Choosing error types for a library or binary
- Designing a crate's public API and newtypes
kromatv/kroma☆ 69Updated Oct 31, 2026