Skip to content

gracefullight/pkgs / .agents/skills/oma-backend

oma-backend

Unverified

Implement server APIs, authentication, and application data access. Schema modeling and query tuning use oma-db.

FileKindSize
SKILL.mdskill md9.9 KB
resources/checklist.mdmarkdown2.1 KB
resources/error-playbook.mdmarkdown3.9 KB
resources/examples.mdmarkdown1.9 KB
resources/execution-protocol.mdmarkdown2.3 KB
resources/orm-reference.mdmarkdown3.9 KB
stack/api-template.tsscript8.8 KB
stack/snippets.mdmarkdown12.2 KB
stack/stack.yamlconfig30 B
stack/tech-stack.mdmarkdown1006 B

resources/checklist.md

View on GitHub
# Backend Agent - Self-Verification Checklist

Run through every item before submitting your work.

## API Design
- [ ] RESTful conventions followed (proper HTTP methods, status codes)
- [ ] OpenAPI documentation complete (all endpoints documented)
- [ ] Request/response schemas defined with validation library
- [ ] Pagination for list endpoints returning > 20 items
- [ ] Consistent error response format

## Database
- [ ] Migrations created and tested
- [ ] Indexes on foreign keys and frequently queried columns
- [ ] No N+1 queries; relation loading strategy chosen explicitly for the ORM in use
- [ ] No over-fetching; selected only required fields/columns/attributes
- [ ] Transactions used for multi-step operations with explicit unit-of-work boundaries
- [ ] ORM session/client/entity-manager lifecycle matches the framework's concurrency model
- [ ] Query risks reviewed: missing indexes, full scans, repeated identical queries, join row multiplication

## Security
- [ ] JWT authentication on protected endpoints
- [ ] Password hashing with Argon2id (bcrypt cost 10-12 acceptable for legacy compatibility)
- [ ] Rate limiting on auth endpoints
- [ ] Input validation enforced (no raw user input in queries)
- [ ] SQL injection protected (ORM or parameterized queries)
- [ ] No secrets in code or logs

## Testing
- [ ] Unit tests for service layer logic
- [ ] Integration tests for all endpoints (happy + error paths)
- [ ] Auth scenarios tested (missing token, expired, wrong role)
- [ ] Project coverage target met; if no target exists, document changed behavior coverage and any justified exclusions

## Code Quality
- [ ] Clean architecture layers: router -> service -> repository
- [ ] No business logic in route handlers
- [ ] Async/await used consistently
- [ ] Type annotations on all function signatures

## Cloud Readiness
- [ ] No hardcoded config values (DB URLs, API keys, ports); all from env vars
- [ ] No in-process state between requests (sessions, caches, counters)
- [ ] Logs written to stdout/stderr, not file; structured format (JSON) preferred
- [ ] Graceful shutdown handled for background jobs and open connections
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