Skip to content
cccskills
FreePublished on GitHub

reference-first

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.

OriginalShow the original description

Ground platform and integration code in documented facts instead of memory. Before writing code that depends on how an external platform, SDK, protocol or vendor behaves (key names, manifest fields, event payloads, threading rules, supported formats, store requirements), read the project's reference docs for that area; when the fact is missing, research it from the official source, cite it, and add it to the reference in the same change. Use when implementing or debugging native, OS, device, SDK or third-party integration code, or when a behaviour "should" work a certain way. Triggers - "how does the platform handle", "what key name", "is this supported on", "according to the docs", "port to a new platform", "native module", "why does the TV".

kromatv/kroma73 stars(GitHub 73 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Implementing a native or third-party SDK integration
  • Checking a platform-specific setting or event format
  • Debugging behavior that differs across devices
  • Porting an integration to a new platform

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-dependency

FreeSummary

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/kroma81Updated Nov 17, 2026

file-structure

FreeSummary

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/kroma69Updated Oct 31, 2026

naming

FreeSummary

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/kroma69Updated Oct 31, 2026

no-comments

FreeSummary

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/kroma69Updated Oct 31, 2026

release-notes

FreeSummary

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/kroma69Updated 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/kroma69Updated Oct 31, 2026

See all skills by kromatv

Report a problem with this skill