# Intelligent Interfaces: portable prompts Original Starlight self-study ยท checked 2026-10-20 https://starlightintelligence.academy/academy/intelligent-interfaces Automatic Intelligent UI is a Chat capability. The separate @Visualize plugin supports eligible Chat and Work sessions on web; other clients vary. A prompt cannot install a capability, grant authority or guarantee a render. These prompts run in your chosen host. ## 1. Compare with evidence Surface: Chat Compare my alternatives on the same decision-relevant criteria. Separate facts, assumptions and unknowns; attach sources to factual claims. Render a compact comparison and let me change one useful input when supported. Give a readable fallback and the next reversible test. ## 2. Reveal the system Surface: Work Map this system as a compact, labeled interactive diagram when supported. Show the owner, inputs, transformations, external actions and failure/recovery boundaries. Let me inspect a node without hiding the whole system. Supply a static text equivalent and original SVG or HTML. ## 3. Explore a trade-off Surface: Chat Build a small interactive explorer for this trade-off. Use only supplied data or clearly labeled assumptions. Expose at most two meaningful controls, show units and uncertainty, and explain the selected state. Do not invent measured precision. Include the underlying formulas and a static fallback. ## 4. Teach one decision Surface: Work Teach this workflow through one decision at a time. First ask me for an unaided prediction and a reason; wait for it. Then show only the source evidence I need. Give a hint before a worked example. Compare my answer to the authored example without treating disagreement as a verified assessment. Ask for one revision and a fresh transfer case. Keep original and revised reasoning distinct. Use Starlight's available learning, architecture and review skills only within their actual tools and permissions. End with a portable practice note containing artifact, sources, changes and unresolved questions. ## 5. Art-direct the artifact Surface: Work Build a self-contained HTML learning workbench for my supplied workflow. Show inputs, preparation, review and output. Add one meaningful control that changes the approval boundary, with a text explanation of the change. Use Starlight's obsidian, restrained ice-blue, editorial typography and shallow smoked glass. Keep body text on a high-contrast plane. Support 320px, keyboard, 200% zoom and reduced motion. Include loading, empty and failure states only where a real operation needs them. Label synthetic examples. Return original HTML, supplied data, a screenshot when supported, and a concise inspection note. Do not make external calls or invent an integration. ## 6. Ship the vertical slice Surface: Codex Implement this reviewed visual artifact in the repository that owns the production route. Read applicable AGENTS.md, architecture decisions, dependencies and release instructions. Record the exact base revision. Reuse installed Starlight AI Architect and relevant design/verification skills when present; report unavailable bindings. Preserve unrelated changes. Implement one complete interaction with accessible narrow-screen, keyboard, error and export behavior. Run the required repository checks and inspect a Git-backed preview. Return the patch, actual check results, preview source SHA, rollback and unresolved limitations. Release only within my authorized scope and the repository's acceptance gates. ## 7. Prototype the API boundary Surface: API Design a typed research-card integration using the repository's current stack. Begin with local fixtures: valid, missing source, invalid shape, partial result and provider failure. Define an allowlisted result schema, validate on the server, and map it to accessible application-owned components. Show sources, checked dates and uncertainty beside claims. Use current official OpenAI and Vercel documentation; distinguish stable capability, beta access and a proposed experiment. Preserve the existing orchestration owner. Keep secrets server-side, set a request budget and cancellation path, and require explicit opt-in before a billable live call. Do not execute model-produced markup. ## 8. Shoot the build Surface: Work Use this actual artifact and its accepted evidence to prepare a recording package. Produce a 60-second script with five timed shots, a six-minute walkthrough outline, caption text, transcript draft, three accurate titles and one useful call to action. Separate captured proof from shots still needed. Show the input, prompt, one interaction, a limitation and the portable result. Draft an answer-first lesson with primary references, checked date, accessible image descriptions and relevant internal links. Name providers as technologies used; describe any collaboration or partnership only with owner-approved substantiation. Keep publication and external messages pending until separately authorized.