Skip to content

leszekgruchala/buddy / skills/implement

implement

Verified

Build 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.

FileKindSize
SKILL.mdskill md10.2 KB
reference.mdmarkdown4.3 KB
references/java-kotlin.mdmarkdown1.3 KB
references/python.mdmarkdown1.2 KB
references/typescript-javascript.mdmarkdown1.2 KB

references/python.md

View on GitHub
# Python

Follow the repository's Python version, frameworks, type checker, formatter, linter, and conventions.

1. Type every function input/return. Run the configured `mypy`, `ty`, or equivalent; never weaken checks to silence errors.
2. Model identifiers/non-interchangeable primitives with `NewType` for static distinction or frozen dataclasses/value objects for runtime validation/behavior.
3. Use `Enum`/`StrEnum` for runtime closed sets, `Literal` for small static-only sets, and unions with exhaustive narrowing for variants.
4. Prefer precise types/protocols and `object` over `Any` for unknown values; avoid unstructured dictionaries/tuples as domain objects.
5. Prefer functions, dataclasses, and composition over class hierarchies; use context managers for owned resources.
6. Never use mutable default arguments. Avoid metaprogramming and dynamic attribute tricks without a required use case.
7. Catch the narrowest useful exception; never use bare `except` or silently discard errors.
8. Keep comprehensions simple; use explicit control flow when it communicates intent better.
9. Validate external data and construct typed domain values at runtime boundaries; type hints do not enforce runtime correctness.
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: 469kUpdated Claude CodeCodexVerifiedInstall
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: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 321kUpdated Claude CodeCodexVerifiedInstall