- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add first-fluke/oh-my-agent --skill oma-backend -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add first-fluke/oh-my-agent --skill oma-backend -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add first-fluke/oh-my-agent --skill oma-backend -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add first-fluke/oh-my-agent --skill oma-backend -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-backendपब्लिशर से
Implement or review backend APIs, authentication, database integration, server-side business logic, and migrations using the project's existing backend stack and clean architecture boundaries.
oma-dbProject stack manifests and existing backend conventions
resources/execution-protocol.md, resources/checklist.md, and resources/orm-reference.md
Optional stack reference (stack/, or the matching variants/<language>/): stack.yaml, tech-stack.md, snippets, and API templates
The project's own toolchain: ORM or database client, and its test, lint, typecheck, and migration commands
Database, queue, cache, mail, auth, or external API resources configured through environment or secret managers
resources/orm-reference.md.oma-db./stack-set.Detect the stack (see Stack Detection) and identify the affected router, service, repository, model, migration, and test boundaries.
Locate files and inspect symbols or content with the configured code-intelligence provider. For Serena, use find_file, search_for_pattern, get_symbols_overview, and find_symbol. Native search is limited to the provider exclusions and non-code paths permitted by the project's search policy.
Read the existing routes, services, repositories, models, schemas, and config. Load a stack-specific reference only when the task needs it.
Implement the change with validation, business logic, persistence, and tests, following the Core Rules.
Select the project's verification commands (lint, typecheck, tests, and migrations when schema changes are involved), preferring the verify: commands in stack/stack.yaml when present. Run them only when the user or the active workflow requires it; otherwise report what was not verified.
Review the applicable checklist items and report the changed behavior, the verification status, and unresolved risks.
Reads and edits backend source, tests, schemas, and migrations. A change may alter the database schema, API or auth behavior, or a service contract, and may require regenerated clients or migration artifacts. Credentials (DB URLs, API keys, secrets) stay in the environment or a secret manager; external APIs and backing services are called only when the task requires them.
Apply framework, library, architecture, and data-model defaults only when the target project has no established choice. Scoped edits do not authorize a stack migration or unrelated infrastructure.
Router (HTTP) → Service (Business Logic) → Repository (Data Access) → Models
// TODO(oma-deferred): integrate <vendor> when key is provisioned, and label its output as simulated. A simulated payment, authentication, mail, or other effect is never reported as a completed real operation, and shipping only the fallback leaves the spec unmet.stack/ when present; otherwise the matching variants/<language>/. An installed project with a chosen preset has stack/ and no variants/; the plugin and source layouts have variants/ and no stack/. Treat it as supplementary reference for coding conventions and snippet templates/stack-setFile names are relative to the stack reference directory selected above.
stack.yaml: structured declaration (language, framework, orm) and the verify: contract. oma verify agent backend runs the verify: block of stack/stack.yaml. The manifest's JSON Schema is variants/stack.schema.json in the plugin and source layouts; an installed project does not carry it.tech-stack.md: human-readable reference only; stack.yaml wins on conflict.snippets.mdapi-template.*Stack generation spec: resources/stack-generation.md (loaded by /stack-set when it generates this skill's stack/)
Local code tools: ../_shared/core/code-intelligence.md (code search/navigation)
Execution steps (follow for the selected task): resources/execution-protocol.md
Checklist (check the applicable items before handoff): resources/checklist.md
ORM reference: resources/orm-reference.md
Error recovery: resources/error-playbook.md
Context loading: ../_shared/core/context-loading.md
Clarification: ../_shared/core/clarification-protocol.md
Context budget: ../_shared/core/context-budget.md
Lessons learned: ../_shared/core/lessons-learned.md (matching prior failure or requested retrospective)
Observability handoff: ../oma-observability/SKILL.md §Integrations — propagators/baggage, span conventions, log correlation, PII redaction
Implement server APIs, authentication, and application data access. Schema modeling and query tuning use oma-db.
---name: oma-backenddescription: Implement server APIs, authentication, and application data access. Schema modeling and query tuning use…---# .agents/skills/oma-backend/SKILL.mdFAQ
पब्लिशर से .agents/skills/oma-backend/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/first-fluke/oh-my-agent पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।