settings-flow

Automate OrcaQ settings panel creation with a type-to-component data flow.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/cin12211/orcaq-test --skill settings-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: settings-flow
Source: https://github.com/cin12211/orcaq-test/tree/main/.github/skills/settings-flow
Command: npx skills add https://github.com/cin12211/orcaq-test --skill settings-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a complete blueprint for managing user settings across OrcaQ, enabling consistent, scalable configuration across UI panels.

Core Features & Use Cases

  • 4-layer flow for settings (type → constant → store → component) ensures a single source of truth and predictable behavior.
  • Guidelines to add, update, and remove settings panels across Appearance, Editor, Quick Query, and Agent areas.
  • Persistence via Pinia's persisted store ensures settings survive sessions.

Quick Start

Open the Settings modal and follow the documented steps to add a new setting panel, wire it through the four-layer flow, and expose it in the navigation.

Frequently Asked Questions about settings-flow

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

FAQPage Schema
How do I structure a scalable settings flow in Vue?

A scalable settings flow uses a 4-layer architecture: type definitions, constants, Pinia store, and UI components. This structure ensures a single source of truth and predictable behavior when adding, updating, or removing settings panels.

How do I persist user preferences across sessions with Pinia?

To persist user preferences across sessions with Pinia, apply the persisted store plugin. This ensures that configuration choices in Appearance, Editor, Quick Query, and Agent modules survive page reloads and browser restarts.

What is the data flow for adding a new settings panel?

The data flow for adding a settings panel follows the sequence: type, constant, store, component. You define the data type, register the constant, wire it through the Pinia store, and finally expose it in the UI component and navigation.

Does this settings architecture work for multiple application modules?

Yes, this settings architecture works across multiple modules. It provides standardized guidelines to add, update, and remove configuration panels specifically for Appearance, Editor, Quick Query, and Agent areas.

When do I need a standardized configuration architecture?

You need a standardized configuration architecture when managing user settings across multiple UI panels to ensure consistency. It prevents fragmented state by establishing a single source of truth for application settings.