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/styling/quick-start.md
View on GitHub# Small-change workflow
## Eligibility and safety
**Small-change:** ordinary declarations on one locale, at most 3 components/10 style groups in one section, inline-only/stylesheet-only/inline+CSS, at most one **existing** stylesheet and guarded class additions. Require known Bootstrap and local targets. Any raw `css`, global scope, nonempty `externalResources`/`importantReason`, new/shared files, templates or Studio-only work needs **expanded** review; unresolved/generated-source work blocks.
- **Local-only:** no PAC/authentication, remote writes, deployment/ALM, Sync or cache clearing. VS Code Web saves remotely; Desktop Preview uses uploaded content/clears cache. Neither is allowed.
- **Local-first:** use required `owner: "custom"` for **both listed and unlisted** properties. The [map](studio-component-capabilities.md) describes availability, not ownership. Unlisted properties allow safe local styling with warnings. Unknown components/Flex availability stay unverified; no promise values populate native controls.
- **Placement:** use owning inline declarations, locale CSS or reusable Web Files. Web File priority is advisory, not a `displayorder` or runtime load-order prerequisite; see [policy](styling-policy.md). Page Copy uses the selected locale; shared-template inline edits need site scope. Do not blanket-inline reusable styles.
- **Safety:** preserve defaults/order, Bootstrap, unrelated edits, Liquid, IDs, accessibility/Studio markers. Edit winning inline declarations, not ineffective overrides or blind priority escalation. Preserve exact-property inline importance; authored priority needs `importantReason` and expanded review.
- **Boundaries:** no DOM/component replacement, PCF/iframe/third-party internals, installs, generated-output overwrites or hand-edited plans. Keep artifacts private, **outside the uploadable site tree**, out of telemetry.
## Inspect with bounded evidence
Select the locale; save full evidence with a 4,096-byte summary:
```bash
node "${PLUGIN_ROOT}/scripts/style-site/inspect-style-context.js" --siteRoot "<siteRoot>" --summary --out "<workDir>/context.json" --pageId "<pageId>" --target ".pp-card"
```
Use `--page "<name-substring>"` for discovery or offline `--pageId`. Inspector targets are literal IDs/classes/tags, not complex selectors; candidates are advisory.
For consented runtime discovery, follow its reference: `--mode structure --maxCandidates 10 --selector "<section>"`, then `--mode styles --properties padding,border-radius --maxCandidates 1`. Reconcile via `--runtimeSnapshot "<snapshot.json>" --pageId "<pageId>"`. No text/values/credentials/storage/HTML capture or crawling.
## Request and prepare
Placeholder: verify source/`pp-card` and effective CSS; Design-panel support is unverified.
```json
{
"title": "Service card spacing",
"pageId": "<resolved-localized-page-id>",
"components": [{
"id": "service-card",
"label": "Service card",
"kind": "card",
"className": "pp-card",
"sourcePath": "web-pages\\home\\content-pages\\Home.en-US.webpage.copy.html"
}],
"styles": [{
"id": "card-spacing",
"componentId": "service-card",
"owner": "custom",
"scope": "page",
"studioComponent": "Custom card",
"declarations": { "padding": "1rem", "border-radius": "12px" },
"rationale": "Adjust this locale's custom card."
}]
}
```
Optional `location`: `stylesheet` (default) or `inline`. General `declarations` use bundled css-tree, not property/value/part or gradient allowlists; no npm installs. Parser acceptance is not rendering proof. Review unknown/semantic-grammar warnings; fix invalid CSS or verify newer browser support, never bypass errors.
Read the [deep contract/examples](proposal-and-verification.md) for raw `css`, `global: true`, resources, priority and inline/context edits. Scoped CSS needs verified hooks; global themes need no fictitious source/class. Inline `null` removes an exact property; combine scoped CSS in the same approved plan. Preserve other source/priority.
```bash
node "${PLUGIN_ROOT}/scripts/style-site/style-site-workflow.js" --operation prepare --siteRoot "<siteRoot>" --request "<workDir>/request.json" --out "<workDir>/revision-1"
```
Result: `status: "ready-for-review"`, `artifacts: {plan,review}`, `route.name: small-change|expanded`, hash/diff/warnings; no edits. Follow `contrastReview: "required-before-approval"` guidance. **Read full review before approval if truncated** (`truncated=true`). Use a revised request and a fresh directory.
Review targets/diffs, pages/locales, parser/resource warnings and global/priority effects; global means all matching elements in scope. There is **no HTML preview, local server or browser prerequisite**. `owner: "studio"` requires `handoffReason: "user-requested"` plus `studioAction`; native support alone is not a reason. Schema 2 remains; legacy/invalid requests need regeneration/new approval, never inherited consent.
## Apply and independently verify
After host approval of this exact hash:
```bash
node "${PLUGIN_ROOT}/scripts/style-site/style-site-workflow.js" --operation apply --plan "<workDir>/revision-1/style-site.plan.json" --approvedHash "<approved-planHash>" --receipt "<workDir>/receipt-1.json"
```
Require fresh preflights and independent validator success, not just a receipt. Verify blocks/tags, scope, defaults/markers and unrelated bytes. Drift/partial failure needs `6.reapprove`, recovery evidence and new diff/hash approval; never rollback.
Review source colors/semantics. Report **desktop/mobile rendering**, cascade, reflow, contrast and keyboard/states as pending live checks; never upload for evidence.
Explicit instructions-only: verify instructions/no edits; skip apply. Ambiguous/unrepresentable/generated-source local work is **blocked** with a specific local next step, not handoff success. Keep unlisted/unknown/conditional warnings in review, approval and final report. Liquid/native behavior and Studio save/reopen editability remain pending; earlier observation cannot verify unuploaded changes.
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 |