sima-end-to-end

Implement ad publishing, viewing, and editing workflows with reusable data modeling patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RosenGray/sima --skill sima-end-to-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sima-end-to-end
Source: https://github.com/RosenGray/sima/tree/main/.cursor/skills/sima-end-to-end
Command: npx skills add https://github.com/RosenGray/sima --skill sima-end-to-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a framework-agnostic end-to-end guide for implementing ad publishing, viewing, and editing workflows.

Core Features & Use Cases

  • Unified publishing, viewing, and editing flows across sections (vehicles, pets, marketplace, services).
  • Reusable data modeling patterns (data layer with models, repositories, and validation schemas) that scale with categories.
  • Architectural clarity with diagrams and guidance to implement across new sections quickly.

Quick Start

Create a new skill directory for your section and begin by adding a SKILL.md frontmatter plus the end-to-end guidance. Follow the publishing, viewing, and editing flows to wire up to your repository and UI components.

Frequently Asked Questions about sima-end-to-end

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build end-to-end ad publishing workflows across different sections?

End-to-end ad publishing workflows are built using a framework-agnostic guide that codifies modular data layers, API routing, and UI integration for consistent publishing, viewing, and editing across sections.

What is the best way to structure data models for marketplace and services sections?

Structuring data models for marketplace and services sections is best handled by reusable patterns using repositories and validation schemas, allowing scalable architecture with optional parent and child relationships.

How does the repository pattern work with Zod schema validation for ad viewing?

The repository pattern works with Zod schema validation by separating data access logic from validation rules, ensuring that ad viewing and editing operations process structured data consistently across categories.

Can I use this end-to-end guide to add new ad categories like vehicles and pets quickly?

You can use this guide to add new ad categories like vehicles and pets quickly because it provides architectural clarity with diagrams and reusable patterns to wire up new sections without altering existing flows.

Do I need a specific framework to implement Mongoose data modeling for ads?

You do not need a specific framework to implement Mongoose data modeling for ads, as the guide is framework-agnostic and focuses on reusable data layer design applicable across various platforms.

When should I use optional parent and child relationships in ad data modeling?

Optional parent and child relationships in ad data modeling should be used when sections require hierarchical categorization, allowing flexible data structures that scale across vehicles, pets, marketplace, or services.