メニュー
Use this skill whenever company-specific jargon, acronyms, or domain terminology is needed to answer correctly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use whenever building a UI table, list view, or dashboard panel showing records with amounts, dates, or statuses (invoices, tickets, orders, tasks, leads, log entries, etc.) — in React/HTML/artifacts, TanStack Table column defs, or when writing/reviewing component code for one. Consult before rendering a "flat" table (raw columns, no aggregation, no visual encoding), even if the user just says "make a table" or "show this data" — a bare table is rarely the best answer once rows carry a magnitude, a due date, or a status. Also use when asked to "make this table nicer", "more like a dashboard", or to add KPIs/summary above a table.
Use this skill whenever the user wants to bootstrap, scaffold, or initialize a new full-stack app with a Vite + React + TanStack + shadcn/ui frontend and a FastAPI + Postgres backend. Triggers on requests like "create a new app", "set up a project", "scaffold a full-stack app", "init a new project", or anything involving starting a fresh React/FastAPI application from scratch.
Discover repos across the whole Azure DevOps org — not just the one you're sitting in — and figure out where a piece of functionality actually lives before assuming it doesn't exist locally. Generates ALL_REPOS.md, a map of every project/repo in the org, each repo's description, and whether it's already cloned locally (and where). Use this whenever the user asks about "other repos", "which repo has X", cross-repo/cross-service work, wants to find or clone a repo they don't have locally yet, or when you're stuck looking for code that isn't in the current repo and it might live elsewhere in the org. Trigger on things like "is there already a repo for this", "check across our other repos", "what repos do we have", "where's the shared X library", or "I don't think this exists yet, can you check devops".
Conventions for versioning a PostgreSQL schema as plain `.sql` files inside a `database/` folder in the repo, instead of an ORM migration framework. Use when creating/organising a `database/` folder, adding a new table/view/function/type, or deciding where a migration script goes. Triggers on things like "add a new table to database/", "where do table definitions live", "database folder structure", "schema layer", "migration script", ".prod file", ".init.sql".
PostgreSQL coding standards for Python projects using psycopg (no ORM). Use this skill whenever the user is writing or reviewing code that queries PostgreSQL with psycopg, creates SQL files, maps query results to Python objects, or asks how to structure database access code. Triggers on things like "add a database query", "write a SQL query", "create a repository", "fetch from postgres", "insert into the database", "update the DB", "parameterized query", "pydantic model from DB row", "sql file", "dynamic SQL", or any mention of psycopg, psycopg2, asyncpg, or SQLAlchemy where the user seems open to a different approach. Also use when the user asks about connection pooling, transactions, cursor factories, or how to organise database code.
Set up and work with a local PostgreSQL test database in Docker for integration/e2e tests. Use this skill whenever the user wants to add, configure, troubleshoot, or run queries against a local test Postgres instance — even if they don't say "postgres" explicitly. Triggers on things like "set up a test database", "add postgres fixtures", "init test DB", "local postgres for tests", "add a column", "create a table", "change the schema", "run a SQL query on my test DB", "reset the database", "database is out of sync", "test data", or anything involving the local test Postgres database. Also use this skill when the user asks how to inspect the test DB, seed rows, or apply a migration to the local environment.
| name | fabricks-glossary |
| plugin | fabricks-data |
| description | Use this skill whenever company-specific jargon, acronyms, or domain terminology is needed to answer correctly. |
| version | 1.0.0 |
This skill provides domain vocabulary, entity definitions, and architecture context for the company's data warehouse, built on Databricks using the Fabricks.Runtime framework. Most of this terminology originates from and is primarily used in the context of that data warehouse.
Load only the reference file(s) relevant to your current task:
| Topic | Reference file | Load when... |
|---|---|---|
| Acronyms & abbreviations | references/acronyms.md | An unknown abbreviation appears (SPT, BU, IVP, HEP, etc.) |
| Core business entities | references/entities.md | Working with articles, customers, sales agents, or inventory |
| Domain concepts | references/domain-concepts.md | Working with commissions, margin bonuses, campaigns, credit risk, or MDM |
| Naming conventions | references/conventions.md | Naming or interpreting tables, columns, schemas, or data layers |
| Fabricks framework | references/fabricks-framework.md | Working with steps, jobs, modes, CDC, or pipeline configuration |
dim_ dimensions · fact_ measures · ref_ lookups · scd1_/scd2_ history · merger_ consolidated · *_agg aggregated · *_hist snapshots__key hash key · __identity surrogate · __is_current SCD2 flag · __valid_from/to SCD2 range · _sk foreign surrogate · _pct percentagestaging (raw ingest) → raw (SCD applied) → transf/core/mdm/ml (gold) → semantic/bme (presentation) → distribution (export)core has surrogate keys (__identity); transf has business logic but no core tables; semantic uses UPPERCASE column names with spaces for Power BI