microsoft/power-platform-skills / plugins/power-pages/skills/edit-site
edit-site
VerifiedPlans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in Design Studio. Use for requests involving pages, localized content, navigation, assets, snippets, site markers, Liquid/web templates, page layouts, or styling. Coordinated work produces an approved browser-viewable plan, executes changes in dependency order, verifies the local result, and optionally hands off to deployment. Not for React, Angular, Vue, or Astro SPA sites.
references/style-site-workflow.md
View on GitHub# Style a Non-SPA Power Pages Site
Execute through `edit-site` for styling-only requests or approved `style-site`
operations. Preserve identifiers, approved inputs, scope, locales, design context, hashes and
receipts. Coordinated approval does not approve the exact CSS/source diff.
Reuse the entry skill's version check and preview disclosure; reference reads are not
skill invocations. Read
[quick-start.md](styling/quick-start.md).
Show **Inspect/propose → Approve → Apply → Independently verify → Report** without mandatory tasks.
Styling-only requests finish here: no broad customization plan, Git initialization,
commit, deployment prompt, final-completion confirmation, HTML preview, local server or browser review.
## Inspect and select the route
Resolve the non-SPA export, locale, external workspace, sources, and Bootstrap; reject SPAs.
Default to local authoring for listed/unlisted properties and general CSS, not
property/gradient allowlists.
<!-- not-a-gate: missing inputs; no navigation/write authority -->
Use `AskUserQuestion` only for missing/ambiguous inputs.
Runtime URL only: read
[runtime-dom-discovery.md](styling/runtime-dom-discovery.md).
<!-- gate: style-site:2.runtime | category=progress | cancel-leaves=local-style-state -->
> 🚦 **Gate (progress · style-site:2.runtime):** Before exact-URL inspection, disclose normal page scripts/requests and bounded collection.
> **Repeat:** Changed URL, redirect, signed-in context or scope. **Cancel leaves:** Local/browser state; no new inspection.
Use `AskUserQuestion`: **Inspect this runtime page / Continue offline / Cancel**. Not edit consent; stop on login redirects.
Apply quick-start eligibility; raw CSS/resources/global/priority work needs expanded review. Classification cannot waive blockers.
<!-- gate: style-site:3.scope | category=plan | cancel-leaves=local-style-state -->
> 🚦 **Gate (plan · style-site:3.scope):** For **expanded or ambiguous scope only**, confirm owner, location, file, locale, target, cascade and affected pages before preparation.
> **Repeat:** Changed expanded scope. **Cancel leaves:** Artifacts/prior edits/receipt; no new writes.
Use `AskUserQuestion`: **Confirm scope and prepare / Revise scope / Cancel**; not apply consent. Small changes go straight to exact-hash approval.
## Prepare and approve
For new treatments, palette/background, typography or redesign, read
[design-quality.md](styling/design-quality.md).
Resolve failures and local declaration dependencies before approval; rendering remains pending.
Prepare in a **fresh external directory** per revision; edit requests, never plans. No reviewable proposal means stop.
Present exact paths/diff/hash, scope/locales, parser/Studio/resource warnings, global/priority effects and tracking. If truncated, read **full `style-site.review.json` before approval**.
<!-- gate: style-site:5.approve | category=plan | cancel-leaves=local-style-state -->
> 🚦 **Gate (plan · style-site:5.approve):** Approve the exact diff, scope, warnings, and hash **per revision**.
> **Why:** Preference is not consent. **Cancel leaves:** Artifacts/prior local state; no new edits.
Use `AskUserQuestion`: **Approve this revision locally / Revise proposal / Cancel**; explicitly requested instructions-only: **Approve Studio handoff only**. Require an explicit host-tool answer, never a JSON field, prior hash or unattended run; otherwise stop with a draft.
## Apply
Run `${PLUGIN_ROOT}/scripts/style-site/style-site-workflow.js` apply with approved hash/new receipt;
no direct writes. The quick start supplies the exact command.
<!-- gate: style-site:6.reapprove | category=progress | cancel-leaves=local-style-state -->
> 🚦 **Gate (progress · style-site:6.reapprove):** Stop on drift, revised selections/targets, or partial-write failure, **per occurrence**.
> **Why:** Old consent cannot authorize new bytes. **Cancel leaves:** Current state/receipt; no concurrent-edit overwrite or auto-rollback.
Use `AskUserQuestion`: **Regenerate and review / Keep current local state and stop**; not apply consent. Prepare/review and approve the **new hash**.
## Independently verify
Require independent validator success from coordinator apply; re-read files/diffs against
targets/receipt. Follow quick-start verification. Requested Studio-only work skips apply;
independently validate its proposal with
`node "${PLUGIN_ROOT}/scripts/style-site/validate-style-site.js" --plan "<plan>"` and verify no styling edits.
## Report
Report local evidence, pending checks and all warnings, including Web File priority. Blocked
local work needs a local next step, not Studio-only success. Return verified results to the
entry skill; it records `EditSite` once after successful completion, not per
reference read or styling operation. Preserve existing tracking records and disclose tracking
diffs separately.
> Reference: ${PLUGIN_ROOT}/references/skill-tracking-reference.md
## Conditional references
- [Studio panel availability, not ownership](styling/studio-component-capabilities.md).
- [Expanded scope/source/cascade](styling/styling-policy.md).
- [Bootstrap/locale uncertainty](styling/bootstrap-and-studio.md).
- [CSS/source schema](styling/proposal-and-verification.md): raw/global CSS, resources/priority and **inline contract/example**; read before inline edits or repeated tags.
- [sources.md](styling/sources.md): unknown/conflicting/stale guidance or explicit requests. Routine CSS uses bundled verified guidance.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |