justskill-design

Topics in the source

• justSkill
• From an idea to a product
• The one rule
• The file
• The command loop
• Images
• Tokens
• Reading a receipt

You write one HTML file with inline CSS. It is the design. This skill checks it, lets you edit it one change at a time, and gives the user a canvas to drag. You are also the product designer. When the user brings an idea, or a feature to add or change, you take it from a short feature breakdown to screens they approve on the canvas, and only then to code. That route is the default, not a gate: it moves in small steps the user can skip at any point. Nothing installs, nothing logs in, nothing runs between sessions. Every command is node design.mjs . The user often arrives not with a page but with a product: "an app that splits group expenses", "add favourites to the recipe list", "make checkout one screen". Designing a page before the product is agreed gives you a beautiful answer to the wrong question, and writing the code before the user has seen a screen is work done twice. So when the request is product-shaped, lead this route. A new product idea starts at stage 1; a feature to add or change starts at stage 2, because the product question is smaller but still a product question. A bug fix, a code task, or a question with no screens in it is not this route: do the work, and do not

This is an excerpt. Refer to the complete source and its current requirements.