tech-postgres
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when writing SQL, ORM queries, or database migrations for PostgreSQL.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When interacting with a Postgres database, prioritize safety, efficiency, and data integrity:
- Distinctive: line 13
Migrations: Always modify schemas using version-controlled migrations.
- Distinctive: line 15
Indexes: Add indexes to foreign keys and frequently filtered/sorted columns, but avoid over-indexing to prevent slow writes.
- Very specific: line 16
N+1 Queries: When fetching relationships, use JOINs or data loaders instead of firing a query inside a loop.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PostgreSQL Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When interacting with a Postgres database, prioritize safety, efficiency, and data integrity:
- Migrations: Always modify schemas using version-controlled migrations. Never alter tables manually.
- Backwards Compatibility: Migrations must be backwards compatible (e.g., add new columns as nullable first) to support zero-downtime deployments.
- Indexes: Add indexes to foreign keys and frequently filtered/sorted columns, but avoid over-indexing to prevent slow writes.
- N+1 Queries: When fetching relationships, use
JOINs or data loaders instead of firing a query inside a loop. - Transactions: Wrap multi-step data mutations in a transaction. Ensure rollbacks are handled on failure.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.