Workbook

From a one-paragraph idea to a specification and a working Laravel application, step by step.

The projects list — where every idea starts, and how to read a project card.

How to write an idea prompt that produces good boards, and what every field on the form controls.

The five discovery boards, how readiness works, and how reacting and refining moves a project forward.

Reading specification versions, the critic's score, and downloading the document in every format.

How to read the screen map diagram — screens, flows, and roles of your future application.

The code generation workspace — tabs, explicit saving, versions, and switching stacks.

Editing the entity diagram — entities, attributes, relationships, and the canvas tools.

The derived database schema — regenerating from entities, custom tables, and SQL export.

Eloquent models and their relations — generating them from entities and fine-tuning by hand.

Where each field appears in the generated app — list, detail page, form or hidden — with defaults, picklists, the row order and the CRUD-level settings.

Generating the codebase — options and presets, browsing files, and downloading the archive.

Where questions asked anywhere on the project are collected, threaded, and answered.

Deploying the generated application to your own server over SSH, step by step.

Publishing selected project artifacts to the public Showcase, and controlling exactly what is visible.

The extended user journeys document — personas, main, alternate and error paths, and what the journeys do not cover yet.

The plain-language guide to your future application — what it is, who uses it, how each role gets a task done, and what the domain words mean.

Exploring published community projects — their prompts, specifications, diagrams and code — and what you can do with an entry.

The locked specification as one navigable graph — roles, journeys, requirements, screens, tables and generated tests, linked, reviewable and exportable as a backlog.

What an entity model is, how Erlyc derives one from a plain-language idea, and how it becomes a database schema and working code.

The specification-first approach — why agreeing on what to build before building it beats iterating on a prototype, and how Erlyc practices it.

A practical guide to producing a complete application specification — what it must contain, and how AI drafting with human review gets you there.

Erlyc is a model-driven engineering system. What that means, why the approach stalled for twenty-five years, what changed, and the new problem that change introduces.

One transition table per status attribute — the states a record can hold, who may move it between them, and what the generated application enforces once you confirm.