Add VSCode setting files

[kyasbal]

Adds VSCode setting files for developer to work on KHI without crafting them.

[gemini-code-assist]

Summary of Changes

Hello @kyasbal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the developer experience by integrating pre-configured VSCode settings directly into the repository. This change aims to reduce the initial setup friction for new contributors, providing ready-to-use launch configurations for debugging the Go backend, running the Angular frontend, Storybook, and Karma tests, thereby accelerating the onboarding process and ensuring a consistent development environment.

Highlights

• Standardized VSCode Configuration: Added comprehensive VSCode configuration files (launch.json, settings.json, tasks.json) to provide a consistent and ready-to-use development environment for all contributors.
• Streamlined Developer Onboarding: Updated project documentation (README.ja.md, development-guide.md) to reflect the new VSCode settings and simplified setup/build processes using make setup and make build commands.
• Enhanced Frontend Development Workflow: Introduced new launch configurations for debugging the Go backend, running the Angular frontend, Storybook, and Karma tests directly from VSCode, along with a new watch-karma make target and test script in package.json.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces VSCode setting files (launch.json, settings.json, tasks.json) to streamline the development workflow for contributors using VSCode. The changes include removing .vscode from .gitignore, adding launch configurations for backend and frontend services, defining helper tasks, and setting up workspace-specific editor settings. The documentation in both English and Japanese has been updated to reflect these new, simplified setup instructions. Additionally, a new make target and npm script have been added to support running Karma tests from within VSCode.

The changes are well-structured and significantly improve the developer experience for VSCode users. I have one suggestion regarding a debugger configuration value in launch.json for consideration.