pp-sync

Microsoft Power Pages classic portals, the hybrid Liquid + Web API pattern. Server-rendered Liquid templates with client-side Web API calls in custom JS. Use for *.webpage.copy.html, *.webtemplate.source.html, *.webpage.custom_javascript.js, fetchxml, entitylist/entityform/webform, web roles, table permissions, and pac paportal. NOT for code sites (use Microsoft's power-pages plugin); for Dataverse-side work, defer to Microsoft's dataverse plugin.

Claude Code plugins for Microsoft Power Pages classic portals: native Power Pages Studio hybrid Liquid + Web API development, pac paportal sync, and permissions audit

Audit a Power Pages classic portal's Web Roles, Table Permissions, Site Settings, and Web API configuration for misalignments, orphaned permissions, missing site settings, exposed fields, broken polymorphic lookups, and security gaps.

Source-anchored architecture + delivery methodology: 30 skills in four families. METHODOLOGY CORE (15) — the driver+architect triangle: /methodology (entry wizard) + /methodology-resume, the active /methodology-drive gate driver, /architect whole-project review, /stakeholder-walk (+ /walk-amend, /walk-packet, /counsel-packet), source + gap tooling (/statute-pull, /gap-analysis, /enrich-ads, /pattern-section, /brief-scaffold), /methodology-extract meta-process, and the /vault per-project state manager — which now links vaults to sibling projects, harvest sources, and design lineage through typed cross-references (vault schema 1.3). PM / BOARD-EXPERT (5) — /pm-ground, /pm-audit, /pm-advise, /pm-operate, /pm-migrate: reasons in a platform-neutral canonical board model and translates through grounded GitHub / GitLab / Jira / Azure DevOps adapters; writes are surface-gated. BA / REQUIREMENTS-MODELING (6) — /ba-ground, /ba-model, /ba-plan, /ba-flow, /ba-data, /ba-trace: board-canonical requirements (epics / work-items / definitions-of-done), pluggable prioritization, mermaid BPMN-lite and ER models, and a traceability matrix that renders captured links and flags gaps rather than inferring them. TECHNICAL-DOCUMENTATION (4) — /doc-ground, /doc-compose, /doc-sync, /doc-generate: source-bound documents where every section records what it came from, so documents are regenerable projections and drift is detectable; composes board artifacts into an SRS, generates architecture (arc42/C4), api (OpenAPI), or data (ER) docs from a codebase, and detects drift by re-projecting from the source and diffing. Standards are Source-Anchored with recorded provenance.