Skip to content

2001105254-netizen/RacePulsePH / .agents/skills/racepulse-access-validation

racepulse-access-validation

Verified

Validate RacePulsePH access policies and plan staged deployment of cloud rules, Functions, Storage and local race-day authorization.

Validate RacePulse access changes

Use docs/access-control-plan.md for acceptance criteria and docs/access-control-progress.md for deployed status. Run npm run verify:rbac with Java 21+ and Firebase CLI available. This runs type/build checks, policy/account/timing tests, real local HTTP route tests, and Firestore/Storage/transaction emulator tests against a demo project.

Policy unit tests do not prove Firestore, Storage, API or LAN enforcement. Before activating the rollout, add emulator and request-level checks covering explicit allow/deny, four roles, approval, scope, direct mutations, account switching, revocation, pending payments and offline replay.

Validate role changes concurrently, retry duplicate requests, and attempt self/last-Super-Admin removal. Access history must be committed with the mutation and cannot be client-editable.

Verification writes output/rbac-verification.json with a source hash. scripts/migrate-access.cjs --apply --activate checks that hash and freshness before activation. Set FIREBASE_TOOLS_PATH to the CLI package for authenticated management calls; do not copy credentials into the repository. Backfill preserves roles and uses transactions. Inspect production indexes before adding access-history indexing; preserve unrelated indexes.

Do not set enforcementReady true until enforcement, migration and deployments are complete. Record evidence and limitations in the rollout document. Production deployment and live account changes need authorization for that operation; never infer permission from these skill instructions.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 197kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall