gracefullight/pkgs / .agents/skills/oma-backend
oma-backend
UnverifiedImplement server APIs, authentication, and application data access. Schema modeling and query tuning use oma-db.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.9 KB |
| resources/checklist.md | markdown | 2.1 KB |
| resources/error-playbook.md | markdown | 3.9 KB |
| resources/examples.md | markdown | 1.9 KB |
| resources/execution-protocol.md | markdown | 2.3 KB |
| resources/orm-reference.md | markdown | 3.9 KB |
| stack/api-template.ts | script | 8.8 KB |
| stack/snippets.md | markdown | 12.2 KB |
| stack/stack.yaml | config | 30 B |
| stack/tech-stack.md | markdown | 1006 B |
resources/execution-protocol.md
View on GitHub# Backend Agent - Execution Protocol
## Preparation
Use the task's scope, existing project conventions, and acceptance criteria. Follow `../../_shared/core/execution-policy.md` when it has not already been supplied. Read only references needed by the selected operation; consult lessons or recovery guides for an observed issue. Expand planning depth only when the change requires it.
## Step 1: Analyze
- Read the task requirements carefully
- Identify which endpoints, models, and services are needed
- Inspect existing structure and relevant symbols via `../../_shared/core/code-intelligence.md`; if the configured provider is unavailable, use native search only for paths outside this project or ignored paths
- If the task is ORM-heavy, load `resources/orm-reference.md` before deciding on loading strategy, transaction scope, or client/session lifecycle
- List assumptions; ask if unclear
## Step 2: Plan
- Decide on file structure: models, schemas, routes, services
- Define API contracts (method, path, request/response types)
- Plan database schema changes (tables, columns, indexes, migrations)
- Plan relation loading strategy, transaction boundary, and ORM lifecycle constraints explicitly
- Identify security requirements (auth, validation, rate limiting)
## Step 3: Implement
- **Honor the task's `test_approach`** (see `../../_shared/core/test-approach.md`): for `tdd` tasks, write and run the focused test first (record the RED failure), make the minimal change (GREEN), then continue; for `tdd` the test comes before item 3 below
- Typical affected files (choose an order from actual dependencies):
1. Database models + migrations
2. Validation schemas (request/response)
3. Service layer (business logic)
4. API routes (thin, delegate to services)
5. Tests (unit + integration)
- Use `stack/api-template.*` as reference
- Follow clean architecture: router -> service -> repository -> models
## Step 4: Verify
- Check applicable items in `resources/checklist.md`
- Use `../../_shared/core/common-checklist.md` only for cross-domain verification
- Ensure affected tests and required project checks pass
- For `tdd` tasks, append the `TDD_EVIDENCE` block (test command, RED, GREEN) to the result file per `../../_shared/core/test-approach.md`
- Confirm OpenAPI docs are complete
## On Error
See `resources/error-playbook.md` for recovery steps.
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 |