Neon

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Open source local audio stem separator : split any song into vocals, drums, bass, guitar and piano

Hi everybody, StemDeck creator here. I wanted to share something I built with Claude Code and Claude that might be useful to some of you. StemDeck is an open source, local audio stem separator. You drop in an MP3 or WAV, or paste a YouTube link for audio you have the rights to process, and it splits the track into six stems: vocals, drums, bass, guitar, piano, and other. The whole thing runs on your machine using Demucs, so nothing gets uploaded anywhere. Once the separation is done you get a DAW-style mixer with per-stem faders, mute, solo, waveform view, loop regions, and mix export. No account, no subscription, no usage limits, completely free. You can grab the native client for macOS or Windows, or clone the repo and self-host it if you want full control. Claude has been a massive help with a significant chunk of this: writing and reviewing code, setting up and managing the Discord server, drafting release announcements, and putting together the website. As a father with limited time (and too many hobbies), having Claude handle the community and content side has meant I can stay focused on actually shipping, which otherwise it would take an eternity to put this together :) GitHub: https://github.com/stemdeckapp/stemdeck submitted by /u/JustDoodlingAround [link] [comments]

Introducing AI finetuner, Source available and free Claude skill to fine tune your vibe coded UI with live preview

​ Fine-tuning UI with AI right now: "Make the shadow softer." "Stronger." "No, less." "Go back." "A bit more." 17 messages later, you've spent more tokens than the shadow is soft. I built something that breaks the loop. AI Fine-Tuner — free, source-available — a plugin that teaches AI coding agents to stop chatting and hand you an actual GUI for your component. Sliders. Color pickers. Live preview. Drag until it feels right. The AI agent automatically opens the editor window for you on your default browser once ready. Then the magic part: you click one button. The tuner outputs a structured handoff with your exact tuned values mapped to their targets in your code. Paste it back to your AI — it reads the mapping, opens your source, and applies everything precisely. No CSS guesswork, no syntax translation, nothing for you to interpret. Why it's not just another slider playground: Bespoke controls — no raw CSS names Sliders are named in plain English: "Glow softness", "Card lift", "Hover intensity" — not "box-shadow-spread-radius" A single slider can drive multiple properties at once. The AI doesn't expose CSS to you; it wires meaningful, human-named controls to your element. 3 prebuilt editor templates — guaranteed polish, every time The AI doesn't design the editor. It picks one of three prebuilt templates and fills in your component: - single.html — 1 control, full-screen preview - small.html — 2-4 controls, preview + bottom grid - full.html — 5+ controls, grouped sidebar + preview Slider chrome, color picker, layout, animations, infinite canvas with zoom/pan — all pre-built. No "the AI generated an ugly panel" failure mode. And once it's open, you tune in pure browser JS — no AI sitting in the loop per drag. Color picker + hex paste Pick it or paste it. Done. Animation tuning Not just static styles — timing, easing, keyframes too. Works on ANY platform — language-agnostic Flutter, SwiftUI, React Native, Tailwind, vanilla CSS, SVG — the AI is meta-prompted to rebuild your component in HTML/CSS for the tuning preview (the web is where sliders work). When you copy back, the AI applies the tuned values to your real source, in your component's original framework. You never leave Flutter to tune Flutter. Infinite canvas + multiple previews Drop 5 variations side-by-side and tune them together. The template is a starting point — experiment freely. Contextually named presets Every tuner ships with thoughtful presets ("Subtle," "Bold," "Brutalist," whatever fits) so you can ping-pong through variations in one click. No new software It's a skill, not an app. Full install guides for Claude Code. One command and you're in. Website and Live demos: https://muhamadjawdatsalemalakoum.github.io/aifinetuner Free. Source-available. #AI #DeveloperTools #ClaudeCode #BuildInPublic #OpenSource #AITools #FrontendDev submitted by /u/keonakoum [link] [comments]

