Thallo remix

Thallo Remix

Turn a design direction into a working website while keeping the user in control of consequential choices. A Thallo spec may be the primary direction, one material among several, or absent when no catalog entry fits.

Route the work

• Read interview.md to establish intent, constraints, approval boundaries, and a compact approval summary.
• Read materials.md whenever the user supplies or points to any useful material, or when relevant material must be discovered or reconciled.
• Read catalog.md when the user asks to find or compare a spec, supplies only a product name or URL, or when a catalog match may help a new website request.
• Read greenfield.md when creating a new project or a deliberately independent replacement.
• Read brownfield.md when changing an existing codebase, integrating only part of a design, or continuing prior work.
• Read verification.md before claiming implementation is complete.

Load only the references needed for the current responsibility. Brownfield owns later-session recovery; there is no separate recovery route.

Common workflow

1. Understand what the user is trying to achieve before recommending a direction.
2. Inventory all available materials and investigate facts that can be discovered safely.
3. Resolve only ambiguity that would materially change the result. Ask related questions together.
4. Present one approval summary covering direction, preserved material, planned changes, architecture, and verification.
5. Wait for approval before implementation when the direction or scope is consequential. A discovery-only request may end with recommendations.
6. After approval, implement autonomously inside the approved boundary. Escalate only a newly discovered choice that would materially change it.
7. Verify in proportion to risk, repair material failures, and report what is actually complete.

Operating principles

• Preserve the user’s real goal, not merely the most visually obvious material.
• Treat supplied material types as open-ended. Use suitable specialist capabilities when available and ordinary agent capabilities when they are not.
• Do not force a Thallo recommendation when the catalog does not contain a close fit or the user declines the candidates.
• Do not silently invent missing brand assets, copy, data, or product decisions. Resolve them explicitly or agree on a clearly labeled temporary substitute.
• Add compatible dependencies within an approved architecture without repeated permission. Seek approval before changing the foundational framework, deployment model, data model, or approved scope.
• Follow repository-local instructions and preserve an existing project’s stack unless the user approves a foundational change.
• Never treat a successful build alone as proof of visual, behavioral, or responsive completion.
• Never claim support for an input source, connector, environment, or installation path that was not actually available or verified.