Skip to content

Instantly share code, notes, and snippets.

View jnelken's full-sized avatar
🎶

Jake Nelken jnelken

🎶
View GitHub Profile
@jnelken
jnelken / openclaw-50-day-prompts.md
Created March 9, 2026 04:21 — forked from velvet-shark/openclaw-50-day-prompts.md
OpenClaw after 50 days: all prompts for 20 real workflows (companion to YouTube video)

OpenClaw after 50 days: all prompts

Companion prompts for the video: OpenClaw after 50 days: 20 real workflows (honest review)

These are the actual prompts I use for each use case shown in the video. Copy-paste them into your agent and adjust for your setup. Most will work as-is or the agent will ask you clarifying questions.

Each prompt describes the intent clearly enough that the agent can figure out the implementation details. You don't need to hand-hold it through every step.

My setup: OpenClaw running on a VPS, Discord as primary interface (separate channels per workflow), Obsidian for notes (markdown-first), Coolify for self-hosted services.

@jnelken
jnelken / CLAUDE.md
Created August 21, 2025 15:48
Global CLAUDE.md guidelines for React TypeScript projects

Guidelines for React TypeScript projects

Architecture

  • When creating new projects, use Next.js
  • If a React component file is longer than 150 lines, check if it can be refactored into smaller components. Oftentimes, the JSX can be broken into smaller individual ui components, and the state logic can be extracted into custom hooks.
  • When asked to combine two components into a shared component, avoid If/else statements inside the shared component by passing all unique values as props or boolean flags.
  • In a React project, if you have a choice to use HTML state management, do not use it. Always default to standard React state management instead with controlled inputs.

Component Extraction and Reusability