Claude Skills by hapyco

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.

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.

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.

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.

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.

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.

Improve or review ordinary dygo code changes for simplicity, focused scope, canonical ownership, clear boundaries, and verifiable behavior. Use for normal implementation and refactoring quality; use dygo-thermonuclear-review only for an explicitly severe audit.

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.

Write or update dygo instructions, reference documentation, task descriptions, CLI help, metadata examples, or architecture notes. Use when documentation quality and contract accuracy are central to the task.

Design or change dygo Entity metadata, Fields, Record Collections, links, naming, routes, indexes, and constraints. Use when a business data model or metadata contract is the main task.

Create or review dygo Fixtures and explicit Patches for reference data, setup Records, backfills, renames, and unsafe lifecycle transitions. Use when metadata sync alone cannot express the required data change.

Design or implement reusable capability in the dygo framework, Core App, Studio App, runtime, or public SDK. Use when changing dygo itself rather than building a Business App.

Write, refactor, or review Go code in the dygo framework or App SDK using dygo package boundaries and runtime conventions. Use for substantial Go implementation that is not primarily Cobra CLI work.

Build or review dygo durable Jobs, Job Executions, queues, workers, retries, idempotency, and Schedules. Use for background or recurring business work.

Develop or review dygo metadata loading, YAML decoding, JSON Schemas, validation, naming, Field types, registries, routes, and persisted metadata contracts. Use for framework-level metadata behavior rather than authoring one Business App Entity.

Add or review dygo Logs, Activity, Audit Logs, health checks, diagnostics, metrics, traces, and operator-visible failure states. Use when runtime behavior must become inspectable or diagnosable.

Define dygo App Pages and metadata-driven Studio experiences for Business Apps. Use when an App needs a Page, navigation entry, renderer choice, or Studio presentation beyond default Entity routes.

Implement or review dygo Record lifecycle Hooks in Business Apps or the Hook runtime. Use for validation, transactional Record reactions, and lifecycle side effects tied to Record changes.

Prepare, validate, package, or review a dygo framework release and its upgrade path. Use for versioning, tags, binaries, Studio and Core bundling, installers, archives, checksums, and release smoke checks.

Design, implement, or review security-sensitive dygo behavior across auth, sessions, Permissions, secrets, APIs, database writes, files, Jobs, and Studio. Use when security boundaries are a primary concern.

Create, extend, or review dygo Studio design tokens, Tailwind v4 styles, primitives, components, and interaction patterns. Use when visual consistency or a reusable Studio UI pattern is the main task.

Implement or review dygo Studio behavior in Vue, TypeScript, Pinia, TanStack Query, Vue Router, Reka UI, and framework renderers. Use for Studio application logic, navigation, state, API integration, and shared components.

Select, write, or review proportionate tests and verification for dygo Go packages, PostgreSQL behavior, metadata, CLI contracts, Studio, integrations, and releases. Use when test scope or confidence strategy is the main decision.

Run an explicitly requested, unusually strict dygo maintainability audit that seeks structural simplification, removes accidental complexity, and challenges weak abstractions without changing behavior.