القائمة
Use for Auth0 configuration - native application, callback/logout URLs, the Apple connection, and writing the public env vars (part of Stage 1 of SUBMISSION.md, only when the app uses auth)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when creating a new .NET CLI/console project from the agent-harness template ("new cli tool", "new console app", "new dotnet project"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new .NET ETL/API service from the agent-harness template ("new api", "new etl service", "new backend service"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new Expo/React Native app from the agent-harness template ("new expo app", "new mobile app", "scaffold an app with payments"). Scaffolds, stamps provenance, and verifies guardrails.
Use at session start when config-doctor reports the project is not build/deploy-ready, or when the user asks to set up the project - interviews the user, gets EAS logged in / project linked / iOS credentials provisioned and a real bundle id, offers optional payments/auth/API config, and records decisions so the session-start nudge goes quiet
Use when asked to report harness feedback, promote captured guardrail failures into issues, or check "anything worth turning into a rule?". Clusters unreported feedback events and raises digest issues on the agent-harness repo.
Use after a PR merges, or on request, to capture human review comments from a PR into the harness feedback store ("capture the review comments", "harvest PR feedback"). Routed from the merge step.
| name | auth-setup |
| description | Use for Auth0 configuration - native application, callback/logout URLs, the Apple connection, and writing the public env vars (part of Stage 1 of SUBMISSION.md, only when the app uses auth) |
Drives https://manage.auth0.com via Playwright MCP browser tools. Only run this when the app uses auth (the user wants a login).
Snapshot before creating anything. If the application/connection already exists, verify its configuration matches SUBMISSION.md, record what is missing, and only create the missing pieces. On unexpected page state: stop, snapshot, report.
apptemplate://redirect for the template, or the scaffolded app's scheme).
Cross-check the scheme against scheme in app.config.js.offline_access)..env.production and .env.local:
EXPO_PUBLIC_AUTH0_DOMAIN=<domain> and EXPO_PUBLIC_AUTH0_CLIENT_ID=<clientId>.
These files are gitignored — confirm with git check-ignore .env.production
before writing. Never write the Auth0 client secret into the repo (the native
PKCE flow does not need it).npm run doctor — the auth checks should pass.