grayhat.studio valid
Grayhat Blog: Creating an MVP for an unofficial v0.dev VS Code Extension clone
The race to generate React UI code in VSCode ensues.
- Authority
- 48 reach 0 · trust 10 · quality 23 · freshness 15
- Tier
- listed
- llms.txt
- https://grayhat.studio/blog/creating-an-mvp-for-an-unofficial-v0-dev-vs-code-extension-clone/llms.txt
- llms-full.txt
- https://grayhat.studio/blog/creating-an-mvp-for-an-unofficial-v0-dev-vs-code-extension-clone/llms-full.txt
- Sections
- 8
- Links
- 5
- Size
- 8025 bytes
- Registered
- 2023-12-25
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-23T05:47:15.271Z
- Last checked
- 2026-10-23T05:47:22.884Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T05:47:15.278Z. Cached copy · Source on grayhat.studio
# Grayhat Blog: Creating an MVP for an unofficial v0.dev VS Code Extension clone
> The race to generate React UI code in VSCode ensues.
## Page
- [Creating an MVP for an unofficial v0.dev VS Code Extension clone](https://grayhat.studio/blog/creating-an-mvp-for-an-unofficial-v0-dev-vs-code-extension-clone)
- [Root LLM Context](https://grayhat.studio/blog/llms.txt)
- [Post Full LLM Context](https://grayhat.studio/blog/creating-an-mvp-for-an-unofficial-v0-dev-vs-code-extension-clone/llms-full.txt)
- [Post API](https://grayhat.studio/blog/api/public/v1/posts/creating-an-mvp-for-an-unofficial-v0-dev-vs-code-extension-clone)
- [Sitemap](https://grayhat.studio/blog/sitemap.xml)
## Post Metadata
- Slug: `creating-an-mvp-for-an-unofficial-v0-dev-vs-code-extension-clone`
- Published: 2024-08-19T15:30:04.000+05:00
- Updated: 2024-08-19T16:46:07.000+05:00
- Reading time: 5 min
- Tags: Developer Tools, Artificial Intelligence, Development, Codegen, Copilot, GitOps, AI, Open Source
- Authors: Asher Siddique, Muhammad Usama Rashid
- Visibility: public
## Post Content
**This extension is in no way affiliated with v0.dev or Vercel. It's just a dummy pet project we made to test out code generation in VSCode. We do aim on pursuing similar goals, but definitely with a different name 🥸Before we started working on this extension, another team with Grayhat was already working on an earlier version of the idea. The initial approach was to create a simple website embedded within VS Code using an iframe. **v0.dev** served as the core interface where users could input prompts and receive generated React component code. However, the iframe approach quickly ran into issues, as the website was eventually blocked by various security measures within VS Code. This made us rethink our strategy and led to the decision to build a native VS Code extension without relying on any website outside of VS Code.
## **Planning**
To streamline things, we started with creating a detailed game plan that outlined the core functionalities we aimed to implement in the extension's proof of concept. These core features included:
- An input field for user prompts
- Image upload functionality
- Handling API calls to the hosted LLM and processing responses
- Displaying the generated React components as text in a UI element
Alongside these features, we established a timeline with specific delivery dates to keep the project on track.
Once the game plan was set, our next step was to familiarize ourselves with the documentation on how extensions work in VS Code. This research was crucial in helping us understand the necessary APIs and the architecture of a typical extension. With this knowledge in hand, we proceeded to set up a basic extension, similar to a "Hello World" page in web development. This initial setup served as the framework on which we built the entire extension.
## **Researching the docs**
After briefly exploring the documentation, we began searching for and testing the appro
…Machine-readable: GET /v1/resolve?q=grayhat.studio · GET /v1/domain/grayhat.studio · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage grayhat.studio, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for grayhat.studio:
1. POST https://agentwebmap.com/v1/sites/grayhat.studio/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://grayhat.studio/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/grayhat.studio/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/grayhat.studio).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.