docs(CONTRIBUTING.md) #2109

Author: justinmk3

CONTRIBUTING.md

@@ -1,7 +1,7 @@
-# Contributing Guidelines
+# Contributing to AWS Toolkit for VS Code
 
-Thank you for your interest in contributing to our project. We greatly value
-feedback and contributions from our community!
+Thanks for taking the time to help us. We greatly value feedback and
+contributions from our community!
 
 Reviewing this document will maximize your success in working with the
 codebase and sending pull requests.
@@ -74,9 +74,12 @@ You can also use these NPM tasks (see `npm run` for the full list):
 
 ## Develop
 
-### Code guidelines
+### Guidelines
 
-See [CODE_GUIDELINES.md](./docs/CODE_GUIDELINES.md) for coding conventions.
+- Project patterns and practices: [CODE_GUIDELINES.md](./docs/CODE_GUIDELINES.md)
+- [VS Code Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines)
+- [VS Code API Documentation](https://code.visualstudio.com/api/references/vscode-api)
+- [VS Code Extension Capabilities](https://code.visualstudio.com/api/extension-capabilities/common-capabilities)
 
 ### Technical notes
 

docs/CODE_GUIDELINES.md

@@ -5,6 +5,13 @@ Toolkit for VSCode. It provides answers to common questions, decisions, UX and
 project consistency, questions of style and code structure, and anything else
 that cannot be enforced by a `lint` build-task.
 
+## UI
+
+- Where possible, follow the conventions of the [VSCode User Interface](https://code.visualstudio.com/docs/getstarted/userinterface)
+  instead of inventing new conventions.
+- Convention: provide global editor commands as an alternative to browsing items in the Explorer.
+    - Instead of needing to visit service _Foo_ in the Explorer to _View_ its items, consider also providing a `AWS: Foo: View Item` command.
+
 ## Naming
 
 Naming is one of the central opportunities for you as a human to add value to