- Home
- Skills
- Data & Databases
- Database Blueprint Architect — Design Reliable Scalable
Works with the AI Agents you already use
Database Blueprint Architect — Design Reliable Scalable
Translate workload requirements into data models, constraints, access patterns, reliability, migration and validation plans.
$9.99
Database Blueprint Architect — Design Reliable Scalable
Example session with this skill installed
Illustrative scenario: Design a conceptual database blueprint for a small multitenant appointment service. A tenant owns customers and appointments. A provider must not have overlapping confirmed appointments. We need lookup by provider/date and customer history. No engine, volume, latency or recovery target exists. Do not execute SQL or invent platform features.
- Read your context and instructions
- Compiled the database blueprint architect
Database blueprint — illustrative conceptual design
Authority: appointment service owns scheduling truth; any cache or search index is a derived view unless explicitly designed otherwise. Confirm tenant boundaries and authorization model.
Entities: Tenant; Customer scoped to tenant; Provider scoped to tenant; Appointment with tenant, customer, provider, start/end, status and version or equivalent concurrency control. Exact types and key strategy depend on chosen engine and requirements.
Invariants: customer/provider and appointment belong to the same tenant; end is after start; confirmed provider appointments do not overlap; valid status transitions are explicit. Enforce through suitable transactional controls and supported constraints after platform verification, not a read-then-write check vulnerable to races.
Access patterns: provider/day schedule; customer appointment history; appointment by tenant and identifier. Candidate indexes follow these predicates, but benchmark and inspect plans before deciding physical design.
Tenant isolation: authorization must scope every relevant access and relationship. Tests should include cross-tenant identifiers and attempted unauthorized relationships; performance work must not weaken isolation.
Reliability: define availability, recovery objectives and retention; plan backups and actual restore rehearsals; use safe migrations with compatibility, validation and rollback/forward-fix gates. No provider durability claim made.
Validation scenarios: concurrent overlapping bookings, adjacent non-overlapping slots, cancellation/rebooking, timezone boundaries, tenant isolation, retry duplication and restore integrity.
Open decisions: engine, workload scale, time semantics, conflict policy, history/audit needs and recovery targets. Start with the simplest architecture that satisfies confirmed requirements.
Execution notes: no database chosen, schema deployed, query benchmarked or migration run.
Connects securely to your tools. The creator never sees your data.
About this skill
Database Blueprint Architect helps teams design or review transactional, analytical and hybrid data systems from business truth and workload evidence. It identifies entities, invariants, ownership, access patterns, transactions, consistency, growth and recovery needs before choosing storage or optimization.
The skill examines relational and other database patterns, keys, constraints, indexes, tenant isolation, replication, caching, history, observability, lifecycle and cost. Search, caches and analytical stores are treated according to their actual authority rather than assumed to be the source of truth. It avoids fashionable platform choices and premature distributed complexity.
Use authorized requirements, schemas and sanitized examples to build blueprints and migration safety plans. Version-specific provider facts need authoritative verification; live access and changes require tools and authorization. It cannot promise infinite scale, zero downtime or zero data loss.
No architecture guarantees infinite scale, zero downtime or zero data loss. Reliability depends on workload, provider behavior, implementation and operations. Exact versions, features, limits, costs and performance require verification and representative tests.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
File Scopes
Use authorized requirements, metadata and sanitized files. Optional read/write files support blueprints and reports. Prefer read-only inspection and avoid production secrets or PII. No destructive SQL, deployment, access change or migration assumed; external actions need explicit authorization.