Skip to content

Vinix24/vnx-orchestration / skills/backend-developer

backend-developer

Verified

Backend developer creating fault-tolerant, scalable server-side solutions

FileKindSize
SKILL.mdskill md6.6 KB
references/_MAPPING.mdmarkdown444 B
scripts/intelligence.shexecutablescript1.2 KB
template.mdmarkdown1.5 KB

references/_MAPPING.md

View on GitHub
# Reference Mapping for backend-developer

These references are project-specific and created during deployment.
Below is the recommended mapping for your project:

| Reference | Target |
|-----------|--------|
| `implementation.md` | `YOUR_PROJECT_DOCS/20_IMPLEMENTATION.md` |
| `services.md` | `YOUR_PROJECT_DOCS/25_SERVICES.md` |
| `extractors.md` | `YOUR_PROJECT_DOCS/30_EXTRACTORS.md` |
| `plugins.md` | `YOUR_PROJECT_DOCS/35_PLUGINS.md` |
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall