Architecture & CodeRoutes, structure, reusable code and resilience.
INCLUDED Storage, query, and generated names stay under one explicit contractREAL PRODUCT
GENESIS PRODUCT VIEWFloot Database Naming & CamelCase Mapping Guard
15package files
63automated test cases
0runtime dependencies
Lowercase snake_case checks, camelCase and PascalCase expectations, digit-adjacent overrides, quoted-name warnings, collision detection, and immutable evidence remain separate from migrations, SQL, and runtime proof. This is the real published Genesis interface—not a stock image.
TECHNICAL SCOPESee exactly where this product applies.Only the categories declared for this product are shown.
UtilitiesSupporting prompts, helpers, checklists and operational tools.
INCLUDEDWHAT YOU GETProduct-specific capabilities
01Audits no more than 200 table, column, and enum contracts using identifier-only metadata without row values or credentials.
02Validates portable lowercase snake_case PostgreSQL names and computes the corresponding camelCase query name.
03Computes optional PascalCase generated type expectations for table and enum comparison.
04Detects the underscore-before-digit case and requires an exact query-name-to-storage-name override.
05Reports quoted-identifier risk, duplicate identities, mismatches, unnecessary overrides, and orphan overrides with stable severity.
06Returns frozen valid or invalid evidence while performing no database, SQL, migration, schema generation, file, network, or configuration operation.
FOLLOW THE DIRECTIONSUse the product in order
01Declare identifier metadataList reviewed storage, query, and generated names without connection strings, values, credentials, or private comments.
02Audit and repair the sourceStop on errors, add exact digit-adjacent overrides where required, and repair migrations or generator inputs instead of hand-editing generated output.
03Verify the installed stackRegenerate schema helpers, run typecheck, and exercise representative queries against an isolated database using the installed Floot and Kysely versions.
TIPFollow the included START HERE and installation directions in order. Do not skip the test, verification, or rollback steps.
FLOOT TIPIf a completed change is not appearing on the published site, ask Floot to surface the Publish/Update action, process the update, then reload and verify the live result.
DISCLAIMEREvery website can differ by content, theme, framework, plugins, APIs, data, hosting, and prior customizations. This product may not detect or resolve every project-specific issue. Additional manual review, testing, access, or repairs may be required. Always complete a full independent audit and verify the result before publishing or relying on it.
FREE FLOOT DATABASE NAMING CODE · VERIFIED
Genesis Code Store · GCD-FLOOT-291
Floot Database Naming & CamelCase Mapping Guard
Audit PostgreSQL snake_case, Kysely camelCase, generated PascalCase types, quoted-name risk, and digit-adjacent overrides before identifiers typecheck but fail at runtime.
An original zero-dependency metadata auditor for Floot and Kysely database naming contracts. It validates bounded table, column, and enum identifiers; computes expected query and generated type names; detects duplicate storage or query identities; reports quoted-name risk; and requires exact query-name-to-storage-name overrides when an underscore immediately before a digit cannot be recovered by reverse camel-case mapping.
Simply put:
Genesis checks the site, shows what looks wrong, and helps you understand what needs attention.
AVAILABLE NOWFree
Free ZIP download Verified ZIP · 15 files · JavaScript + TypeScript declarations + 63 tests + README + START-HERE
Free Product LicenseSee included license
Free products remain subject to the written license included with the package. Free does not mean public-domain or unrestricted resale. Domain limits count websites, not individual page URLs.
Read license termsWhat it helps you do
- Explicit storage, query-layer, and generated-type name comparison
- Exact override requirement for underscore-before-digit round-trip gaps
- Quoted-identifier, duplicate, mismatch, and orphan-override evidence
TESTED FREE CODEFloot database name mapping evidence without touching the database.
What this specific product actually does
Every Genesis listing has its own capabilities, workflow, automation status, limits, and proof standard—without generic promises copied from another product.
CAPABILITIES
Inside Floot Database Naming & CamelCase Mapping Guard
- 01Audits no more than 200 table, column, and enum contracts using identifier-only metadata without row values or credentials.
- 02Validates portable lowercase snake_case PostgreSQL names and computes the corresponding camelCase query name.
- 03Computes optional PascalCase generated type expectations for table and enum comparison.
- 04Detects the underscore-before-digit case and requires an exact query-name-to-storage-name override.
- 05Reports quoted-identifier risk, duplicate identities, mismatches, unnecessary overrides, and orphan overrides with stable severity.
- 06Returns frozen valid or invalid evidence while performing no database, SQL, migration, schema generation, file, network, or configuration operation.
TESTED FREE CODE
Floot database name mapping evidence without touching the database.
The guard audits supplied identifier metadata only; the host owns migrations, generation, configuration, database integration tests, deployment, monitoring, and rollback.
63 test casesDigit overridesNo dependencies
AUTOMATIC REPAIRNot enabled
This product does not modify a customer website.
PRODUCT FIT
Who this is built for
- 01Floot projects using Kysely CamelCasePlugin with generated schema helpers
- 02Teams reviewing migrations before query-layer names reach production
- 03CI checks that compare database, query, and generated type naming without database access
DELIVERY
How you receive it
Listing Code
GCD-FLOOT-291
Format
Verified ZIP · 15 files · JavaScript + TypeScript declarations + 63 tests + README + START-HERE
Compatibility
All Platforms, Floot
Cost
Free
This listing is a downloadable Genesis code package. The ZIP includes reusable code and START-HERE directions.
HOW TO USE IT
Three steps for this product
- 01
Declare identifier metadata
List reviewed storage, query, and generated names without connection strings, values, credentials, or private comments.
- 02
Audit and repair the source
Stop on errors, add exact digit-adjacent overrides where required, and repair migrations or generator inputs instead of hand-editing generated output.
- 03
Verify the installed stack
Regenerate schema helpers, run typecheck, and exercise representative queries against an isolated database using the installed Floot and Kysely versions.
GENESIS CODE DOCTOR™
Before & After Repair Report
Floot Database Naming & CamelCase Mapping Guard · GCD-FLOOT-291
Evidence-backed output
Report format preview. Scores and status values populate only from measurements produced by an actual run. Genesis does not invent improvements.
CategoryBeforeAfterStatus
ArchitectureMeasured at runVerified after repairAwaiting run
Functional HealthMeasured at runVerified after repairAwaiting run
What Genesis Code Doctor fixed
- Only verified changes appear here.
- Each repair can show affected files, routes, checks, or rules.
- Regression checks are recorded separately from the repair itself.
Still needs attention
- Unresolved, blocked, unavailable, or not-tested items remain visible.
- Evidence links can explain why an item passed, failed, or needs review.
- Follow-up verification can be run after implementation.
Know the fit, evidence, and handoff before a repair is used.
These controls turn a code product into a traceable repair workflow. They do not claim compatibility or success that has not been verified.
Declared support is available
Declared platforms: All Platforms, Floot
Exact compatibility still depends on the customer's framework version, dependencies, hosting, custom code, and current site state.
Ready for project-specific pre-check
Lifecycle protection is part of the product standard.
- Compatibility is reviewed before release.
- Regression and rollback requirements stay explicit.
- Follow-up verification can be run after implementation.
Genesis keeps the recommendation tied to evidence.
- Confirm the observed problem.
- Check product fit and safety boundary.
- Apply only the authorized repair scope.
- Re-run equivalent checks before calling it fixed.
Generate a clean technical handoff in one click.
The handoff includes product identity, declared compatibility, delivery method, capabilities, safety boundary, and the verification sequence.
IMPORTANT BOUNDARY
What this item does not claim
This guard audits caller-supplied identifier metadata only. It does not connect to PostgreSQL, inspect migrations, query a schema, generate or edit schema helpers, configure Kysely or Floot, execute SQL, prove a runtime mapping, or replace version-specific integration tests.
DOWNLOADABLE CODE POLICY
Simple delivery when verified code is released
Free code uses Free Download. Paid code uses Add to Cart. Every released package includes a verified ZIP, README, license notice, and START-HERE directions.
Copyright © Connect Point ISP LLC. Genesis Code Doctor™. All rights reserved. Purchase or download does not transfer ownership. Except where a product expressly provides a different written license, Genesis packages may not be resold, redistributed, sublicensed, repackaged for sale, or published as a competing download.
Free Product License: See included license. Free products remain subject to the written license included with the package. Free does not mean public-domain or unrestricted resale. A domain means a distinct production website host; pages and routes under the same domain do not consume separate activations. Agency use beyond the included limit requires an expanded agency license.