ppbp-dataverse-metadata
claudeDataverse schema design best practices: table, column and global Choice conventions, model review, and dev-only, confirm-first change principles — whatever tool applies the changes.
5 skills
Power Apps Code Apps best practices: tooling, UI/logic architecture, component reuse and async states, server-side Dataverse data access through TanStack Query, centralised error handling, app review, and UX/UI theming with the shared uxui/ design system.
Plugin ppbp-codeapps from marketplace powerplatform-bestpractices in tchinnin/powerplatform-bestpractices-skills. Commands read from the repo's manifest — 10 days ago.
ppbp-codeapps-architectureArchitecture of a Power Apps Code App: strict isolation between UI and logic through layers (generated, services, queries, actions and form hooks, pure rules, presentational components, pages), src/ organisation by feature, a decision tree for where state lives (TanStack Query, route, React Hook For
ppbp-codeapps-componentsComponent practices for Power Apps Code Apps: search and reuse existing components before creating one, extend primitives with variants, promote shared pieces, use one shared DataTable and AsyncState so every table, grid and async block renders loading, error, empty and no-result states, plus forms
ppbp-codeapps-dataDataverse and connector data access in Power Apps Code Apps: every call through a service wrapper and TanStack Query, work delegated to the server (native OData, then FetchXML through the Dataverse connector, then bound or unbound Custom APIs), bounded and paginated lists, counts, writes and cache p
ppbp-codeapps-errorsIndustrialised error handling for Power Apps Code Apps: one AppError model, one normaliser that classifies Dataverse and connector failures by error code, one services/dataverse-result.ts module, global TanStack Query error channels, route and zone error boundaries, user-facing versus technical mess
ppbp-codeapps-overviewPower Apps Code Apps domain overview. Use when starting any Code App task — scaffolding, architecture, components, Dataverse data access, error handling, review or deployment. Provides the repository layout for Code Apps (including the mandatory docs/<app-name>/ call map), the five team principles s
ppbp-codeapps-reactGeneric React 19 and TypeScript rules (community standards, react.dev) as applied in Power Apps Code Apps: hooks, derived state, effects, list keys, conditional rendering, strict typing without non-null assertions, measured performance and behaviour-driven tests. Use when the user writes or reviews
ppbp-codeapps-reviewRead-only quality review of an existing Power Apps Code App against the ppbp Code App conventions — error handling, Dataverse data access and load, TanStack Query usage, state placement, UI/logic isolation, component reuse, async states, accessibility, typing, tooling and bundle — with a report rank
ppbp-codeapps-setupAdditive best practices for Power Apps Code Apps scaffolding, dependencies and tooling. Use when the user is scaffolding a new Code App (template choice), choosing or upgrading dependencies, configuring environment-specific values, or setting up the tooling baseline — strict TypeScript, ESLint (reac
ppbp-codeapps-uxuiBest practices for applying your own or your company's UX/UI guidelines to a Power Apps Code App. Use when the user wants to brand a Code App, apply a colour palette / typography / spacing system, set up design tokens or a theme, work with design guidelines, or turn HTML/Claude design previews into
Dataverse schema design best practices: table, column and global Choice conventions, model review, and dev-only, confirm-first change principles — whatever tool applies the changes.
5 skills
Dataverse plug-in best practices: project scaffolding and build, step and Custom API design, and dev-only, confirm-first registration principles — whatever tool registers them.
4 skills
Power Platform ALM best practices: solution design, naming, versioning, segmentation, and deployment pipelines.
3 skills
Dataverse data manipulation best practices: script naming and lifecycle, idempotency, initial data import, bulk operations, dependency ordering, and environment segmentation.
3 skills
Power Platform project orientation: canonical repository layout, skill routing, README requirements, and agent instruction files.
3 skills
Power Apps Generative Pages best practices: repository organisation, page naming and splitting, and Fluent v9 branding with the shared uxui/ design system.
2 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.