Vinix24/vnx-orchestration / skills/backend-developer
backend-developer
VerifiedBackend developer creating fault-tolerant, scalable server-side solutions
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.6 KB |
| references/_MAPPING.md | markdown | 444 B |
| scripts/intelligence.shexecutable | script | 1.2 KB |
| template.md | markdown | 1.5 KB |
template.md
View on GitHub# Backend Developer Report Template
## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`
## Filename Format
`{timestamp}-{track}-{title}.md`
Example: `20260202-143000-A-authentication-implementation.md`
## Report Structure
### Summary
Brief overview of what was accomplished (2-3 sentences)
### Tags (Required)
- [tag1, tag2, tag3] # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.
### Implementation/Investigation
- What was built/analyzed
- Technical approach taken
- Key decisions made
### Code Changes
- Files modified/created
- Key functions/classes added
- Database changes (if any)
### Testing
- Tests added/modified
- Test coverage metrics
- Validation results
### Evidence
- Working code examples
- Test output
- Performance metrics (if applicable)
### Open Items
<!-- List any unfinished work, blockers, or issues discovered -->
<!-- Format: - [ ] [severity] Title (optional details) -->
<!-- Severities: [blocker], [warn], [info] -->
<!-- Example: - [ ] [blocker] Missing error handling in auth module -->
<!-- Leave empty if all work completed -->
### Recommendations
- Next steps
- Potential improvements
- Technical debt items
### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []
## Quality Standards
- Include actual code snippets
- Provide test evidence
- Document API changes
- List all dependencies added
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |