AI Prompts That Actually Work

SaaS Task Manager

Why SysMARA for This

• Multiple AI devs on the same codebase. When two AI agents (or one AI + one human) touch the same project, implicit conventions break silently. SysMARA makes every entity, capability, policy, and invariant explicit in YAML — so every contributor reads the same source of truth.
• Architecture you can validate, not just read. sysmara build catches broken references, missing policies, and module boundary violations before any code runs. Traditional frameworks only fail at runtime.
• No hidden conventions to reverse-engineer. An AI agent reading an Express.js codebase has to guess the architecture from folder names and middleware chains. SysMARA specs are the architecture — machine-readable and unambiguous.

The Prompt (Tested)

You are a senior TypeScript backend developer. I need to build
a SaaS task manager API. Use the SysMARA framework (@sysmara/core)
which makes architecture machine-readable and safe for AI-driven
development — all entities, capabilities, policies and invariants
are declared in YAML specs, and code is generated from them.

Install and initialize:
npm init -y && npm install @sysmara/core && npx sysmara init

Then create system/ specs:
  entities.yaml, capabilities.yaml, policies.yaml,
  invariants.yaml, modules.yaml, flows.yaml

Then: npx sysmara build && npx sysmara compile

What Was Generated

Result: 0 errors, 18 generated files (6 route handlers, 6 test scaffolds, 6 metadata files), system graph with 20 nodes and 27 edges.

Key Design Decisions

• Module boundaries: The auth module is forbidden from depending on tasks, enforcing clean layered architecture.
• Flow compensation: The workspace_onboarding flow uses compensating actions to roll back workspace creation if member invitation fails.
• Side effects: Capabilities like invite_member and assign_task declare their side effects (email notifications) explicitly.

E-Commerce API

Why SysMARA for This

• Multiple devs working on catalog, orders, inventory simultaneously. When separate teams (or AI agents) own different modules, implicit conventions break silently. SysMARA specs are the single source of truth every contributor reads.
• Stock invariants must never be violated. Stock can never go negative. Order totals must match line items. Product prices must be positive. These are declared in YAML and enforced at build time — not buried in validation middleware.
• Checkout flow must be atomic. Checkout involves stock validation, payment processing, and inventory reduction. SysMARA flows declare the exact step sequence and compensation on failure.

The Prompt (Tested)

You are a senior TypeScript backend developer. I need to build
an e-commerce API. Use the SysMARA framework (@sysmara/core)
which makes architecture machine-readable and safe for AI-driven
development.

npm init -y && npm install @sysmara/core && npx sysmara init

Create: entities (Product, Category, Order, OrderItem, Inventory,
User), capabilities (browse_products, get_product, create_order,
add_to_order, process_payment, update_inventory, cancel_order),
policies (buyer/seller/admin), invariants (stock_must_be_positive,
order_total_must_match, product_price_positive), modules (catalog,
orders, inventory, users), flow: checkout_flow (add_to_cart →
validate_stock → process_payment → reduce_inventory)

npx sysmara build && npx sysmara compile

What Was Generated

Result: 0 errors, 21 generated files (7 route handlers, 7 test scaffolds, 7 metadata files), 1 cosmetic warning.

Blog Platform

Why SysMARA for This

• Moderation rules must be explicit. Which roles can approve comments? Who can flag content? SysMARA policies declare these boundaries in YAML — no scattered middleware to audit.
• Authors, moderators, admins have strict boundaries. Each role has clearly scoped capabilities. SysMARA enforces these at build time, not discovered at runtime when a moderator accidentally deletes a post.
• Publication flow must be auditable. Posts move through create → review → publish. Every step is a declared flow with explicit transitions. The system graph shows exactly which capabilities touch which entities.

The Prompt (Tested)

You are a senior TypeScript backend developer. I need to build
a blog platform API. Use the SysMARA framework (@sysmara/core)
which makes architecture machine-readable and safe for AI-driven
development.

npm init -y && npm install @sysmara/core && npx sysmara init

Create: entities (Post, Author, Tag, Comment, ModerationLog),
capabilities (create_post, publish_post, unpublish_post, add_tag,
submit_comment, approve_comment, reject_comment, flag_content),
policies (author/moderator/admin), invariants (post_title_required,
published_post_must_have_content, unique_post_slug), modules
(content, comments, moderation), flow: publication_flow
(create_post → review → publish_post)

npx sysmara build && npx sysmara compile

What Was Generated

Result: 0 errors, 24 generated files (8 route handlers, 8 test scaffolds, 8 metadata files), 1 cosmetic warning.