원클릭으로 Manus에서 모든 스킬 실행

bosskuai-database-engineering

스타0

포크0

업데이트2026년 4월 26일 17:35

Use this for SQL and NoSQL database design across MariaDB, MySQL, PostgreSQL, SQLite, MongoDB, indexing, transactions, migrations, constraints, query plans, and data correctness.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

fikrimastor

fikrimastor/Bossku-AI

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

BosskuAI Database Engineering

Use this skill when schema, query behavior, indexes, migrations, data consistency, or database choice affects the outcome.

Database coverage

MariaDB / MySQL: InnoDB constraints, indexes, generated columns, JSON tradeoffs, online migration risk, replication-aware changes.
PostgreSQL: constraints, partial indexes, JSONB, GIN/GiST, CTEs, advisory locks, EXPLAIN ANALYZE.
SQLite: local/dev/test constraints, WAL mode, type affinity, concurrency limits, migration compatibility.
MongoDB: document shape, compound indexes, aggregation pipelines, schema validation, write concern, and bounded document growth.

Review checklist

Data model matches the business invariant, not only the current UI.
Constraints exist in the database for rules that must never be violated.
Indexes match real WHERE, JOIN, ORDER BY, and uniqueness paths.
Migrations are reversible or have a safe forward-only rollback plan.
High-volume changes are chunked and safe for production traffic.
Query plans are checked before claiming a query is fast.
Soft deletes, tenancy, status transitions, and audit trails are modeled explicitly.

Guardrails

Do not solve missing constraints only in application code.
Do not add indexes blindly; check selectivity and write cost.
Do not use MongoDB as a shortcut for unclear relational modeling.
Do not assume MySQL, MariaDB, PostgreSQL, and SQLite support the same DDL.

Output format

Database engine: [engine/version if known]
Invariant to protect: [rule]
Schema/query findings:
  P0/P1/P2 — [issue] — [fix]
Migration plan: [safe steps]
Index plan: [index + reason]
Verification: [EXPLAIN/tests/constraints checked]

References

../../references/playbooks/bosskuai-database-engineering-playbook.md
../../references/checklists/database-engineering-checklist.md
../../references/checklists/expert-cofounder-stack-checklist.md

이 저장소의 다른 Skills

같은 저장소

bosskuai-hyperframes

fikrimastor/Bossku-AI

Use this for Hyperframes video composition work, including HTML-based scene authoring, preview/render workflows, CLI commands, agent-friendly composition updates, and GSAP-assisted animation inside Hyperframes projects.

2026-05-080

bossku-ai

fikrimastor/Bossku-AI

Use when a Codex workspace needs BosskuAI routing, repo-local memory, skill selection, or quality gates without loading the full toolkit.

2026-05-080

bosskuai-cost-optimization

fikrimastor/Bossku-AI

Use this for cloud/server/API/model cost control, token budgets, queue sizing, storage costs, vendor spend, and unit economics.

2026-05-040

bosskuai-customer-success-support

fikrimastor/Bossku-AI

Use this for support SOPs, onboarding, ticket triage, customer success playbooks, retention, churn reduction, and feedback loops.

2026-05-040

bosskuai-eval-driven-agent-improvement

fikrimastor/Bossku-AI

Use this for agent eval design, routing tests, retrieval tests, LLM quality cases, regression harnesses, scorecards, and continuous agent improvement.

2026-05-040

bosskuai-malaysia-pdpa-privacy

fikrimastor/Bossku-AI

Use this for Malaysia PDPA-aware privacy review, data minimization, consent, retention, user rights, vendor processors, and privacy-safe SaaS operations.

2026-05-040

name	bosskuai-database-engineering
description	Use this for SQL and NoSQL database design across MariaDB, MySQL, PostgreSQL, SQLite, MongoDB, indexing, transactions, migrations, constraints, query plans, and data correctness.

BosskuAI Database Engineering

Use this skill when schema, query behavior, indexes, migrations, data consistency, or database choice affects the outcome.

Database coverage

MariaDB / MySQL: InnoDB constraints, indexes, generated columns, JSON tradeoffs, online migration risk, replication-aware changes.
PostgreSQL: constraints, partial indexes, JSONB, GIN/GiST, CTEs, advisory locks, EXPLAIN ANALYZE.
SQLite: local/dev/test constraints, WAL mode, type affinity, concurrency limits, migration compatibility.
MongoDB: document shape, compound indexes, aggregation pipelines, schema validation, write concern, and bounded document growth.

Review checklist

Data model matches the business invariant, not only the current UI.
Constraints exist in the database for rules that must never be violated.
Indexes match real WHERE, JOIN, ORDER BY, and uniqueness paths.
Migrations are reversible or have a safe forward-only rollback plan.
High-volume changes are chunked and safe for production traffic.
Query plans are checked before claiming a query is fast.
Soft deletes, tenancy, status transitions, and audit trails are modeled explicitly.

Guardrails

Do not solve missing constraints only in application code.
Do not add indexes blindly; check selectivity and write cost.
Do not use MongoDB as a shortcut for unclear relational modeling.
Do not assume MySQL, MariaDB, PostgreSQL, and SQLite support the same DDL.

Output format

Database engine: [engine/version if known]
Invariant to protect: [rule]
Schema/query findings:
  P0/P1/P2 — [issue] — [fix]
Migration plan: [safe steps]
Index plan: [index + reason]
Verification: [EXPLAIN/tests/constraints checked]

References

../../references/playbooks/bosskuai-database-engineering-playbook.md
../../references/checklists/database-engineering-checklist.md
../../references/checklists/expert-cofounder-stack-checklist.md