ebuilder-sql-safe-patterns

name	ebuilder-sql-safe-patterns
description	Hub for eBuilder SQL generation playbooks. Routes to specialized skills: ebuilder-eb-sql-symbols (for $EB_* symbols and portability), ebuilder-sql-query (query router hub with focused sub-skills), ebuilder-sql-mutation (for mutation envelope design), and ebuilder-sql-step (for mutation step internals). USE FOR: directing to the correct SQL generation context.

eBuilder SQL Generation Hub

Overview

This skill is a routing hub that directs SQL work to the correct focused playbook.

Core Routing

• ebuilder-eb-sql-symbols

  • Use for $EB_* symbols, portability, and engine-aware SQL patterns.

• ebuilder-sql-query

  • Use as query router hub for query-* work.
  • Sub-skills:
    • ebuilder-sql-query-foundation
    • ebuilder-sql-query-input-validation
    • ebuilder-sql-query-result-shaping
    • ebuilder-sql-query-pre-pipeline
    • ebuilder-sql-query-post-pipeline
    • ebuilder-sql-query-security-error-handling

• ebuilder-sql-mutation

  • Use for mutation envelope design.

• ebuilder-sql-step

  • Use for step internals inside mutation steps[].

Quick Intent Mapping

• Need portable symbols or cross-DB syntax: ebuilder-eb-sql-symbols.
• Need read-only query work: ebuilder-sql-query (then route to a query sub-skill).
• Need mutation root transaction/response design: ebuilder-sql-mutation.
• Need detailed mutation step chaining/save/check behavior: ebuilder-sql-step.

Universal Safety Checklist

1. File is under configs/sql.*.yml.
2. Root keys are only query or mutation.
3. Query keys match ^query-[a-zA-Z0-9-]+$.
4. Mutation keys match ^mutation-[a-zA-Z0-9-]+$.
5. User input is parameter-bound (no unsafe interpolation).
6. Datasource keys exist in configs/app.yml.
7. Authorization references are valid for app security policy.
8. Deprecated keys are not used (param, op, value, throw, silentThrow).