Skip to content

Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-team-auth-access

saas-team-auth-access

Unverified

Orchestrate auth, RBAC, session security, and multi-tenant RLS specialists end-to-end.

Running this workflow on this client

Run commands from the project root (use Git Bash on Windows if bash points to an unavailable WSL distro). Shared studio files live in .claude/; follow .agents/PORTABLE-RUNTIME.md and .claude/docs/config-resolution.md for client tools, delegation, and approval rules.

Run bash .claude/hooks/yaml-helper.sh resolve_config --keys locale,review_mode,automation and use its output below.

Resolved above — use as-is; --review overrides review_mode for this run.

Team Authentication & Access

Locale & User Profile: Match locale (pt-BR → natural Brazilian Portuguese questions/options, overriding English examples; en → English) and user_profile (founder → plain business language with (Recomendado) first, zero tech jargon; developer → technical). Keep code/tests in English.

Orchestrate the authentication, authorization, and multi-tenancy team to build secure login, RBAC permissions, session handling, team invites, and organization switching.

Argument check: If no description is provided, output:

"Usage: /saas-team-auth-access [feature description] [--review full|lean|solo] — Describe the auth or access feature (e.g. Email+Password auth with magic links, Google/GitHub OAuth, Organization invite & RBAC, Multi-tenant Row-Level Security, Session revocation)."

When this skill is invoked with a valid argument, orchestrate the team:

  1. Security & Data Modeling:

    • auth-security-specialist: Specify threat model, cookie security flags (HttpOnly, SameSite=Lax, Secure), session duration, and CSRF strategy
    • backend-engineer: Database migration for User, Account, Session, Organization, and Membership models
    • Define Row-Level Security (RLS) policies or middleware tenant guards
  2. Backend API & Middleware:

    • backend-engineer: Implement OAuth callbacks, email verification token generation, password hashing (Argon2id/bcrypt), and role authorization middleware (requireRole('admin'))
  3. Frontend Flows:

    • frontend-engineer: Login, Registration, Forgot Password, and Accept Invite screens
    • Session context provider (useUser, useTenant), protected route wrappers, and error alert banners
  4. Testing & Security Validation:

    • qa-manual-tester: Test valid and invalid login attempts, token tampering, expired links, and cross-tenant access denial
  5. Verdict:

    • Output: COMPLETE — authentication and access controls designed, implemented, and verified.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall