upjack-app-builder

Upjack App Builder

Generate complete, spec-compliant NimbleBrain Upjack apps from a plain English description. The user says "create me a todo app" and you produce every file needed for a working Upjack app.

Quick Start

User says: "Create me a todo app"

You produce:

todo/
├── manifest.json
├── README.md
├── schemas/
│   ├── task.schema.json
│   ├── project.schema.json
│   └── label.schema.json
├── skills/
│   └── task-management/
│       └── SKILL.md
├── context.md
├── seed/
│   └── sample-tasks.json
└── server.py

References

Read these before generating. They are the source of truth. All paths are relative to the Upjack repo root.

• Upjack spec: docs/SPEC.md
• Entity model: docs/ENTITY_MODEL.md
• Manifest spec: docs/UPJACK_MANIFEST.md
• Manifest schema: schemas/v1/upjack-manifest.schema.json
• Entity base schema: schemas/v1/upjack-entity.schema.json
• CRM example: examples/crm/
• Research example: examples/research-assistant/
• Library source: lib/src/upjack/

Process

Phase 1: Understand the Request

Extract from the user's description:

1. App domain: What problem space? (productivity, finance, content, operations, etc.)
2. Core entities: What things does the user manage? (tasks, projects, invoices, articles)
3. Behaviors: What should the agent do automatically? (prioritize, categorize, alert, summarize)
4. Relationships: How do entities connect? (tasks belong to projects, invoices have line items)
5. Target location: Where to create files. Default: examples/{app-name}/

If the request is ambiguous, ask ONE round of clarifying questions. Keep it tight — propose a default and ask if they want changes:

I'll build a todo app with these entities:
- task (the core item — title, description, priority, due date)
- project (groups tasks)
- label (categorization tags)

One skill: task-management (prioritization, overdue detection, daily planning).
Sound right, or should I adjust?