Please give us custom themes!!

Hi Claude team, I'd like to request expanded theme/appearance customization, specifically for the Claude desktop app. Right now, Settings → Appearance only offers Light, Match System, and Dark. The default dark mode is fine, but I'd really enjoy more vibrant or personalized options — for example, accent color choices, higher-contrast variants, or a few curated themes (midnight, neon, warm, etc.). What prompted this: on the web version, I was able to install a browser extension (Stylus) and apply a community-made dark/vibrant theme to claude.ai, which made the experience much nicer for long sessions. But that approach doesn't carry over to the desktop app since extensions can't run inside it. Since I use the desktop app most of the time, the customization is effectively unavailable to me. A few specific things that would make a big difference: • A handful of built-in theme presets beyond Light/Dark • Adjustable accent color • Optional support for user-supplied CSS or imported themes (similar to VS Code or Discord) Appreciate the work you all do — Claude is great, and a bit of visual personalization would make it feel even more like home. Thanks! submitted by /u/Gr3yGryffin [link] [comments]

25 Years of Diaries + ChatGPT + Suno: I turned my life into a concept album

ChatGPT cenerated the album cover I used ChatGPT as a creative development partner to analyze 25 years of personal diary material, identify recurring emotional themes, build a concept album structure, draft/revise lyrics, and create Suno style prompts. The result was a personal, non-commercial concept album called Beautiful Ugly Light. I’m sharing the process because I’m still thinking through both the creative value and the ethical discomfort of AI-generated music. Full disclosure - I had ChatGPT help me organize and ghostwrite this post based on our process. What the album is Beautiful Ugly Light is a personal concept album built from my diary material. It is about shame, memory, self-recognition, emotional survival, work exhaustion, aging, loneliness, and the uncomfortable process of trying to change. It is not fictional, exactly, but it is also not a direct transcription of my diaries. It is more like an emotional translation of them. The songs came from real patterns in my life, but they were shaped into something more structured than the original writing. The album became about the strange beauty of seeing the ugly parts clearly. Why I made it I made it because I wanted to hear my life from a distance. Journaling has always been one of the main ways I process my life, but when I write, I am usually inside the feeling. I am in the middle of the shame, the anxiety, the anger, the hope, the regret, the self-questioning. This project let me experience those same feelings from the outside. There was something surprisingly powerful about hearing parts of my inner life turned into songs. Not because the songs “fixed” anything, but because they gave shape to things that had mostly lived as text. It made certain emotions feel less scattered. Less abstract. More visible. It felt less like “AI made me an album” and more like AI helped me build a mirror I could actually stand far enough away from to look into. How ChatGPT helped analyze the diaries ChatGPT helped me look across the diary entries for recurring themes, emotional patterns, repeated images, conflicts, and shifts in how I saw myself over time. When I use ChatGPT I rarely "prompt craft" but engage in a conversational back-and-forth dialogue. I extensively engage with ChatGPT when it comes to my diaries; I often microdose and write, and then afterward engage with ChatGPT in assessing my writing. I do not use ChatGPT to supplant my regular therapy & trauma therapy work. It helped identify what kept coming back: shame, loneliness, family dynamics, friendship conflict, work stress, body image, emotional avoidance, longing for transformation, and the gap between having insight and actually changing behavior. That last part became important. A lot of my writing is not just about pain. It is about noticing the pain, naming it, analyzing it, understanding it — and then still struggling to change. That tension became one of the main emotional engines of the album. How the album concept formed The title Beautiful Ugly Light came from the contradiction I kept feeling in my diaries. While driving home I became curious it and then about having ChatGPT build an entire album based off my diaries and to see if/how it would pick up on the tension I felt. So I prompted ChatGPT: Based on my diaries, I want to make a music album, but keeping identifiable details about myself and others out of the lyrics. What do you recommend as a tracklist that would tell the story of my life and who I am, and what genre of music do you think is best based on the material? Yes. Based on the material in your diaries, I would not make this a pure club album and I would not make it straight pop-rock either. The best fit is a theatrical synth-pop / dance-rock concept album with some dark club energy, some heart-on-sleeve ballads, and a few spoken-word or half-sung interludes. That fits the actual texture of your diaries much better: you are reflective, emotionally intense, often isolated, highly observant, drawn to beauty, stuck between routine and reinvention, and always narrating your life like it has symbolic meaning. Your diaries repeatedly show loneliness, social anxiety, difficult friendships, work pressure, travel/daydreaming, shame around self-expression, and then a later turn toward therapy, microdosing, transformation, and creative awakening. So the album should sound like: verse: private diary, interior monologue chorus: big release, hooky, danceable, emotionally direct bridge: theatrical turn, almost like a character confession That gives you the “musical” feeling without becoming corny. Best genre Primary genre: theatrical synth-pop / pop-rock Secondary colors: dark disco, new wave, club ballad, glam-pop Why this works: Your writing is not casual. It is dramatic, image-rich, self-analyzing, and often cinematic. You also return again and again to identity, reinvention, invisibility, desire, shame, and transformation. That is perfect for a concept album wit

