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
Check project references and authoritative documentation before coding against platform, SDK, protocol, or vendor behavior. Record sourced facts, version scope, and device observations so integration work and debugging rely on traceable evidence instead of assumptions.
- Implementing a native or third-party SDK integration
- Checking a platform-specific setting or event format
- Debugging behavior that differs across devices
kromatv/kroma☆ 73Updated Nov 5, 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