This serves as a quick reference and showcase of GitHub Flavored Markdown. For more complete info, see John Gruber's original spec and the Github-flavored Markdown info page.
Discover gists
| Feature | Manual Trend Analysis | DeeVid Viral Studio |
|---|---|---|
| Hook breakdown | Done manually | AI-generated |
| Scene structure | Time-consuming | Automatically analyzed |
| Visual style notes | Requires experience | Extracted by AI |
| Prompt creation | Manual | AI-assisted |
| Customization | Fully manual | Characters, products, locations, backgrounds, clothing, and more |
| Best for | Experienced creators | Creators, brands, agencies, and beginners |
- Step 1 - Test Case Generation
Generate 5 functinal Test cases for the url https://medistack.vercel.app/. Atleast one test case should be for appointment confirmation workflow. Once the test cases are generated, add them to the Test Case repository. Use test.automation@medistack.com and password as testingisfun99 for exploring the application
- Step 2 - Create a new Project
MediStack E2E Testsand add a folder inside the project in BrowserStack TM and add the test cases created.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
A practical guide to running multiple Qwen3 models through a single llama-server instance using model routing. Covers embedding, reranking, and chat/vision models.
Tested on Windows with RTX 3090 (24GB VRAM), llama-server build from llama.cpp master branch. Last updated: 2025-03-09.
| name | code-review-turbo | ||||
|---|---|---|---|---|---|
| description | Run a triple-agent code review on the current branch's PR. Waits for Cursor Bugbot, runs a Claude sub-agent and Codex in parallel, then cross-references all findings to filter out hallucinations. Use when you want a thorough, multi-perspective code review before merging. | ||||
| metadata |
|
||||
| allowed-tools | Bash(gh:*) Bash(codex:*) Bash(cat:*) Bash(tee:*) Bash(sleep:*) Agent Read Grep Glob Write(/tmp/*) |
Note
If you want to use Wayland in WSLg in a simpler setup, you can try the WSLg (Wayland) tutorial.
In this tutorial, we will setup GUI in WSL2. No additional software outside WSL (like VcXsrv or GWSL) is required. You will find this tutorial very similar to the one that replaces Xorg with Xvnc. Indeed, it's pretty much the same tutorial, with some few changes.
The key component we need to install is the desktop metapackage you want (GNOME, KDE, Xfce, Budgie, etc), and after that, replace the default Xorg by a script that calls Xwayland instead.
For this setup, I will use Ubuntu 24.04, and install GNOME Desktop. Unfortunately older versions of Ubuntu lack some fundamental things, so we cannot reproduce it in older versions (at least not fully). Since the key components aren't bound to Ubuntu or GNOME, you can use your favorite distro and GUI. Check the [Sample screenshot
| routes": { | |
| "activityDecorateLive": { | |
| "host": "https://uts-api.itunes.apple.com/", | |
| "needsLocation": true, | |
| "needsMescal": false, | |
| "path": "/uts/v2/activity/decorate/live", | |
| "requiredParamsType": "Default", | |
| "url": "https://uts-api.itunes.apple.com/uts/v2/activity/decorate/live" | |
| }, | |
| "activityDecorateLiveEbs": { |