Skip to main content
GitHub-Repository

libsignal_dart

libsignal_dart enthält 8 gesammelte Skills von djx-y-z, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.

gesammelte Skills
8
Stars
8
aktualisiert
2026-07-17
Forks
2
Berufsabdeckung
2 Berufskategorien · 100% klassifiziert
Repository-Explorer

Skills in diesem Repository

release-frb-crate
Softwareentwickler

Release a new libsignal_frb native crate version (stage 1 of the two-stage release). Use when the user wants to build/publish new native binaries after libsignal dependency updates, bump the libsignal_frb crate, or push a libsignal_frb-* tag. NOT for the Dart pub.dev release (that is release-package).

2026-07-17
release-package
Softwareentwickler

Prepare a new version of libsignal for publication to pub.dev. Use when user wants to release, publish, or tag a new version of the package.

2026-07-17
update-libsignal
Softwareentwickler

Update libsignal native library version. Use when checking for updates, upgrading libsignal, bumping version, or updating native dependencies.

2026-07-13
stores-implementation
Softwareentwickler

Implement Signal Protocol stores for libsignal_dart. Use when implementing SessionStore, IdentityKeyStore, PreKeyStore, SignedPreKeyStore, KyberPreKeyStore, or SenderKeyStore for production use.

2026-04-03
build-native
Softwareentwickler

Build libsignal native libraries for different platforms. Use when user asks about building, compiling, or creating native libraries for iOS, Android, macOS, Linux, or Windows.

2026-02-15
frb-patterns
Softwareentwickler

Flutter Rust Bridge patterns and best practices for libsignal. Use when writing Rust API code, adding new bindings, implementing DartFn callbacks, or troubleshooting FRB issues.

2026-02-08
update-template
Softwareentwickler

Update copier template version. Use when checking for template updates, running copier update, or applying template changes to the project structure.

2026-02-05
security-review
Informationssicherheitsanalysten

Review libsignal Dart code for security issues. Use when reviewing code changes, checking for proper API usage, verifying secure patterns, or auditing cryptographic code.

2026-01-24