Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/Backend Models Standards
Define database models with clear naming, appropriate data types, constraints, relationships, and validation at multiple layers.
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
and 7 more in the full report
9 fixed12 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am creating a simple `Tag` ORM model for articles, containing `id` and `name`. Since tags are static metadata, we don't need audit timestamps on this table. Write the SQLAlchemy model class for `Tag`.
| Checked | Without skill | With skill |
|---|---|---|
| The model defines `created_at` and `updated_at` columns. | Missed | Passed |
The instructions your model reads when the skill loads.
Core Rule: Models define data structure and integrity. Keep them focused on data representation, not business logic.
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle backend models.
Models: Singular, PascalCase (User, OrderItem, PaymentMethod)
Tables: Plural, snake_case (users, order_items, payment_methods)
Relationships: Descriptive and clear
user.orders (one-to-many)order.items (one-to-many)product.categories (many-to-many)Avoid generic names: data, info, record, entity
Timestamps on every model:
created_at = Column(DateTime, nullable=False, default=datetime.utcnow)
updated_at = Column(DateTime, nullable=False, default=datetime.utcnow, onupdate=datetime.utcnow)
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.