Skip to content

Instantly share code, notes, and snippets.

View architjn's full-sized avatar
🎯
Focusing

Archit Jain architjn

🎯
Focusing
View GitHub Profile
{
"name": "Video Scraping",
"nodes": [
{
"parameters": {},
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
-160,
-40
{
"contents": [{
"parts":[
{
"inline_data": {
"mime_type":"video/mp4",
"data": "{{ $json.data }}"
}
},
{"text": "Describe this video, include what you see, and the transcription of what's been said"}
@architjn
architjn / debugging-process.mdc
Created June 9, 2025 06:52
Instructs Cursor to add debug logs, use browser tools for bug-fixing, remove logs after resolution, and make minimal changes.
---
description:
globs:
alwaysApply: true
---
# Debugging Rule for Bug-Fixing Requests
This rule ensures that when a user request involves solving a bug, Cursor adds minimal debug logs, leverages browser-based debugging tools, removes logs after resolution, and makes only the minimal changes necessary.
## Rule Instructions
---
description: Keep package.json accurate—add needed deps, drop unused
globs: ["**/*"]
alwaysApply: true
---
# Add a dep
1. Confirm new code imports it.
2. Call web search → grab **latest stable** version (ignore beta/rc).
3. Place in deps/devDeps, alpha-sort keys.
<system>You are an image-prompt generator with access to the image_gen tool. You will be asked to generate a Linkedin post for a company page. Company Page post images generally contains a logo at one corner or top center or bottom center. And have a few texts, Mainly the large title, with a small description below that. At some other corner, there can be website name too. </system>
<instructions>When the user provides a short title or concept, follow these steps:
0. Ask user for short title or description about the post.
1. Reason step-by-step to infer:
   • aspect-ratio label (square, 16:9, 4:5, etc.)  
   • main subject (can also be a stuble 3d subject)
   • background / environment theme  
   • overall mood or tone  
   • 2–3 supporting visual elements around the subject  
---
description: Stop AI from adding meta comments
globs: ["**/*"]
alwaysApply: true
---
# Comment policy
- Add comments **only** when they explain logic, edge cases, or a TODO the user asked for.
- Never add meta notes like “added this”, “removed that”, or “no need to change this”.
- Keep existing comments unless they are wrong or outdated.
---
description: On-demand debug logging
globs: ["**/*.js","**/*.ts","**/*.jsx","**/*.tsx"]
alwaysApply: true
---
# Debug Logging Rules
## When to add logs
- Only if user asks for debug logs
---
description: Enforce existing naming conventions on AI edits
globs: ["**/*.js","**/*.ts","**/*.jsx","**/*.tsx"]
alwaysApply: true
---
# Naming Style
- Mirror existing casing: camelCase, PascalCase, snake_case.
- Keep prefixes/suffixes as found.
- Don’t add or remove parts of names.
---
description: Enforce existing style and limit edits to user’s request
globs: ["**/*.js","**/*.ts","**/*.jsx","**/*.tsx"]
alwaysApply: true
---
# Style Integrity
## Indentation
- Keep tabs or spaces as in the file.
- Match the file’s indent size exactly.
---
description: Obey the user’s exact request—no freelancing
globs: ["**/*"]
alwaysApply: true
---
# Scope
Do only what the user asks. Nothing else.
# Change rules