materializar-ideia

Transforms abstract ideas into running applications with justified stack choices and verified execution.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/GuilhermeBrancalhao/ENGINE-CODEX --skill materializar-ideia-guilhermebrancalhao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: materializar-ideia
Source: https://github.com/GuilhermeBrancalhao/ENGINE-CODEX/tree/main/motores/materializar-ideia
Command: npx skills add https://github.com/GuilhermeBrancalhao/ENGINE-CODEX --skill materializar-ideia-guilhermebrancalhao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Users often bring vague ideas ("I want an app that...") rather than specifications, and typical AI output is a skeleton full of TODOs that never actually runs. This Skill turns a raw concept into a working application by making and naming the undecided decisions, choosing the smallest adequate stack, and verifying the result actually executes. ## Core Features & Use Cases - Concept fixation: Defines who uses the product, the central action, and the hard constraint before writing code, asking everything at once only when truly undecidable. - Justified stack selection: Picks the minimal stack that satisfies the hard constraint (single-file HTML/JS, component framework, or backend with database), with a decision matrix in references/escolha-de-stack.md. - Inside-out construction: Builds model, use cases, boundary, persistence, then interface, so each layer tests the previous one. - Visual identity method: Derives palette, typography, and layout from the subject matter using references/identidade-visual.md, avoiding generic AI-generated aesthetics. - Verified delivery: Requires running the app, exercising error paths, checking narrow widths, and reporting exactly what was and was not tested. - Use Case: A user says "I need a dashboard for tracking my freelance invoices." The Skill decides on a single-file HTML app with localStorage, builds the full vertical, runs it, and delivers the exact command to open it plus a list of decisions made on the user's behalf. ## Quick Start Ask the assistant to turn your idea into a working application, for example: "Create a tool that converts CSV files into charts I can share as a single HTML file."

Frequently Asked Questions about materializar-ideia

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

FAQPage Schema
How do I turn a vague app idea into working code?▼

Define three things first: who uses it and why, the single central action, and the hard constraint such as offline use or no backend. Then choose the smallest stack that satisfies that constraint and build one complete vertical instead of many half-finished features.

How to choose a tech stack for a new project?▼

Choose based on where the state lives, not familiarity. Pure calculation needs only a single HTML file; multi-screen state needs a component framework; shared data across devices or secrets the client cannot see require a backend with a database like Postgres.

When does a project actually need a backend?▼

A backend is justified only when data is shared between devices or people, a secret must stay hidden from the client, a rule must be enforced server-side, or long work cannot depend on an open browser tab. Otherwise it is pure cost.

Should I use SQLite or Postgres for a new application?▼

Use SQLite for a single process with predominantly read workloads, such as local tools. Use Postgres as the default for anything multiuser. In all cases, version the schema with migrations from the first table.

What are the limitations of single-file HTML applications?▼

Single-file apps stop serving well when data must persist across devices, an API key must be hidden, or the project grows past roughly three screens with shared state. Above about 1500 lines, navigation within the file also degrades.