Skip to content
cccskills
FreePublished on GitHub

dygo-database-engineering

Develop or review dygo PostgreSQL connectivity, schema planning, additive migration, prune, metadata persistence, Records, transactions, and schema snapshots. Use for framework database behavior and high-risk data lifecycle changes.

The English summary is being prepared. Showing the original description.

Works withPostgreSQL
See how to install

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

dygo Database Engineering

Make database changes reviewable, transactional, and safe for business data.

Start

Read docs/database.md, docs/patches.md, and the relevant Record or metadata contract. Inspect the planner, executor, naming policy, and current schema tests before you edit behavior.

Rules

  • Keep dygo db migrate additive and safe.
  • Use explicit prune for metadata-orphaned tables, columns, indexes, and constraints.
  • Keep destructive targets concrete and visible in the plan.
  • Use metadata as source of truth for dygo-managed schema.
  • Preserve deterministic plans and schema snapshots.
  • Keep related state changes atomic when partial application would violate an invariant.
  • Use parameterized SQL. Do not interpolate business values or identifiers without approved quoting rules.
  • Respect transaction ownership and PostgreSQL locking behavior.
  • Make concurrent claims and uniqueness rules enforceable in the database when correctness depends on them.
  • Keep Core metadata persistence on the same framework contracts where practical.
  • Return actionable database errors without exposing credentials.

Check

Use focused planner and database tests. Verify both the intended schema result and meaningful data preservation. Development migrations require elevated execution because the database socket is outside the normal sandbox.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design, implement, or review dygo roles, Entity access metadata, Permissions, and permission-aware Business App behavior. Use when access to Records or business actions is central to the task.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Design, implement, or review dygo HTTP APIs and public App SDK contracts. Use for Record APIs, metadata and boot endpoints, query behavior, response envelopes, compatibility, and public Go interfaces.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Diagnose a dygo Business App that does not validate, boot, route, render, authorize, migrate, or execute background work correctly. Use for evidence-first investigation rather than feature implementation.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Build or extend a dygo Business App using the supported project layout, generators, metadata, SDK, and validation workflow. Use for general app work that is not primarily Entity modeling, access, hooks, Jobs, fixtures, or patches.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Review a dygo Business App for framework conventions, model quality, access control, SDK boundaries, observability, and safe lifecycle behavior. Use for App audits and pre-merge reviews, not ordinary implementation.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

Design, implement, or review the dygo framework CLI in Go with Cobra. Use for commands, flags, help, prompts, plans, output contracts, completion, and project-aware CLI behavior. Do not use for operating a deployed business through the reserved dygo-cli operator skill.

The English summary is being prepared. Showing the original description.

hapyco/dygo16Updated Oct 18, 2026

See all skills by hapyco

Report a problem with this skill