[Preset]: Add spec-kit-preset-db-standards

Abierto
#4,618 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
sql

Línea de trabajo

Start with the linked README and download URL, then inspect the preset.yml manifest and the listed constitution, spec, plan, and tasks templates. Run the documented specify preset add command and verify installation, template resolution, and documentation against the submission checklist; done means the preset is accepted with its required files and checks passing.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

preset-submission triage-can-wait validation-failed
Preset ID

spec-kit-preset-db-standards

Preset Name

DB Standards

Version

0.8.2

Description

A Spec Kit preset that bakes database conventions into the spec-driven workflow. ORM-agnostic — the rules are about SQL schema design, not a particular framework.

Author

Guilherme Makoto Sacoman Dakuzaku

Repository URL

https://github.com/gdakuzak/spec-kit-preset-db-standards

Download URL

https://github.com/gdakuzak/spec-kit-preset-db-standards/archive/refs/tags/v0.8.2.zip

Documentation URL

https://github.com/gdakuzak/spec-kit-preset-db-standards/blob/main/README.md

License

MIT

Required Spec Kit Version

0.1.0

Required Extensions (optional)

=0.1.0

Templates Provided
  • constitution-template.md — adds Database + Data protection sections (engine, version, migration tool; security posture)
  • spec-template.md — adds Data Requirements section
  • plan-template.md — adds Database Design section (naming, data-model design, constraints & integrity, data protection, performance, query safety)
  • tasks-template.md — adds Schema Review Checklist
Commands Provided
  • speckit.constitution.md — requires confirming the target database (engine, version, migration tool) and the security posture (roles, RLS) before the constitution is drafted
Number of Scripts (optional)

No response

Tags

database, standards, data-modeling, performance

Key Features
  • Forces confirming the target database (engine, version, migration tool) before the constitution is drafted, and records it in a Database section
  • Adds a Data Requirements section to specs: entities, reads/writes, retention, consistency
  • Adds Database Design guidance to plans: naming conventions, OLTP/OLAP classification, normalization (3NF) vs. denormalization trade-offs, constraints & integrity, data protection (column classification, secrets, RLS, least-privilege), external identifier exposure, SQL portability (ANSI-first), query safety (SQL injection), indexing plan, N+1/query-volume plan
  • Adds a Schema Review Checklist to tasks, run before merging any migration
  • Ships engine-specific reference files (Oracle, MySQL, SQL Server, DynamoDB, MongoDB) — read on demand from the plan, not bloating every project's plan with guidance for engines it doesn't use
  • ORM-agnostic; all overrides use append, so it stacks cleanly with other presets
Testing Checklist
  • Preset installs successfully via specify preset add
  • Template resolution works correctly after installation
  • Documentation is complete and accurate
  • Tested on at least one real project
Submission Requirements
  • Valid preset.yml manifest included
  • Linked README (Documentation URL) explains how to use this preset and includes a valid specify preset add ... command (preferably specify preset add --from <download-url> using the exact download URL)
  • LICENSE file included
  • GitHub release created with version tag
  • Preset ID follows naming conventions (lowercase-with-hyphens)
Lenguaje dominante
Python
Estrellas
138k
Forks
12.4k
Merge medio
2 d 15 h
PR fusionados (30 d)
141

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/spec-kit

Todos los issues de github/spec-kit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.