sqlalchemy-postgres

cfircoo/claude-code-toolkit · updated May 26, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/cfircoo/claude-code-toolkit --skill sqlalchemy-postgres
0 commentsdiscussion
summary

<essential_principles>

skill.md

<essential_principles>

SQLAlchemy 2.0 + Pydantic + PostgreSQL Best Practices

This skill provides expert guidance for building production-ready database layers.

Stack

  • SQLAlchemy 2.0 with async support (asyncpg driver)
  • Pydantic v2 for validation and serialization
  • Alembic for migrations
  • PostgreSQL only

Core Principles

1. Separation of Concerns

models/       # SQLAlchemy ORM models (database layer)
schemas/      # Pydantic schemas (API layer)
repositories/ # Data access patterns
services/     # Business logic

2. Type Safety First Always use SQLAlchemy 2.0 style with Mapped[] type annotations:

from sqlalchemy.orm import Mapped, mapped_column

class User(Base):
    __tablename__ = "users"
    id: Mapped[int] = mapped_column(primary_key=True)
    name: Mapped[str] = mapped_column(String(100))

3. Async by Default Use async engine and sessions for FastAPI:

from sqlalchemy.ext.asyncio import create_async_engine, AsyncSession
engine = create_async_engine("postgresql+asyncpg://...")

4. Pydantic-SQLAlchemy Bridge Keep models and schemas separate but mappable:

# Schema reads from ORM
class UserRead(BaseModel):
    model_config = ConfigDict(from_attributes=True)

5. Repository Pattern Abstract database operations for testability and clean code. </essential_principles>

  1. Setup database layer - Initialize SQLAlchemy + Pydantic + Alembic from scratch
  2. Define models - Create SQLAlchemy models with Pydantic schemas
  3. Create migration - Generate and manage Alembic migrations
  4. Query patterns - Async CRUD, joins, eager loading, optimization
  5. Full implementation - Complete database layer for a feature

Auto-detection triggers (use this skill when user mentions):

  • database, db, sqlalchemy, postgres, postgresql
  • model, migration, alembic
  • repository, crud, query
  • async session, connection pool

<reference_index>

Domain Knowledge

Reference Purpose
references/best-practices.md Production patterns, security, performance
references/patterns.md Repository, Unit of Work, common queries
references/async-patterns.md Async session management, FastAPI integration
</reference_index>

<workflows_index>

Workflow Purpose
workflows/setup-database.md Initialize complete database layer
workflows/define-models.md Create models + schemas + relationships
workflows/create-migration.md Alembic migration workflow
workflows/query-patterns.md CRUD operations and optimization
</workflows_index>

<quick_reference>

File Structure

src/
├── db/
│   ├── __init__.py
│   ├── base.py          # DeclarativeBase
│   ├── session.py       # Engine + async session factory
│   └── dependencies.py  # FastAPI dependency
├── models/
│   ├── __init__.py
│   └── user.py          # SQLAlchemy models
├── schemas/
│   ├── __init__.py
│   └── user.py          # Pydantic schemas
├── repositories/
│   ├── __init__.py
│   ├── base.py          # Generic repository
│   └── user.py          # User repository
└── alembic/
    ├── alembic.ini
    ├── env.py
    └── versions/

Essential Imports

# Models
from sqlalchemy import String, Integer, ForeignKey, DateTime
from sqlalchemy.orm import Mapped, mapped_column, relationship, DeclarativeBase

# Async
from sqlalchemy.ext.asyncio import create_async_engine, AsyncSession, async_sessionmaker

# Pydantic
from pydantic import BaseModel, ConfigDict, Field

Connection String

# PostgreSQL async
DATABASE_URL = "postgresql+asyncpg://user:pass@localhost:5432/dbname"

</quick_reference>

<success_criteria> Database layer is complete when:

  • Async engine and session factory configured
  • Base model with common fields (id, created_at, updated_at)
  • Models use Mapped[] type annotations
  • Pydantic schemas with from_attributes=True
  • Alembic configured for async
  • Repository pattern implemented
  • FastAPI dependency for session injection
  • Connection pooling configured for production </success_criteria>
how to use sqlalchemy-postgres

How to use sqlalchemy-postgres on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add sqlalchemy-postgres
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/cfircoo/claude-code-toolkit --skill sqlalchemy-postgres

The skills CLI fetches sqlalchemy-postgres from GitHub repository cfircoo/claude-code-toolkit and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/sqlalchemy-postgres

Reload or restart Cursor to activate sqlalchemy-postgres. Access the skill through slash commands (e.g., /sqlalchemy-postgres) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.654 reviews
  • Shikha Mishra· Dec 28, 2024

    Keeps context tight: sqlalchemy-postgres is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aarav Bhatia· Dec 20, 2024

    Registry listing for sqlalchemy-postgres matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kiara Ndlovu· Dec 20, 2024

    sqlalchemy-postgres has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Min Torres· Dec 12, 2024

    Useful defaults in sqlalchemy-postgres — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mia Farah· Nov 11, 2024

    Useful defaults in sqlalchemy-postgres — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • James Jackson· Nov 11, 2024

    sqlalchemy-postgres fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Benjamin Ndlovu· Nov 3, 2024

    Registry listing for sqlalchemy-postgres matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Desai· Oct 22, 2024

    sqlalchemy-postgres reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Mia Flores· Oct 2, 2024

    I recommend sqlalchemy-postgres for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • James Brown· Oct 2, 2024

    We added sqlalchemy-postgres from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 54

1 / 6