Are you getting tired of doing BrickColor.new() and trying to remember what the BrickColor name you want to use is? (or perhaps you find yourself doing Color3.new repetitively)
Well, me too and I have complied a list of all the BrickColors into a simple Dictionary
It is pretty straight forward you just access the table and assign a Color3 value of your choice. These are not a BrickColor value so beware, you can learn more about BrickColors in the links below, they are pretty useful.
You can just do BrickColor.Color if you want the Color3
I’m aware that’s not the point of this module
also having to do BrickColor.Color is rather tedious why not cut the extra step?
local Color = BrickColor.new("Light stone grey").Color
local Color = Colors["Light stone grey"]
I personally don’t think this module poses any significant use as you’re able to do exactly what @dispeller said and just do .Color
For your argument about it being shorter… if it’s that important to you just make a single function to replace your entire module like so:
local function Colors(BColorName)
return BrickColor.new(BColorName).Color
end
--- Call function
local Color = Colors("Light stone grey")
Additionally, if Roblox were to add more brick colors in the future, your module would automatically be considered deprecated. To circumvent that issue, just use the function posted above.
I don’t think this really meets the requirement to be a community resource as you’ve essentially just re-invented an API that already exists.
I commend your effort though. 
I agree that the module is very simple, do you have any suggestions where I should move it?
I prefer to have intellisense and rather not make any typos, this isn’t an issue inside of Roblox Studio but I use VS Code, there isn’t any autocompletion for BrickColor
I would recommend moving it to #help-and-feedback:cool-creations and changing the main intention of your post to be that it triggers intellisense in VS code.
that’s not all the brickcolors, you forgot all the hidden ones