Make the canvas app decisions that generation can't — is canvas even the right shape, delegation and data strategy, screen and navigation architecture, conventions — then hand a decided build plan to Microsoft's canvas authoring tooling. Checkpoints at real data volumes, because a 50-row test proves nothing. Methodology, not mechanics.
8 on GitHubby Howdang Rashidv0.2.1MITupdated today
/
Plugin canvas-planner from marketplace powercademy-skills in Powercademy/powercademy-skills. Commands read from the repo's manifest — today.
What it installs
Skills (1)
plan-canvas-app
Make the decisions that determine whether a Power Apps canvas app survives contact with real data - delegation strategy, data architecture, screen and navigation design, performance conventions - and produce a build plan Microsoft's canvas authoring tooling can then execute. Trigger whenever the use
Powercademy's living conventions for Power Platform delivery — Dataverse schema judgement (statecode over custom status, solution and publisher discipline, dependency packaging), the Power Automate and PCF lessons that cost hours once (editing live flows, child-flow contracts, whether PCF is the right tool, the premium-licensing trap), applied before and alongside any build, model-driven app UX (every command button has an icon that says what it does, modal focused-task dialogs), the tool-selection ladder (purpose-built tools, then SDK / Web API / CLI, browser automation only where nothing else reaches), plus the writing-skills house standard for authoring skills that work in both runtimes. Each rule carries its reasoning; the lists grow with every corrected mistake.
Power Platform ALM the Powercademy way — design the delivery process (environments, solution segmentation, publisher, the config boundary, promotion path and approvals), then run promotions with checkpoints that stop before anything irreversible. Routes execution to Microsoft's Dataverse solution skills, native pipelines and pac CLI rather than rebuilding them. A production import is always a red checkpoint.
Takes a machine from nothing to fully equipped for end-to-end Power Platform development, then keeps it healthy. setup-workstation asks which workloads you'll build, installs the SDKs, CLIs, Microsoft's plugins and MCP servers with one approval, and writes an IT request for anything needing admin rights; check-setup diagnoses and repairs auth profiles, tenants, outdated tools and plugin drift. Both read one versioned toolchain manifest that a weekly upstream watch keeps current.
Delegates dbt and warehouse work to altimate-code, a specialized CLI agent with 100+ purpose-built data tools (SQL analysis, column-level lineage, dbt build/test/run, warehouse profiling, FinOps, connectivity to Snowflake, BigQuery, Redshift, Databricks, Postgres, MySQL, DuckDB).
Entry point for Internet Court and the agentic economy stack: natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, GenLayer dispute resolution, and the vendored protocol + connector skills it routes to.
96 skills
internet-court/internet-court-skill 7,112
Maintain canvas-planner?
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.