Tenor
Log in
Browse docs

Docs · Reference

Troubleshooting, limits, privacy, and portability

Know what Tenor can refine, where a workflow can break down, and what still belongs in the destination codebase.

6 min read

Outcome and prerequisites

Use this page to diagnose a stuck workflow, set the right boundary for Tenor, and prepare a generated component for safe continuation in code.

  • Tenor creates and refines live React interface components; it is not a full-stack application builder.
  • Tenor uses conversational and visual direction; it is not a manual style-property editor or a Figma replacement.
  • Generated code is implementation material and still requires review before production use.

Troubleshoot the current step

  1. 01

    Reduce the scope

    Work with one component and one judgeable change when a request produces unrelated edits.

  2. 02

    Clarify the source of truth

    State whether the prompt, screenshot, existing code, or selected component should control the result.

  3. 03

    Protect the invariants

    Name the content, behavior, structure, and surrounding regions that must stay unchanged.

  4. 04

    Return to the last working version

    Continue from the strongest saved result instead of repairing several failed directions at once.

  5. 05

    Move application work into the repository

    Use Codex, Claude Code, or your normal engineering workflow for real data, routes, permissions, and integration.

Common limits

  • A broad prompt can produce a plausible redesign instead of the bounded change you intended.
  • A screenshot can show visual truth but not hidden behavior, data rules, or product intent.
  • Existing code may not render when it depends on private packages, unavailable services, or application-wide context.
  • A snip can be ambiguous when the selected region is too small, repeated elsewhere, or tied to a structural change.
  • Voice prompting and native Figma-frame import are not part of the current documented workflow.

Privacy and portability

Do not put secrets, customer data, private source material, or sensitive operational information into a prompt, screenshot, or pasted component.

Before handoff, check that the component source, assets, and dependencies can move into the destination repository. Review accessibility, responsive behavior, interaction states, and compatibility with the application's existing primitives and design system.

Expected result

You should know whether to narrow the request, provide better context, return to a saved version, or continue the work in the destination codebase. When the interface direction is resolved, use the coding-agent handoff guide as the next step.

Try Tenor