leszekgruchala/buddy / skills/implement
implement
VerifiedBuild or fix decision-complete code directly, or execute an approved spec with verification; unresolved product/architecture decisions require spec. Keep the current request in this skill; route new requests by their own scope.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.2 KB |
| reference.md | markdown | 4.3 KB |
| references/java-kotlin.md | markdown | 1.3 KB |
| references/python.md | markdown | 1.2 KB |
| references/typescript-javascript.md | markdown | 1.2 KB |
references/java-kotlin.md
View on GitHub# Java and Kotlin
Follow repository versions, frameworks, compiler settings, and conventions.
1. Give identifiers, units, money, validated values, and other non-interchangeable concepts dedicated types—not `String`, `Long`, or other primitives.
2. Use Java records/final value objects or Kotlin data/value classes; validate on construction and keep them immutable.
3. Use enums for closed constants and sealed types for variants with distinct data/behavior; require exhaustive handling where supported.
4. Prefer narrow visibility and explicit nullability; avoid sentinel primitives or nullable values when domain types can express the states.
5. Add interfaces only for meaningful contracts/boundaries and inheritance only for genuine substitutability.
6. Own resources with try-with-resources/`use`. Catch specific exceptions only to recover, translate, or add context.
7. Prefer clear loops/collection operations over dense streams/chains. Avoid reflection, raw types, unchecked casts, and serialization machinery unless required.
8. Kotlin: prefer `val`, immutable collection interfaces, top-level functions, and structured concurrency; never launch unowned coroutines.
9. Avoid `!!` and unclear scope-function chains. State public types at library and Java/platform boundaries; do not mechanically translate Java patterns into Kotlin.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |