Antigravity-awesome-skills pydantic-models-py
Create Pydantic models following the multi-model pattern for clean API contracts.
install
source · Clone the upstream repo
git clone https://github.com/sickn33/antigravity-awesome-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/pydantic-models-py" ~/.claude/skills/sickn33-antigravity-awesome-skills-pydantic-models-py-1b837a && rm -rf "$T"
manifest:
plugins/antigravity-awesome-skills/skills/pydantic-models-py/SKILL.mdsource content
Pydantic Models
Create Pydantic models following the multi-model pattern for clean API contracts.
Quick Start
Copy the template from assets/template.py and replace placeholders:
→ PascalCase name (e.g.,{{ResourceName}}
)Project
→ snake_case name (e.g.,{{resource_name}}
)project
Multi-Model Pattern
| Model | Purpose |
|---|---|
| Common fields shared across models |
| Request body for creation (required fields) |
| Request body for updates (all optional) |
| API response with all fields |
| Database document with |
camelCase Aliases
class MyModel(BaseModel): workspace_id: str = Field(..., alias="workspaceId") created_at: datetime = Field(..., alias="createdAt") class Config: populate_by_name = True # Accept both snake_case and camelCase
Optional Update Fields
class MyUpdate(BaseModel): """All fields optional for PATCH requests.""" name: Optional[str] = Field(None, min_length=1) description: Optional[str] = None
Database Document
class MyInDB(MyResponse): """Adds doc_type for Cosmos DB queries.""" doc_type: str = "my_resource"
Integration Steps
- Create models in
src/backend/app/models/ - Export from
src/backend/app/models/__init__.py - Add corresponding TypeScript types
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.