GOT BORED OF BLOCKED GAMES SO MADE MY OWN WITH CLAUDE

Long story short, in class I'm always searching the web for new websites and games and even when I do find one it's always full of lag and ads. So, I decided to vibe code my own website. I used Claude and spent my entire weekend working on this. Even though AI is doing all the coding (and I'm very thankful), it still took a lot of work to do testing and describe exactly what I wanted. Moving on, I'm now able to play games in class again. It's lowkey an enjoyable video game and it's very addicting. There's a normal mode and a hardcore mode. Basically, you're this blue player and you can move left, right, and dash to avoid this neon blocks falling from the sky. Hence the name: NEON DODGE. There's different types of neon blocks that fall and different waves. I also added two bosses. It's a full game to explore and super fun. A full good runthrough takes about 10 minutes for the normal mode. Hardcore mode is much harder. I haven't been able to clear it yet but it's definitely possible. I was wondering if yall know what to add to games like this. Do people want basic video games or a full long games with multiple bosses? So far, there are no checkpoints and the game isn't very long. If you guys have any recommendations let me know. I'm not tryna advertise the game, just wanna know what video gamers find interesting in stuff like this to make my experience better. I did upload it to a website if any of yall wanted to try it out. neondodgegame.lovable.app submitted by /u/sunnyorygun [link] [comments]

I created awesome-claude-design using Claude code: DESIGN.md prompts by aesthetic families for Claude Design

Claude Design launched 48 hours ago, and everyone’s cloning the same 60–70 brand DESIGN .md files from a single catalog. I wanted something that matches how designers actually pick: by visual family, not industry. So I put together awesome-claude-design, a meta-resource for Claude Design that groups DESIGN .md files by aesthetic family (editorial minimalism, terminal-core, warm editorial, data-dense pro, cinematic dark, playful color, glass/soft-futurism, neon brutalist, cult/indie), plus remix recipes, prompt packs with full I/O examples, and an anti-slop kit pulled from Anthropic’s frontend aesthetics cookbook. You’ll also find: A launch-week timeline (Opus 4.7 + Claude Design, Figma’s 4.26% close, Reddit threads, X signal) Official Anthropic resources (launch post, claude .ai/design, prompt library, cookbooks) Video teardowns, community hype and pushback, and related OSS projects like SuperDesign and Claude skills repos. Repo: https://github.com/rohitg00/awesome-claude-design This post and the repo were created with Claude for the Claude community, using Claude Design and Claude Code as the primary tools. Curious what other Claude power users want added next: more DESIGN.md families, deeper workflows, or tighter SkillKit integrations? Built end‑to‑end with Claude (Claude Design + Claude Code) for the r/ClaudeAI community. submitted by /u/SeveralSeat2176 [link] [comments]

I built a CLI tool that lets Claude Code deploy a full backend in minutes

Hey, I'm the developer of Teenybase. It's a CLI that lets Claude Code / Codex spin up a full backend for you: database, REST API, user auth, file uploads, admin panel, API docs, deploy. Why I built it I have a ton of vibe coded projects and setting up a backend for each is a pain. I'd typically get a VPS from OVHCloud or Hetzner for the API layer, use Supabase or Neon as the database, and WorkOS or Clerk for auth. Each one has its own dashboard, its own billing, its own config. Then there's SSHing into the VPS, managing migrations with something like Alembic, gluing it all together. Too much context switching across services that Claude Code can't even reach. That's the problem Teenybase solves: your entire backend defined in a single file that Claude Code can read, write, and deploy. How it works Install the CLI: npm i -g teenybase Paste this into Claude Code: "Use teeny cli (try teeny docs) to add a backend to this project." Claude reads the docs in the terminal, writes your config, generates migrations, and deploys. One config file, one session, live API. Runs on Cloudflare Workers + D1 + R2. You get up to 5 free projects under a new teeny account created via the terminal: teeny register Each free project gets 1M req/mo, 100 MB database, and 1 GB file storage. https://teenybase.com Happy to answer questions and feeback is welcome! submitted by /u/invocation02 [link] [comments]

I built an AI content engine that turns one piece of content into posts for 9 platforms — fully automated with n8n

What it does: You give it any input — a blog URL, a YouTube video, raw text, or just a topic — and it generates optimized posts for 9 platforms at once: Instagram, Twitter/X, LinkedIn, Facebook, TikTok, Reddit, Pinterest, Twitter threads, and email newsletters. Each output is tailored to the platform (hashtags for IG, hooks for TikTok, professional tone for LinkedIn, etc.). It also auto-generates images for visual platforms like Instagram, Facebook, and Pinterest,using AI. Other features: - Topic Research — scans Google, Reddit, YouTube, and news sources, then uses an LLM to identify trending subtopics before generating content - Auto-Discover — if you don't even have a topic, it searches what's trending right now (optionally filtered by niche) and picks the hottest one - Cinematic Ad — upload any photo, pick a style (cinematic, luxury, neon, retro, minimal, natural), and Gemini transforms it into a professional-looking ad - Multi-LLM support — works with Mistral, Groq, OpenAI, Anthropic, and Gemini - History — every generation is saved, exportable as CSV The n8n automation (this is where it gets fun): I connected the whole thing to an n8n workflow so it runs on autopilot: 1. Schedule Trigger — fires daily (or whatever frequency) 2. Google Sheets — reads a row with a topic (or "auto" to let AI pick a trending topic) 3. HTTP Request — hits my /api/auto-generate endpoint, which auto-detects the input type (URL, YouTube link, topic, or "auto") and generates everything 4. Code node — parses the response and extracts each platform's content 5. Google Drive — uploads generated images 6. Update Sheets — marks the row as done with status and links The API handles niche filtering too — so if my sheet says the topic is "auto" and the niche column says "AI", it'll specifically find trending AI topics instead of random viral stuff. Error handling: HTTP Request has retry on fail (2 retries), error outputs route to a separate branch that marks the sheet row as "failed" with the error message, and a global error workflow emails me if anything breaks. Tech stack: - FastAPI backend, vanilla JS frontend - Hosted on Railway - Google Gemini for image generation and cinematic ads - HuggingFace FLUX.1 for platform images - SerpAPI + Reddit + YouTube + NewsAPI for research - SQLite for history - n8n for workflow automation It's not perfect yet — rate limits on free tiers are real — but it's been saving me hours every week. Happy to answer questions. https://preview.redd.it/f8d3ogk3nktg1.png?width=888&format=png&auto=webp&s=dcd3d5e90facd54314f40e799b32cab979dae4bf https://preview.redd.it/j8zl07llmktg1.png?width=946&format=png&auto=webp&s=5c78c12a223d6357cccaed59371e97d5fe4787f5 https://preview.redd.it/5cjas6hkmktg1.png?width=891&format=png&auto=webp&s=288c6964061f531af63fb9717652bececfb63072 https://preview.redd.it/k7e89belmktg1.png?width=1057&format=png&auto=webp&s=8b6cb15cfa267d90a697ba03aed848166976d921 https://preview.redd.it/3w3l70tlmktg1.png?width=1794&format=png&auto=webp&s=6de10434f588b1bf16ae02f542afd770eaa23c3f https://preview.redd.it/a40rh1canktg1.png?width=1920&format=png&auto=webp&s=1d2414c7e653a5f01f12a21a43e69bd4fb4b99ed submitted by /u/emprendedorjoven [link] [comments]

I made a game where you center a div. The threshold is 0.0001px. Nobody has ever won.

I built "Can You Center This Div?" for the DEV April Fools 2026 challenge. https://preview.redd.it/x28bvuc80etg1.png?width=3840&format=png&auto=webp&s=b15647824686c7739dee573b480804281e6976b3 You drag a div to the center of the screen. That's it. The catch: the success threshold is 0.0001 pixels, roughly 5,000x smaller than a single pixel on a Retina display. The global success counter reads 0. It has always read 0. The whole thing is wrapped in a JARVIS-style HUD with real-time deviation readouts, a logarithmic precision meter, a global leaderboard, radar sweep with live player blips, and an "Earth Scale" that translates your pixel miss to real-world distance. Miss by 3px? That's 49,000km on Earth. Congrats, you missed by more than the circumference. Other features: - 2,500+ quotes based on how far off you are - Share cards for every platform (1080x1080 PNG) - Hidden 418 teapot easter egg (3D particle cloud with steam) - Anti-cheat that rejects suspiciously close submissions with HTTP 418 - Light and dark mode - Open source Stack: Next.js 16, React 19, TypeScript, Neon Postgres (serverless), pure CSS for 90% of the visuals. No animation libraries. Game logic is a single custom hook. GitHub: github.com/raxxostudios/center-this-div Try it: center-this-div.vercel.app The anti-value proposition: this app takes the most solved problem in CSS and makes it unsolvable. Happy April Fools. The joke is your CSS skills. submitted by /u/norm_cgi [link] [comments]

Switched from MCPs to CLIs for Claude Code and honestly never going back

I went pretty hard on MCPs at first. Set up a bunch of them, thought I was doing things “the right way.” But after actually using them for a bit… it just got frustrating. Claude would mess up parameters, auth would randomly break, stuff would time out. And everything felt slower than it should be. Once I started using CLIs. Turns out Claude is genuinely excellent with them. Makes sense, it's been trained on years of shell scripts, docs, Stack Overflow answers, GitHub issues. It knows the flags, it knows the edge cases, it composes commands in ways that would take me 20 minutes to figure out. With MCPs I felt like I was constraining it. With CLIs I jactually just get out of the way. Here's what I'm actually running day to day: gh (GitHub CLI) — PRs, issues, code search, all of it. --json flag with --jq for precise output. Claude chains these beautifully. Create issue → assign → open PR → request review, etc. Ripgrep - Fast code search across large repos. Way better than grep. Claude uses it constantly to find symbols, trace usage, and navigate unfamiliar codebases. composio — Universal CLI for connecting agents to numerous tools with managed auth. Lets you access APIs, MCPs, and integrations from one interface without wiring everything yourself. stripe — Webhook testing, event triggering, log tailing. --output json makes it agent-friendly. Saved me from having to babysit payment flows manually. supabase — Local dev, DB management, edge functions. Claude knows this one really well. supabase start + a few db commands and your whole local environment is up. vercel — Deploy, env vars, domain management. Token-based auth means no browser dance. Claude just runs vercel --token $TOKEN and it works. sentry-cli — Release management, source maps, log tailing. --format json throughout. I use this for Claude to diagnose errors without me copy-pasting stack traces. neon — Postgres branch management from terminal. Underrated one. Claude can spin up a branch, test a migration, and tear it down. Huge for not wrecking prod. I've been putting together a list of CLIs that actually work well with Claude Code (structured output, non-interactive mode, API key auth, the things that matter for agents) Would love to know any other clis that you've been using in your daily workflows, or if you've built any personal tools. I will add it here. I’ve been putting together a longer list here with install + auth notes if that’s useful: https://github.com/ComposioHQ/awesome-agent-clis submitted by /u/geekeek123 [link] [comments]

I built MAGI — a Claude Code plugin that spawns 3 adversarial AI agents (inspired by Evangelion) to review your code, designs, and decisions

Hey everyone, I built a Claude Code plugin called MAGI that brings multi-perspective analysis to your workflow. Instead of getting a single opinion from Claude, MAGI launches three independent sub-agents in parallel — each analyzing the same problem through a completely different lens — then synthesizes their verdicts via weighted majority vote. The concept comes from Neon Genesis Evangelion. In the anime, NERV operates three supercomputers called the MAGI (Melchior, Balthasar, Caspar), each containing a copy of their creator's personality filtered through a different aspect of her identity. Decisions require 2-of-3 consensus. I adapted that architecture for software engineering. The Three Agents Agent Role What it focuses on Melchior (Scientist) Technical rigor Correctness, algorithmic efficiency, type safety, test coverage Balthasar (Pragmatist) Practicality Readability, maintainability, team impact, time-to-ship, reversibility Caspar (Critic) Adversarial red-team Edge cases, security holes, failure modes, hidden assumptions, scaling cliffs Each agent analyzes independently (no agent sees the others' output), produces a structured JSON verdict with findings sorted by severity, and the synthesis engine computes a weighted consensus. How voting works Verdicts are weighted: approve = +1, conditional = +0.5, reject = -1. The score determines the consensus: STRONG GO — All three approve GO WITH CAVEATS — Majority approves but conditions exist HOLD — Majority rejects STRONG NO-GO — All three reject The key insight: disagreement between agents is a feature, not a failure. When Melchior approves but Caspar rejects, you've surfaced a genuine tension between correctness and risk. That's exactly the kind of thing you want to catch before shipping. Three modes code-review — Reviews code or diffs with line-specific findings design — Evaluates architecture decisions, migration plans, trade-offs analysis — General problem analysis ("should we use Redis or Postgres for this?") Example output +==================================================+ | MAGI SYSTEM -- VERDICT | +==================================================+ | Melchior (Scientist): APPROVE (90%) | | Balthasar (Pragmatist): CONDITIONAL (85%) | | Caspar (Critic): REJECT (78%) | +==================================================+ | CONSENSUS: GO WITH CAVEATS | +==================================================+ ## Key Findings [!!!] [CRITICAL] SQL injection in query builder (from melchior, caspar) [!!] [WARNING] Missing retry logic for API calls (from balthasar) [i] [INFO] Consider adding request timeout (from caspar) The report includes the full dissenting opinion (Caspar's argument against), conditions for approval, and specific recommended actions from each agent. Technical details Agents run in parallel via asyncio + claude -p — total time is the slowest agent, not the sum 109 tests passing (pytest), linted with ruff, type-checked with mypy Degraded mode: if one agent fails, synthesis continues with 2/3 Fallback mode: works without claude -p by simulating perspectives sequentially Complexity gate: trivial questions skip the full 3-agent system Python 3.9+, dual-licensed MIT/Apache-2.0 Install claude --plugin-dir /path/to/magi Or symlink for auto-discovery: mkdir -p .claude/skills ln -s ../../skills/magi .claude/skills/magi GitHub: https://github.com/BolivarTech/magi Full technical documentation (including the Evangelion-to-software mapping) is in docs/MAGI-System-Documentation.md. I'd love to hear feedback. If you try it and the three agents unanimously approve your code on the first try... your code is either perfect or Caspar's prompt needs tuning. submitted by /u/jbolivarg [link] [comments]

