platform-conventions

Document platform patterns and generate a Platform Context Document for brownfield Qlik projects.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Pupfish-LLC/qlik-agents --skill platform-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-conventions
Source: https://github.com/Pupfish-LLC/qlik-agents/tree/main/skills/platform-conventions
Command: npx skills add https://github.com/Pupfish-LLC/qlik-agents --skill platform-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and standardizes platform patterns for brownfield Qlik projects, enabling consistent adoption of shared subroutines, naming standards, connection practices, and QVD conventions across teams.

Core Features & Use Cases

  • Structured templates for documenting existing app inventory, shared subroutine catalogs, naming convention maps, data connection standards, QVD storage conventions, and organizational coding standards.
  • Reusable guidance for Phase 0 context ingestion and Phase 4 script development to ensure platform compatibility.
  • Generates Platform Context Documents that serve as decision records for reconciling platform vs. framework conventions.

Quick Start

Review inputs in inputs/ to begin populating the Platform Context Document for your brownfield Qlik environment.

Frequently Asked Questions about platform-conventions

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

FAQPage Schema
How do I document existing Qlik platform conventions for a brownfield project?

To document Qlik platform conventions for a brownfield project, use structured templates to inventory subroutines, naming maps, connection standards, and QVD storage patterns. This produces a Platform Context Document to guide subsequent development phases.

What is a Platform Context Document used for in Qlik development?

A Platform Context Document in Qlik development serves as a decision record for reconciling existing platform conventions with framework defaults. It standardizes organizational coding standards across inputs and libraries to ensure team-wide consistency.

How do I standardize QVD storage and naming conventions across Qlik apps?

Standardize QVD storage and naming conventions by mapping existing patterns into structured documentation templates. This captures subroutine catalogs and data connection standards, enabling consistent adoption across all Qlik apps.

Can I use these documentation templates for greenfield Qlik deployments?

These documentation templates target brownfield Qlik environments to capture pre-existing platform patterns. Greenfield deployments lack existing conventions to inventory, making this context ingestion unnecessary for initial framework setup.

When do I need to capture platform conventions during the Qlik development lifecycle?

Capture platform conventions during Phase 0 context ingestion before Phase 4 script development. This ensures platform compatibility by inventorying resources and applying shared subroutine standards before writing new scripts.

What's the best way to reconcile framework defaults with existing Qlik coding standards?

The best way to reconcile framework defaults with existing Qlik coding standards is to generate a Platform Context Document. This inventory of existing resources enables informed reconciliation between platform conventions and framework defaults.