OpenParable
Skip to content
← Back to skills

Frontend Pane Lifecycle

Development
frontend-pane-lifecycle

Frontend Pane Lifecycle is an Agent Skill for development published in the fossasia/visdom repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Build and debug pane lifecycle behavior in the React frontend. Use when adding pane actions, layout behavior, rendering updates, or pane-level interactions.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/fossasia/visdom/blob/HEAD/.agents/skills/frontend-pane-lifecycle/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/frontend-pane-lifecycle, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Skill: Frontend Pane Lifecycle

When to Use

Use this skill when changing pane rendering, pane actions, or lifecycle events.

Core Workflow

  1. Trace pane flow in js/main.js from incoming command to rendered pane.
  2. Update pane components in js/panes/ with existing memo/ref patterns.
  3. Keep layout and focus behavior compatible with current grid logic.
  4. Ensure topbar and modal interactions remain coherent with pane state.
  5. Verify close/save/reset behavior and content refresh semantics.

Guardrails

  • Preserve React.memo and render-coalescing assumptions.
  • Do not break pane IDs, titles, or layout item contracts.
  • Keep compatibility with existing pane types and settings registration.

Documentation

  • Skill reference
  • js/main.js
  • js/panes/
  • js/settings.js
  • js/topbar/
  • AGENTS.md
  • CONTRIBUTING.md

Assets

  • See assets/README.md and store templates/resources in assets/.

Tests

  • Follow the default flow in references/TESTS.md.