Built a voice dictation app entirely with Claude Code. 4 months in, 326 stars.

VoiceFlow runs Whisper locally for voice dictation. Hold a hotkey, speak, text shows up at your cursor. No cloud, no accounts. I built it with Claude Code and the repo has a CLAUDE.md documenting what was AI-assisted. Some of you might remember the first version I posted here in December. It was Windows-only, kind of rough, and I was mostly using it to dump context into Claude faster. Since then it has been 4 months, 10 releases, and 326 GitHub stars. It runs on Linux now too. The Linux port took about 3 days with Opus 4.6. Claude wrote the evdev hotkey capture code and I had never touched evdev before, worked on the first try. Same with AppImage packaging and CUDA library probing, stuff I had no experience with and it just handled it. PySide6 on Wayland was a different story. Transparency, compositing, multi-monitor detection, Claude kept suggesting fixes that sounded right but did not actually work. I ended up in the Qt docs for those. Clipboard was similar, the wl-copy vs xclip vs pyperclip situation on Linux is a mess and Claude's first pass was a catch-all abstraction that broke on half the setups. I had to be very specific: only wl-copy, only Wayland, fall back to wtype. After 4 months on this project, the thing I keep coming back to is that Claude Code works best when I hand it existing code and say "make this work on a different platform." When the problem is more open-ended it tends to guess confidently and get it wrong. Also set up GitHub Actions this week so both Windows and Linux builds are automated now. Caught a glibc bug from user reports that was breaking the AppImage on Fedora and KDE Neon, fixed it and shipped v1.4.0 within two days. 326 stars, MIT licensed, still free. Demo: https://i.redd.it/59rbyzplc87g1.gif Site: https://get-voice-flow.vercel.app/ Repo: https://github.com/infiniV/VoiceFlow submitted by /u/raww2222 [link] [comments]

