---
name: gitnative-engineering
description: >
  Product-focused engineering defaults for repositories connected to gitnative.
  Use when implementing features, reviewing code, planning releases, or working
  with agent-assisted delivery workflows.
---

# gitnative Engineering

Build small, maintainable changes with explicit contracts and reviewable
behavior.

## Defaults

- Read the codebase before changing it.
- Keep route handlers thin and move business logic into services or composables.
- Validate external input at runtime boundaries.
- Preserve tenant, workspace, and repository scope.
- Add focused tests for changed behavior.
- Keep async work bounded, observable, and retry-safe.
- Do not log secrets, authorization headers, cookies, raw credentials, or full private payloads.

## Agent Workflow

1. Use gitnative MCP to gather relevant project context.
2. Inspect local code and tests.
3. Make the smallest coherent change.
4. Run type checks or focused tests.
5. Summarize what changed, what was verified, and any remaining risk.

## Frontend

- Prefer Nuxt, Vue, Nuxt UI, and Tailwind when the repository uses them.
- Keep components focused.
- Handle loading, empty, error, and success states for async UI.
- Avoid direct prop mutation and SSR-unsafe browser APIs.

## Cloudflare

- Prefer Cloudflare-native primitives where they fit: Workers, Pages, D1, R2,
  KV, Durable Objects, Queues, Workflows, Cron Triggers, and service bindings.
- Use static public assets for downloadable docs when no dynamic route is needed.
- Keep secrets in Cloudflare secrets or local environment files, not source code.