ywc-auth-implement

Standardize authentication implementation via policy interviews and subagent dispatch.

8|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-auth-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ywc-auth-implement
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-auth-implement
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-auth-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Implementing authentication is high-stakes and error-prone, often leading to security vulnerabilities when hand-rolled. This skill standardizes the entire process by orchestrating a policy interview, stack-aware library recommendations, and disciplined implementation dispatch.

Core Features & Use Cases

  • Policy-Driven Orchestration: Conducts a 9-category policy interview to ensure all security and compliance requirements are met before implementation begins.
  • Secure Implementation Dispatch: Delegates backend and frontend tasks to specialized agents using a TDD-based ritual, ensuring no hand-rolled crypto or insecure practices are introduced.
  • Automated Security Gates: Enforces mandatory security audits and E2E testing, ensuring that only verified, battle-tested authentication flows are integrated.

Quick Start

Invoke the ywc-auth-implement skill to begin the authentication policy interview and setup process for your current project.

Frequently Asked Questions about ywc-auth-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement secure authentication with OAuth and MFA using TDD?

Implement secure authentication with OAuth and MFA using TDD by conducting a policy interview and dispatching specialized agents for backend and frontend tasks. This enforces automated security audits and E2E testing to guarantee no hand-rolled crypto.

What is the best way to standardize authentication implementation across a new project?

Standardize authentication implementation across a new project by applying a policy-driven orchestration process that covers 9 security and compliance categories. This ensures strict TDD compliance, automated security auditing, and legal documentation drafting before deployment.

Can I use this approach to migrate existing authentication flows to strict security compliance?

Yes, you can migrate existing authentication flows to strict security compliance by applying a standardized policy interview and stack-aware library recommendations. This ensures the migration satisfies automated security auditing and E2E test verification requirements.

Does the authentication implementation process support RBAC and automated security auditing?

The authentication implementation process supports RBAC and automated security auditing by enforcing mandatory security gates and conducting a 9-category policy interview. This ensures only verified, battle-tested authentication flows are integrated into the system.

Why does hand-rolling authentication lead to security vulnerabilities and how to avoid it?

Hand-rolling authentication leads to security vulnerabilities through insecure practices and custom crypto. Avoid it by dispatching implementation tasks to specialized agents using a TDD-based ritual, enforcing automated security gates and E2E testing.

When do I need a policy interview for email and password authentication extensions?

You need a policy interview for email and password authentication extensions when strict security and compliance requirements must be met. It ensures all 9 policy categories are satisfied before stack-aware implementation dispatch begins.