How I wired Claude Code into Linear, Discord, and Vercel for a 30-day solo build

I built a full-stack product in 30 days of evenings and weekends. Solo. Using Claude Code as my pair programmer, wired into Linear for ticket tracking and Discord for build notifications. The result: [VGC Team Report](https://pokemonvgcteamreport.com) — a team report builder for competitive Pokemon (VGC). Players paste their teams and get detailed breakdowns with matchup plans, damage calcs, speed tiers, and shareable reports. This post is about the workflow — specifically how I connected Claude Code to Linear and Discord to create a one-person development pipeline that actually ships. ## The Numbers - 274 commits in 30 days - ~42,000 lines of TypeScript - 25 features tracked and shipped via Linear - 66 React components, 41 API routes, 22 custom hooks - Auth (Clerk), database (Neon Postgres), PWA, i18n in 7 languages - Continuously deployed on Vercel ## The Stack - **Next.js 16** (App Router) - **React 19** - **TypeScript** (strict mode) - **Tailwind CSS v4** - **Clerk** for auth - **Neon** for serverless Postgres - **Vercel** for hosting and deploys - **Linear** for ticket tracking - **Discord** for build notifications - **Claude Code** as the AI development partner ## The Workflow: Linear -> Claude -> Discord -> Vercel This is what a typical session looks like: 1. Claude runs `linear_get_in_progress` to check my Linear board for tickets 2. Picks the highest priority ticket (bugs first, always) 3. Reads relevant files and implements the feature or fix 4. Runs `tsc --noEmit && npm run build` — if it fails, Claude fixes the errors 5. Commits with the ticket ID: `VGC-42: Add speed tier chart` 6. Pushes to main 7. Posts a comment on the Linear ticket via GraphQL — commit URL + changed files 8. Moves the ticket to In Review 9. Calls `discord_notify_build` — posts an embed to Discord #builds with the commit, changed file list, and deploy status 10. Vercel auto-deploys from main 11. Moves to the next ticket This isn't hypothetical. I wrote a `linear.sh` bash script with functions that Claude calls directly: - `linear_get_in_progress` — queries Linear GraphQL for In Progress tickets - `linear_move_issue` — moves a ticket to a new state - `linear_comment_with_changes` — posts a comment with the commit link and changed files - `discord_notify_build` — sends a Discord embed with commit info and deploy status Claude calls these via bash. The whole flow — implement, verify, commit, update Linear, notify Discord — happens in one session without me touching any of those systems. ## The CLAUDE.md Operating Manual The key to making this work is a `CLAUDE.md` file at the repo root. Claude reads it at the start of every session. Mine contains: **Git strategy:** - Trunk-based development — push direct to main for routine work - Feature branches only for large or risky changes - `npx tsc --noEmit && npm run build` before every push — non-negotiable **Linear workflow:** - The exact state IDs for "In Progress" and "In Review" - How to query for tickets, implement them, commit with the VGC-XX prefix - How to post the commit comment and move the ticket state - Rule: bug tickets are always worked on first, regardless of priority number **Discord notifications:** - The `discord_notify_build` function format - Different embeds for direct-to-main pushes vs PR flows **Failure handling:** - Build fails → fix and retry, never push broken code - Linear API fails → still commit and push, note the failure to the user - Production breaks → `git revert`, push to main, notify Discord, move ticket back **Code conventions:** - Follow existing patterns, no drive-by refactors - Commit messages: `VGC-XX: description` for tracked work This file is the single most valuable thing in the project. Every session starts with full context. No re-explaining, no drift, no "can you check the codebase structure?" ## Automated Monitoring Beyond the dev workflow, I set up two Vercel cron jobs: - **Daily (9 AM):** Site health check, stale ticket scan, SEO audit, DB health — posts alerts to Discord only if something's wrong - **Weekly (Friday 5 PM):** Linear progress digest, user growth, dependency updates — always posts a summary to Discord These run on Vercel's free tier. Real-time uptime monitoring is handled by UptimeRobot with 5-minute pings. ## What Worked **Trunk-based development with type-checking gates.** Every push to main auto-deploys on Vercel. The gatekeeper is `tsc --noEmit && npm run build`. The feedback loop is minutes, not days. **Linear ticket traceability.** Every commit links back to a ticket. Every ticket has a comment with the commit URL and changed files. When something breaks, I trace it to the exact change and the exact intent. **Discord as an audit trail.** Every build posts to #builds. It sounds like overkill for a solo project, but scrolling through the channel to see what shipped this week is genuinely useful. **The CLAUDE.md as living infrastructure.** I update it whenever the workflow changes. New conventions, new failure modes, new

Ungefragt Ausführungen

submitted by /u/Sea_Fruit5986 [link] [comments]

MCP server that lets AI create animated SVGs from scratch

hey, I just shipped this and looking for feedback. nakkas is an MCP server where AI is the artist. you describe what you want, AI constructs the full config (shapes, gradients, animations, filters), and the server renders clean animated SVG. some things it can do: animated logos, loading spinners, data visualizations scatter fields, radial patterns, grid layouts parametric curves (rose, spiral, heart, superformula) 15 filter presets (glow, neon, glitch, chromatic aberration...) CSS @ keyframes + SMIL animations, zero JavaScript works in anywhere SVG renders. npx nakkas@latest I would love to see what you make with it. you can share examples in github discussions. repo: https://github.com/arikusi/nakkas npm: https://www.npmjs.com/package/nakkas submitted by /u/Niacinflushy [link] [comments]