create-webroles

name	create-webroles
description	This skill should be used when the user asks to "create web roles", "add web roles", "set up web roles", "add roles", "create roles for my site", "manage web roles", "add authenticated role", "add anonymous role", or wants to create web roles for their Power Pages code site. Web roles control access and permissions for site users.
user-invocable	true
allowed-tools	Read, Write, Bash, Grep, Glob, AskUserQuestion, Task, TaskCreate, TaskUpdate, TaskList
model	opus
hooks	{"Stop":[{"hooks":[{"type":"command","command":"node \"${CLAUDE_PLUGIN_ROOT}/skills/create-webroles/scripts/validate-webroles.js\"","timeout":15},{"type":"prompt","prompt":"If web roles were being created in this session (via /power-pages:create-webroles), verify before allowing stop: 1) The .powerpages-site/web-roles/ directory was checked for existing roles, 2) New web role YAML files were created with valid UUIDs generated by the generate-uuid.js script, 3) All web role files were verified (valid UUIDs, correct format, no duplicate flags), 4) The user was asked to deploy the site to apply the new roles. If any of these are incomplete, return { \"ok\": false, \"reason\": \"<specific issues>\" }. If no web role work happened or everything is complete, return { \"ok\": true }.\n","timeout":30}]}]}

Create Web Roles

Create web roles for a Power Pages code site. Web roles define the permissions and access levels for different types of site users.

Core Principles

• Use TaskCreate/TaskUpdate: Track all progress throughout all phases — create the todo list upfront with all phases before starting any work.
• Always use the UUID script: Never generate UUIDs manually — always use ${CLAUDE_PLUGIN_ROOT}/scripts/generate-uuid.js to produce valid UUID v4 values for each web role.
• Preserve uniqueness constraints: Only one role can have anonymoususersrole: true and only one can have authenticatedusersrole: true. Always check existing roles before setting these flags.

Prerequisite: The site must be deployed at least once before web roles can be created, since deployment creates the .powerpages-site folder structure that stores web role definitions.

Initial request: $ARGUMENTS

---

Workflow

1. Phase 1: Verify Site Structure → Check for .powerpages-site/web-roles/ directory
2. Phase 2: Discover Existing Roles → Read current web role YAML files
3. Phase 3: Determine New Roles → Analyze the site and ask the user what roles are needed
4. Phase 4: Create Web Role Files → Generate YAML files with UUIDs from the Node script
5. Phase 5: Verify Web Roles → Validate all created files exist, have valid UUIDs, and flags are correct
6. Phase 6: Review & Deploy → Present summary and proceed to deployment

---

Phase 1: Verify Site Structure

Goal: Confirm the .powerpages-site/web-roles/ directory exists and is ready for web role files

Actions:

1. Look for the .powerpages-site/web-roles/ directory in the project root. Use Glob to search:

   **/.powerpages-site/web-roles
   

2. Also locate the project root by finding powerpages.config.json:

   **/powerpages.config.json
   

3. If .powerpages-site folder does NOT exist: