user-m

Generate backend User models, auth APIs, and frontend components.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/h617265630/Modularity-skill --skill user-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-m
Source: https://github.com/h617265630/Modularity-skill/tree/main/.claude/skills/user-m
Command: npx skills add https://github.com/h617265630/Modularity-skill --skill user-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

用户系统模块,自动生成 User 模型、注册/登录/资料 API,以及前端 UserProfile、UserList 组件,降低重复实现成本并统一接口风格。

Core Features & Use Cases

  • User model: SQLAlchemy model for users with id, username, email, hashed_password, is_active, avatar_url, bio, created_at, updated_at; no cross-model relationships.
  • Auth APIs: Registration and login endpoints with proper error handling and standardized responses.
  • Frontend components: UserProfile component and UserList page to display and manage user information.
  • Migrations & docs: Migration-ready schema with indices and Swagger/Redoc documentation support.

Quick Start

Generate the user-m module to scaffold backend models, authentication APIs, and frontend UserProfile and UserList components.

Frequently Asked Questions about user-m

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

FAQPage Schema
How do I generate a full-stack user management module with SQLAlchemy and frontend components?

Generating a full-stack user management module involves scaffolding backend SQLAlchemy User models, registration and login APIs, and frontend UserProfile with UserList components. This workflow automates the end-to-end setup to reduce repetitive implementation costs and unify API response schemas.

What fields are included in the SQLAlchemy User model for authentication?

The SQLAlchemy User model includes id, username, email, hashed_password, is_active, avatar_url, bio, created_at, and updated_at. It is designed without cross-model relationships to keep the user management schema self-contained and migration-ready.

Can I use the generated authentication APIs with my existing frontend?

Yes, the generated authentication APIs provide registration and login endpoints with standardized response schemas and Swagger documentation. You can integrate these backend endpoints with an existing frontend by consuming the standardized API responses directly.

What's the best way to scaffold registration, login, and profile endpoints for a new project?

The best way to scaffold registration, login, and profile endpoints is to automate the generation of backend models and authentication APIs alongside frontend components. This provides a cohesive full-stack setup with proper error handling and migration-ready database schema validation.

Why does the User model avoid cross-model relationships?

The User model avoids cross-model relationships to maintain a simple, migration-ready database schema. This design constraint ensures the user management module remains modular and reduces complexity during initial full-stack authentication setup.