add-username-handle-route

Generate unique entity profile handles with availability checks and regex routing.

Updated May 30, 2026
One-click install
npx skills add https://github.com/buitrankimlong/thongtincty --skill add-username-handle-route
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-username-handle-route
Source: https://github.com/buitrankimlong/thongtincty/tree/main/.claude/skills/add-username-handle-route
Command: npx skills add https://github.com/buitrankimlong/thongtincty --skill add-username-handle-route

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of creating unique, public URLs for entity profiles, streamlining the routing of users to their respective profiles.

Core Features & Use Cases

  • Unique URL Generation: Automatically generates user-friendly handles for entity profiles.
  • Reserved Words List: Ensures no route conflicts with reserved words.
  • Availability Check: Validates the availability of the chosen handle.
  • Client-Side Validation: Provides debounced validation for handle input.
  • Regex Route Placement: Utilizes regex for precise route matching.
  • Use Case: Ideal for creating user handles for personal users, companies, investors, etc., to replace less user-friendly UUID-based URLs.

Quick Start

Run the 'add-username-handle-route' skill to create a unique URL for a user's profile.

Frequently Asked Questions about add-username-handle-route

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

FAQPage Schema
How do I generate unique user handles for entity profile URLs?

Unique URL generation for entity profiles automates the creation of user-friendly handles to replace UUID-based URLs. It integrates availability checks and client-side validation to ensure a conflict-free URL structure for personal profiles, companies, and investors.

What is the best way to prevent route conflicts with reserved words when routing user handles?

Preventing route conflicts with reserved words involves maintaining a dedicated reserved words list during handle generation. This ensures newly created user handles for entity profiles do not collide with existing application routes or restricted terms.

How does regex handle routing work for public entity profiles?

Regex handle routing works by utilizing regular expressions for precise route matching of entity profiles. This approach targets user-facing handle routing, ensuring personal users, companies, and investors receive accurate and conflict-free URL structures.

Can I use client-side validation to check handle availability before submitting a profile?

Yes, client-side validation checks handle availability before submitting a profile. The system provides debounced validation for handle input, checking availability against existing entity profiles to prevent conflicts in real-time.

Does this handle routing approach work for both personal users and company profiles?

Yes, this handle routing approach works for both personal users and company profiles. It specifically targets user-facing handle routing for personal profiles, companies, and investors, replacing less user-friendly UUID-based URLs.

Why should I replace UUID-based URLs with user-friendly handles for entity profiles?

You should replace UUID-based URLs with user-friendly handles to simplify creating unique public URLs for entity profiles. This streamlines routing users to their respective profiles, improving overall user experience and URL memorability.