Teach AI how to name your files!
Then AI will understand your project better and help you more effectively.

🌐 Language: English | 한국어 | 日本語 | 中文

✅ Anyone using AI tools like Claude, ChatGPT, Cursor
✅ People struggling with too many files
✅ Teams wanting consistent file naming rules
✅ Anyone wanting AI to understand their project better

login.js user_page_final_v2.jsx payment_fixed.py test123.sql 

Result: AI gets confused and makes mistakes 😵

001_FE_User-Login_C_Page_PROD.jsx 002_BE_Payment-Process_X_API_PROD.py 003_DB_User-Schema_C_Migration_PROD.sql 004_TEST_Login_Unit_DEV.test.js 

Result: AI understands perfectly and helps better! ✨

Just say in plain language:

• "Create a login page" → AI makes: 001_FE_User-Login_C_Page_PROD.jsx
• "Add payment refund API" → AI makes: 021_BE_Payment-Refund_C_API_PROD.py
• "Create product table" → AI makes: 005_DB_Product-Schema_C_Migration_PROD.sql

Your project stays organized automatically:

my-project/ ├── 00_DOCS/ 📚 Documentation ├── 01_CONFIG/ ⚙️ Settings ├── 02_STATIC/ 📦 Images, fonts ├── 03_ACTIVE/ 🔥 Your main code ├── 04_TEST/ 🧪 Tests ├── 05_BUILD/ 🏗️ Build files ├── 06_LOGS/ 📊 Logs └── 07_META/ 🎯 AI collaboration files 

• Claude writes code
• Cursor reviews it
• ChatGPT designs structure
• All understand the same rules!

Everything is tracked automatically:

• Who did what
• When it was done
• Which files depend on each other

npm install -g ai-naming-standard-mcp

Just copy this into your Claude or Cursor settings:

{ "mcpServers": { "ai-naming-standard": { "command": "node", "args": ["path/to/ai-naming-standard-mcp/src/index.js"] } } }

Tell your AI in plain language:

• "Create a user dashboard page"
• "Add email verification API"
• "Make a product database table"

That's it! 🎉

You say: "I need a shopping cart page"

AI creates:

015_FE_Cart-Shopping_R_Page_PROD.jsx 

You can tell it means:

• 015 - File number (easy to find)
• FE - Frontend (it's a webpage)
• Cart-Shopping - Shopping cart feature
• R - Read/Display (shows information)
• Page - It's a page
• PROD - For production (real site)

Before:

• John makes: login_page.jsx
• Sarah makes: LoginPage.jsx
• Mike makes: user-login-component.jsx
• 😵 Everyone confused!

After:

• Everyone makes: 001_FE_User-Login_C_Page_PROD.jsx
• ✨ Perfect consistency!

All features work in your language:

Don't worry - you don't need to memorize this!
Just tell AI what you want, and it creates the correct name.

But if you're curious, here's how it works:

[Number]_[Where]_[What]-[Detail]_[Action]_[Type]_[Environment] 

Examples:

Where (Layer):

• FE = Frontend (what users see)
• BE = Backend (server logic)
• DB = Database (data storage)
• API = API (connects things)

Action:

• C = Create (making new)
• R = Read (showing)
• U = Update (changing)
• D = Delete (removing)
• X = Execute (processing)

📧 Email: omskykhal@gmail.com

We welcome:

• Bug reports
• Feature suggestions
• Translations
• Documentation improvements

How to contribute:

1. Visit our GitHub: https://github.com/ai-naming-standard/mcp
2. Open an Issue or Pull Request
3. We'll review and respond quickly!

MIT License - Free to use for everyone!

Copyright (c) 2025 AI Naming Standard Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software. 

✨ Save Time: No more thinking about file names
✨ Less Confusion: Everyone uses the same system
✨ Better AI Help: AI understands your project structure
✨ Easy Teamwork: Clear rules for everyone
✨ Professional: Your project looks organized and clean