161 entries · last verified 2026-10-13 · 161 links checked · 0 dead
One founder's handbook for running a company on Claude Code: the skills I install, the setups I copied, the rules I keep, and the people worth learning from. It is not a directory of everything that exists - if something is here, it earned its place in real work. Suggest a link by opening an issue (see CONTRIBUTING.md).
Descriptions are my own notes where I wrote one. Where I only saved a link, the description is the repository's or the post's own summary. Ratings like (Matt: 8/10) are my personal scores.
- Start here
- Learn
- Agent teams and subagents
- Prompting
- Skills
- Collections
- Field notes
- Tools and memory
- n8n with Claude Code
- Other useful lists
- How this list is built
- License
What I would send a founder who has one evening: my highest-rated picks and the first entries I wrote a reason for. The full list follows.
- apple-design - Apple's fluid-interfaces philosophy (WWDC 2018 "Designing Fluid Interfaces") translated to the web: springs, velocity inheritance, momentum projection, interruptible gestures, translucent materials, optical type sizing, reduced-motion. Dense and genuinely educational. Why: in my setup it is always on for any app or website build, not only for animation questions - routed by name from a prompt hook, a path-scoped rule and CLAUDE.md, because description matching alone fired it 2 times in 213 skill calls. (Matt: 9/10) · 45k stars · MIT · updated 2026-10 · Skills / Webdesign dev skills
- design-taste-frontend - The flagship (266.5K installs, 1,200 lines). Reads the brief before generating: infers page kind, audience, vibe and constraints, outputs a one-line "Design Read", then pulls only the contextual rules that fit instead of one house style for everything. (Matt: 9/10) · 95k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- emil-design-eng - Emil Kowalski's full design-engineering philosophy (679 lines): UI polish, when to animate, the invisible details that make software feel right. Mild course-plug in the intro, content is excellent. (Matt: 8/10) · 45k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- find-animation-opportunities - Restraint-first finder built on "You Don't Need Animations": sweeps a UI for moments that genuinely deserve motion, rejects most candidates, proposes exact values. Read-only. (Matt: 8/10) · 45k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- imagegen-frontend-web - Directs image generation of website design references: one horizontal image per section (never a compressed full-page board), enforced composition variety, one palette across all images. Pairs with banana / higgsfield-generate. (Matt: 8/10) · 95k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- improve-animations - Senior-advisor motion audit: surveys a codebase's animation code, produces prioritized findings plus self-contained implementation plans a cheaper model can execute. Read-only. (Matt: 8/10) · 45k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- redesign-existing-projects - Scan, diagnose, fix sequence for upgrading existing sites: audits typography, spacing and generic AI patterns with concrete checks, improves within the existing stack rather than rewriting. (Matt: 8/10) · 95k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- review-animations - Reviews animation code against a strict craft bar with a separate STANDARDS.md; "default to flagging, approval is earned". NOTE: ships with disable-model-invocation, so it never auto-fires - invoke explicitly. (Matt: 8/10) · 45k stars · MIT · updated 2026-10 · Skills / Webdesign taste skills
- find-skills - Discovers and installs skills from the open ecosystem - checks the skills.sh leaderboard, ranks by installs and source reputation, and installs straight from GitHub. Why: The package manager habit: instead of building from scratch, we check what already exists and vet it. · 34k stars · MIT · updated 2026-10 · also: github.com · Skills / General
- Frontend design - Anthropic's official frontend design skill; encodes Vercel-style web interface guidelines, component patterns, and accessibility rules so Claude produces production-grade UI out of the box. Why: Raises the floor: UI output goes from generic to shippable without extra prompting. · 180k stars · updated 2026-10 · Skills / Webdesign dev skills
- higgsfield-generate - Gives Claude one-command generation across 30+ models - Nano Banana 2/Pro for images, Seedance 2.0 for video with native audio, plus Kling, Veo, GPT Image 2, 3D, and Marketing Studio - including image-to-video, reframe, and virality scoring. (official Higgsfield · uses your connected Higgsfield MCP/account) Why: Powers our creative AI guides, including the champagne video - one skill instead of five tabs. · 1.3k stars · MIT · updated 2026-09 · Skills / Image & Video Editing
- Humanizer - Claude Code skill that removes signs of AI-generated writing from text. Why: Every piece of copy on agentmatik.ai passes through it. Non-negotiable in our content pipeline. · 56k stars · MIT · updated 2026-09 · Skills / Marketing - Content & Writing
Videos and threads that taught me how Claude Code actually works - start here if you are new to it.
- AI marketing Masterclass: From beginner to expert in 60 minutes - I sit down with James Dickerson, a growth marketer, Claude Code power user, and the mind behind The Boring Marketer, to watch him build an entire marketing system live from the terminal.
- Automate Your Life with Claude Code in 40 Minutes | Moritz Kremb - The honest tradeoffs: OpenClaw vs. Claude Code.
- Build & Sell with Claude Code (10+ Hour Course) - This is the complete Claude Code course. Trust me, save this for later.
- Build an agent that improves itself in 20 minutes (CyrilXBT on X, video) - CyrilXBT's clip of an Anthropic engineer's AI Engineer World's Fair talk, framed as 'Fable 5 is already smarter than we know how to use, the bottleneck was never the AI, it is you'. The talk shows how to build a self-improving agent with no extra tools and no extra cost; the post quotes his own X article on 60 Fable 5 workflows.
- Claude Code Just Got an Agent Dashboard - Claude Code just dropped Agent View, a new way to run and manage multiple sessions from a single terminal tab.
- Claude Code Skills Just Got Even Better - Claude Code just dropped a major update to how skills work.
- Designing loops with Claude Fable 5 (Divyanshi Sharma on Instagram) - 11-slide carousel on building self-improving systems that run on repeat: a self-correction loop where a separate grader model scores the output against a rubric until it passes (Claude Code /goal versus Outcomes in Claude Managed Agents), memory across sessions so the agent turns mistakes into rules it actually rereads, and the Parameter Golf benchmark where Fable 5 improved a training pipeline...
- Eyad Khrais - Claude Code Tutorial Thread - Viral 4.8M-view thread by ex-Amazon/Disney/Capital One CTO breaking down Claude Code's three power features: Skills, Hooks, and Commands - with concrete examples for each.
- How to Make Claude Code Your AI Engineering Team - GStack is an open-source toolkit built by YC President & CEO Garry Tan that turns Claude Code into an AI engineering team - with skills for office hours, design, code review, QA, and browser testing.
- Loop engineering, clearly explained (Charlie Hills on Instagram) - 9-slide carousel with the six-part loop Charlie runs in Claude Code without writing code: /init writes your standards into CLAUDE.md, /goal sets the outcome and the rubric score it cannot stop below, /agents spins up a strategist, a writer and a designer with one job each, a separate QA agent grades every draft (LLM-as-judge), MEMORY.md saves every correction as a rule, and a scheduled Routine...
- Stop prompting Claude, use loops instead (Divjot Sahni on Instagram) - 8-slide carousel on the five loops Claude Code runs on its own once you give it a goal and a finish line, namely plan-act-check, self-correction, tool use, subagent fan-out and stop conditions, plus the built-in /loop command that reruns a task or a whole slash command on an interval or paces itself. The plain-English case for handing over the whole job instead of feeding it the next instruction.
- The Four Agent Loops in Claude Code · TheVibeFounder - Turn-based, goal-based, time-based, proactive. The four Claude Code agent loops, and how much you hand off at each rung.
How I split work between subagents, and the two setups worth copying.
- agency-agents - A complete AI agency in Claude Code: frontend wizards, Reddit community ninjas, whimsy injectors, and reality checkers - each agent is a specialized expert with personality, processes, and proven deliverables. · 159k stars · MIT · updated 2026-10 · also: agencyagents.app
- gstack - Garry Tan's exact Claude Code setup: 15 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA. · 136k stars · MIT · updated 2026-10
- Skills vs MCP (The New Stack) - "Skills (Markdown) are the knowledge layer; MCP is the execution layer," with a 100x token-cost difference for equivalent functionality. The article also covers Brad Feld's open-sourced CompanyOS, which runs an operation on 12 Markdown files plus 8 MCPs, each skill with a standalone mode that works without MCP.
- Sub-agents for atomic tasks ONLY - Don't create CEO agents and product agents. Keep shared context in ONE session. Sub-agents lose the reasoning chain. Bring work to the context, not context to the work.
My own prompt patterns for Fable 5 - copy them as they are.
- 10 Claude prompts to build a mobile app (Hamidullah Khan on Threads) - Hamidullah Khan's Threads post with 10 Claude prompts for building a mobile app end to end, starting with an architecture prompt that makes Claude act as a senior SwiftUI engineer and propose MVVM, folder structure and data flow before it writes code, then one prompt per stage of the build. Each prompt sits in a reply under the post.
- 5 Claude prompts to grow an Instagram account (Camila Markson on Instagram) - Camila Markson's 7-slide carousel with the five Claude prompts behind her claim of 3,000 new followers in a day: analyse five top-performing reels in your niche and explain why they went viral, write ten scroll-stopping hooks, build a 7-day content strategy, rewrite a caption with emotional storytelling and a strong call to action, and generate five carousel ideas built for saves and shares.
- 500 Claude prompts that replace a $10K marketing agency (CyrilXBT on X) - CyrilXBT's X article with 500 Claude prompts organised by the agency role they replace, content strategist, copywriter, social media manager, SEO and blog writer, brand consultant, customer research, email marketing and video scripts, each a fill-in-the-blanks brief that treats Claude like a senior employee.
- 7 Claude prompts to run your business (Camila Markson on Instagram) - 9-slide carousel with the seven prompts Camila Markson says she uses every day so Claude works like a $5K a month assistant: a 7-day content machine in your brand voice, a blunt offer audit of your sales page, a 5-email welcome sequence, a 30-second Reels script, a 3-message DM follow-up, a 10-slide carousel builder and a weekly CEO debrief on your numbers. Copy-paste prompts, no tools required.
- Content OS built with Claude Code prompts (Tyler Germain on Instagram) - Tyler Germain's 8-slide carousel with the prompts he used to build a full content OS in a week: a Next.js, Tailwind and shadcn/ui dashboard with an Instagram manager, a Metricool-fed analytics page, a content calendar, a competitor tracker and an RSS news consolidator, one plain-English prompt per page, plus a CLAUDE.md that documents the stack and the decisions.
- Fable 5 can report a step as done before verifying it, to fix, insert always this prompt:
Before reporting progress, audit each claim against a tool result from this session. Only report work you can point to evidence for. If something is not verified, say so. If a step failed, state that with the output. Do not report success you cannot prove. - Blindspot pass - Ask Claude to surface your unknown unknowns before starting unfamiliar work.
-
"Can you do a blindspot pass to help me figure out my relevant unknown unknowns and help me prompt you better."
- Brainstorms & prototypes - Ask for several wildly different options to react to instead of one answer.
-
"Make me an HTML page with 4 wildly different design directions so I can react to them."
- Interviews - Have Claude interview you one question at a time to resolve ambiguity.
-
"Prioritize questions where my answer would change the architecture."
- References - Point Claude at existing code and have it reimplement the same semantics.
-
"This Rust crate in vendor/rate-limiter implements the exact backoff behavior I want. Read it and reimplement the same semantics in our TypeScript API client."
- Implementation notes - Have Claude keep a running log and handle edge cases without stopping.
-
"Keep an implementation-notes.md file. If you hit an edge case, pick the conservative option, log it under 'Deviations', and keep going."
- Quizzes - After a change, ask for a report plus a quiz to verify your own understanding.
-
"Give me a HTML report on the changes with context, intuition, what was done - and a quiz at the bottom that I must pass."
The skills I install, grouped by what they are for. Star counts and licenses come from GitHub and are refreshed with every sync. The last group, Installed on my machine, is synced automatically from the skill lock on my Mac: everything installed that is not already listed above, with the skill's own description and the install date.
- Instagram post Db1USzsMNnZ - Teach Claude Code how to watch YT.
- Access to Codex - Use OpenAI Codex from within Claude Code to review code, run tasks in parallel, or delegate subtasks to a separate coding agent. · 34k stars · Apache-2.0 · updated 2026-07
- AI Project Starter for Claude Code - Opinionated project scaffold with pre-configured CLAUDE.md, folder structure, and best-practice defaults to get any Claude Code project started cleanly. · 8 stars · MIT · updated 2026-01
- Claude Mem - Persistent context across sessions for any agent; captures everything Claude does, compresses it with AI, and injects relevant context back into future sessions via hybrid semantic and keyword search. · 100k stars · Apache-2.0 · updated 2026-10
- Claude Video - See frames in videos - Give Claude the ability to watch any video. /watch downloads, extracts frames, transcribes, hands it all to Claude. · 18k stars · MIT · updated 2026-09
- find-skills - Discovers and installs skills from the open ecosystem - checks the skills.sh leaderboard, ranks by installs and source reputation, and installs straight from GitHub. Why: The package manager habit: instead of building from scratch, we check what already exists and vet it. · 34k stars · MIT · updated 2026-10 · also: github.com
- GSD (Get Sh*t Done) - Context engineering framework for reliable Claude Code with planning and subagent orchestration. · also: youtube.com
- Obsidian Skills - Agent skills that teach Claude Code how to natively create and edit Obsidian-specific formats including Markdown with wikilinks, Canvas files, and Bases, and interact with the Obsidian CLI. · 49k stars · MIT · updated 2026-09
- openai/whisper - General-purpose speech recognition model trained on 680,000 hours of multilingual audio; performs transcription, translation, and language identification with state-of-the-art accuracy. · 110k stars · MIT · updated 2026-08
- Skill Seekers - Converts any documentation website, GitHub repo, or PDF into a ready-to-use Claude skill with automatic conflict detection. · 15k stars · MIT · updated 2026-09
- skill-creator - Build and optimize skills based on Anthropic's own best practices; lets an agent do deep research on a topic (like SEO) and iteratively refine the skill until it's perfect. Why: The skill that makes all the other skills - we used it to build our client-specific ones. · 180k stars · updated 2026-10
- Caveman - Cuts 65% of token usage by instructing Claude to respond in compressed, caveman-style shorthand - ideal for long sessions where context budget matters. · 111k stars · Apache-2.0 · updated 2026-10 · also: linkedin.com
- Omniroute - Never stop coding. Free MIT AI gateway: one endpoint, 359 providers (150+ free), 1200+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. · 75k stars · MIT · updated 2026-10 · also: omniroute.online
- Ponytail - Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. · 161k stars · MIT · updated 2026-10
- STE Writing Skill - A global Claude skill that rewrites technical prose (READMEs, PR descriptions, error messages, runbooks, release notes, code comments - never code or marketing copy) into ASD-STE100 Simplified Technical English, stripping AI-slop form. Two modes (strict for procedures/safety, STE-flavored for general docs) plus a 7-point self-lint; adapted to ban em/en dashes per Matt's hyphen-only rule. · 541 stars · updated 2026-10
- animation-vocabulary - Reverse-lookup glossary: describe a motion effect vaguely ("the bouncy thing when a popover opens") and get the precise term to prompt with. Useful, narrow. (Matt: 6/10) · 45k stars · MIT · updated 2026-10
- brandkit - Image-generation direction for brand-guidelines boards, logo systems and identity decks that look studio-made. For pitch and identity work. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- design-taste-frontend - The flagship (266.5K installs, 1,200 lines). Reads the brief before generating: infers page kind, audience, vibe and constraints, outputs a one-line "Design Read", then pulls only the contextual rules that fit instead of one house style for everything. (Matt: 9/10) · 95k stars · MIT · updated 2026-10
- emil-design-eng - Emil Kowalski's full design-engineering philosophy (679 lines): UI polish, when to animate, the invisible details that make software feel right. Mild course-plug in the intro, content is excellent. (Matt: 8/10) · 45k stars · MIT · updated 2026-10
- find-animation-opportunities - Restraint-first finder built on "You Don't Need Animations": sweeps a UI for moments that genuinely deserve motion, rejects most candidates, proposes exact values. Read-only. (Matt: 8/10) · 45k stars · MIT · updated 2026-10
- gpt-taste - Awwwards/GSAP-heavy landing pages: forced layout randomization via a simulated dice-roll, AIDA structure, strict motion patterns. Breaks layout repetition but rigid and gimmicky. (Matt: 6/10) · 95k stars · MIT · updated 2026-10
- high-end-visual-design - "Premium agency" aesthetic: hard banned-list (Inter, harsh shadows, Bootstrap grids) plus a variance engine picking from texture archetypes (ethereal glass, editorial luxury, soft structuralism). Slightly LARP-y persona, concrete rules. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- image-to-code - Design-image-first workflow: generate large section-specific reference images, analyze deeply, implement to match. Codex-flavored phrasing but the discipline transfers. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- imagegen-frontend-mobile - Mobile counterpart: app-native screen concepts in subtle phone mockups with multi-screen consistency. Images only, no code. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- imagegen-frontend-web - Directs image generation of website design references: one horizontal image per section (never a compressed full-page board), enforced composition variety, one palette across all images. Pairs with banana / higgsfield-generate. (Matt: 8/10) · 95k stars · MIT · updated 2026-10
- improve-animations - Senior-advisor motion audit: surveys a codebase's animation code, produces prioritized findings plus self-contained implementation plans a cheaper model can execute. Read-only. (Matt: 8/10) · 45k stars · MIT · updated 2026-10
- industrial-brutalist-ui - Two committed archetypes (Swiss industrial print or CRT/tactical terminal, never mixed) with specific type systems and simulated analog degradation. Great when the brief calls for it. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- minimalist-ui - Notion-like warm-monochrome editorial style: flat components, serif/sans/mono type architecture with named font stacks, bans on gradients, pills and AI copy cliches. Narrow by design, coherent in its niche. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- redesign-existing-projects - Scan, diagnose, fix sequence for upgrading existing sites: audits typography, spacing and generic AI patterns with concrete checks, improves within the existing stack rather than rewriting. (Matt: 8/10) · 95k stars · MIT · updated 2026-10
- review-animations - Reviews animation code against a strict craft bar with a separate STANDARDS.md; "default to flagging, approval is earned". NOTE: ships with disable-model-invocation, so it never auto-fires - invoke explicitly. (Matt: 8/10) · 45k stars · MIT · updated 2026-10
- stitch-design-taste - Generates anti-generic DESIGN.md files in Google Stitch's semantic language; wired into the UI sourcing rule alongside the Stitch MCP. (Matt: 7/10) · 95k stars · MIT · updated 2026-10
- ai-website-cloner-template - Clone any website with a single command using AI coding agents; outputs a fully editable local copy of the target site's structure and styles. · 36k stars · MIT · updated 2026-10
- anthropics/knowledge-work-plugins - design-critique - Anthropic's open-source plugin repository for knowledge workers (16.8K stars), featuring the design-critique skill that delivers structured UX/UI critique by evaluating decisions across usability, hierarchy, clarity, and interaction quality. It is particularly useful for spotting weak UX patterns and suggesting concrete, actionable improvements. · 29k stars · Apache-2.0 · updated 2026-10
- apple-design - Apple's fluid-interfaces philosophy (WWDC 2018 "Designing Fluid Interfaces") translated to the web: springs, velocity inheritance, momentum projection, interruptible gestures, translucent materials, optical type sizing, reduced-motion. Dense and genuinely educational. Why: in my setup it is always on for any app or website build, not only for animation questions - routed by name from a prompt hook, a path-scoped rule and CLAUDE.md, because description matching alone fired it 2 times in 213 skill calls. (Matt: 9/10) · 45k stars · MIT · updated 2026-10
- Brand Guidelines - Encode your brand into a skill; auto-applies your colors, fonts, spacing, and tone of voice consistently across everything Claude outputs. · 180k stars · updated 2026-10
- Canvas Design - Anthropic's official skill for creating visual art, posters, and compositions as real PNG/PDF files directly from Claude Code. · 180k stars · updated 2026-10
- Figma Skills - Official Figma skills that teach Claude Code how to read Figma files, extract design tokens, and implement designs with pixel-perfect accuracy via the Figma MCP server. (Figma MCP Writeup) · 2.1k stars · updated 2026-10 · also: help.figma.com
- Frontend design - Anthropic's official frontend design skill; encodes Vercel-style web interface guidelines, component patterns, and accessibility rules so Claude produces production-grade UI out of the box. Why: Raises the floor: UI output goes from generic to shippable without extra prompting. · 180k stars · updated 2026-10
- Huashu Design - A free alternative to Claude Design that runs inside Claude Code, turning a single sentence into finished prototypes, HTML slide decks, MP4 animations, or infographics in 3-30 minutes. Draws on 20 built-in design philosophies and uses Playwright to verify output in a real browser before delivery. · 24k stars · MIT · updated 2026-09
- Impeccable - A design auditor that enforces 27 deterministic anti-pattern rules (no cheesy gradients, no Inter-for-everything, no cards-inside-cards) to catch AI slop before it ships. Includes 23 slash commands for auditing, polishing, and iterating on frontend designs directly inside Claude Code. Why: Catches AI-slop design before it ships; we run it on every UI change. · 80k stars · Apache-2.0 · updated 2026-10 · also: github.com
- inference-sh/skills - landing-page-design - inference.sh's agent skills library (483 stars), providing the landing-page-design skill that helps create higher-converting landing pages by improving structure, messaging hierarchy, CTAs, and visual layout. It balances aesthetics with conversion-oriented design principles to produce pages that both look good and perform well. · 765 stars · updated 2026-10
- Playwright - Microsoft's browser automation framework that, when paired with Claude Code, opens your app in a real browser, takes a screenshot, and flags design issues before you ship. Supports Chromium, Firefox, and WebKit across 100+ browser styles and 20+ usability rules. · 97k stars · Apache-2.0 · updated 2026-10
- Schoepplake/framer-motion-skill - Production-grade animation patterns for React and Next.js using Motion (formerly Framer Motion). Covers correct imports, scroll animations, exit animations with AnimatePresence, stagger variants, layout animations, gesture animations, accessibility via useReducedMotion, and ready-to-use recipes (progress bar, counter, page transition, gradient shimmer). · 5 stars · updated 2026-06
- taste-skill - An anti-slop frontend framework with adjustable dials for layout variance, motion intensity, and visual density - soft, minimalist, brutalist, and redesign variants. · 95k stars · MIT · updated 2026-10
- Theme Factory - Generate cohesive color palettes and typography systems you can apply across an entire product; maintained by Anthropic. · 180k stars · updated 2026-10
- Top 5 Claude Code Front-End Skills - Detailed tutorial on impeccable, Huashu design, UI/UX Max Pro, Taste skill, Playwright.
- ui-ux-pro-max - A searchable design intelligence database - 161 reasoning rules, 67 UI styles, 161 color palettes, 57 font pairings - that generates a complete design system before a line of code is written. · 135k stars · MIT · updated 2026-10 · also: github.com
- vercel-labs/agent-skills - web-design-guidelines - Vercel's official collection of agent skills, containing the web-design-guidelines skill that reviews UI code against Vercel's web interface standards to catch design, UX and accessibility issues, with file-level feedback. Why: A second, stricter pair of eyes on layout and accessibility - complements impeccable well. · 32k stars · updated 2026-08
- 21st-dev/magic-mcp - The official 21st.dev Magic MCP server itself. Described as "like v0 but in your Cursor/Windsurf/Cline" - an AI-driven tool that generates polished, production-ready UI components from natural language descriptions, with SVGL logo integration. · 6k stars · ISC · updated 2026-09
- Google Stitch MCP - Generate full UI screens from a text prompt, piped directly into Claude Code via MCP. · 8.5k stars · Apache-2.0 · updated 2026-08 · also: stitch.withgoogle.com · also: stitch.withgoogle.com
- Shadcn-ui - A set of beautifully-designed, accessible components and a code distribution platform. Works with your favorite frameworks. Open Source. Open Code. · 125k stars · MIT · updated 2026-10
- Linear - Manage Linear issues, projects, and teams from Claude Code using MCP tools, SDK automation, and GraphQL API patterns. (Codex version by OpenAI) · 134 stars · MIT · updated 2026-07 · also: github.com
- Code Reviewer - Use before opening a PR; delivers a full structured review covering what is broken, what is risky, what is messy, and what is solid.
- Debug this - Use when stuck on a bug; gives real breakpoints, lets you step through execution line by line, and inspect live variable state. · 330 stars · MIT · updated 2026-04
- Feature Forge - Use before writing a single line of code; asks the right questions, thinks like both a PM and a dev, and hands you a full spec with requirements and acceptance criteria.
- Git Worktrees - Creates isolated workspaces for multiple branches so you never lose your current context when switching between them. · 298k stars · MIT · updated 2026-10
- LightRAG - A fast, lightweight RAG system that enhances LLMs with graph-based retrieval, supporting multiple storage backends and multimodal data processing. · 40k stars · MIT · updated 2026-10
- Mobile Apps - Agent skills for building and testing mobile apps from Claude Code, covering React Native and Expo workflows. · 586 stars · MIT · updated 2026-10
- Playwright Skill - Use before writing any implementation code; walks through the full TDD cycle: write the failing test, watch it fail, then write just enough to pass it. · 392 stars · MIT · updated 2026-10
- RAG Architect - Designs the full RAG pipeline for any vector search or knowledge base project: chunking, embeddings, retrieval, and reranking.
- Secure Code Guardian - If you’re building anything with auth, passwords, or user input, this writes secure code from the jump. no vulnerabilities you’ll regret later.
- Spec Miner - Point at inherited code with zero documentation; reads everything, traces data flows, and writes the spec that should have been there from day one.
- Supabase Agent Skills - Official Supabase skills that teach AI agents how to interact with Supabase databases, auth, storage, and edge functions from Claude Code. · 2.8k stars · MIT · updated 2026-10
- Superpowers - Keeps context windows clean by dispatching isolated agents per task instead of one long session that drifts; covers the full software development workflow including brainstorming, planning, subagent-driven dev, TDD enforcement, code review, and git worktrees. Why: It is the backbone of how we build - every feature on this very website goes through its brainstorm and review steps. · 298k stars · MIT · updated 2026-10
- The Fool - Use before committing to any big decision or architecture choice; challenges thinking from five angles including devil's advocate, red team, and pre-mortem.
- Web App Testing (official) - Anthropic's official skill for testing web apps inside Claude Code using Playwright; opens a real browser, runs interaction tests, captures screenshots, and reports failures. · 180k stars · updated 2026-10
- Claude-Obsidian - Persistent, compounding wiki vault for Claude based on Karpathy's LLM Wiki pattern; use /wiki, /save, and /autoresearch to build a self-updating knowledge base. · 15k stars · MIT · updated 2026-09 · also: x.com
- Last30days - Researches any topic across Reddit, X, YouTube, HN, and Polymarket from the last 30 days, then synthesizes findings and generates copy-paste prompts; ideal for content and marketing research. Why: Our content research starts here - it is how the guides stay grounded in what people actually struggle with this month. · 64k stars · MIT · updated 2026-10
- banana - Turns Claude into a Nano Banana Pro creative director that writes optimized prompts with Google's 5-component formula and generates or edits images directly via the Gemini API; handles text-to-image, inpainting, style transfer, 4K, and multi-turn creative sessions. (needs a GEMINI_API_KEY · scanned Med Risk) · 1.1k stars · MIT · updated 2026-10
- browser-use/video-use - Agent-native video editing skill for Claude Code that takes raw footage, cuts filler words, color grades, burns subtitles, and produces a final MP4 entirely through natural language instructions. · 28k stars · MIT · updated 2026-10
- Claude Video Vision - Gives Claude the ability to watch and understand videos by extracting frames via ffmpeg and processing audio through multimodal backends; ideal for generating creative briefs, hooks, and shot-by-shot breakdowns from any video. · 1.4k stars · MIT · updated 2026-10
- digitalsamba/claude-code-video-toolkit - Full AI-native video production workspace for Claude Code bundling skills, slash commands, templates, and tools covering the entire pipeline from narration and scoring to rendering and composition. · 2.2k stars · MIT · updated 2026-10
- heygen-com/hyperframes - Write HTML and CSS to declaratively define animated video frames that render to MP4, purpose-built for AI agents that need to programmatically produce video without a GUI. · 61k stars · Apache-2.0 · updated 2026-10
- higgsfield-generate - Gives Claude one-command generation across 30+ models - Nano Banana 2/Pro for images, Seedance 2.0 for video with native audio, plus Kling, Veo, GPT Image 2, 3D, and Marketing Studio - including image-to-video, reframe, and virality scoring. (official Higgsfield · uses your connected Higgsfield MCP/account) Why: Powers our creative AI guides, including the champagne video - one skill instead of five tabs. · 1.3k stars · MIT · updated 2026-09
- Nano Banana 2 - AI image generation skill powered by Gemini 3 Pro; supports green-screen transparency, reference images, and style transfer directly inside Claude Code. · 417 stars · MIT · updated 2026-04
- Remotion best practices - Deep knowledge of animations, timing, and audio sync so Claude can produce programmatic videos using React and Remotion with production-grade output. · 5.1k stars · updated 2026-10
- seedance-prompt-en - Makes Claude an expert prompt engineer for Seedance 2.0, mastering the @ reference syntax, camera language, beat-matching, and shot structure to turn a rough idea into a precise, production-ready video prompt; built straight from ByteDance's official docs. (no key - pure prompt craft) Why: Pure prompt craft, no API key needed - the difference between a generic clip and a usable shot. · 4.3k stars · MIT · updated 2026-09
- Content Research Writer - Full research → outline → draft pipeline that adds citations, improves hooks section by section, and enables systematic, high-quality content production at scale. · 76k stars · updated 2026-09
- Go Viral Bro (GVB) - acts as a trainable content brain - it discovers winning topics from 9+ platforms, generates hooks and full scripts, and automatically learns from your analytics to improve your content over time. · 269 stars · MIT · updated 2026-03
- Humanizer - Claude Code skill that removes signs of AI-generated writing from text. Why: Every piece of copy on agentmatik.ai passes through it. Non-negotiable in our content pipeline. · 56k stars · MIT · updated 2026-09
- Lookalike content - Analyzes your past content, identifies the patterns behind what performs best, and uses them to generate new trend-relevant content ideas more likely to resonate with your audience.
- agent-skills/google-ads - Twelve Google Ads skills covering campaign audits, keyword work, and reporting. · 41 stars · MIT · updated 2026-04
- AgriciDaniel/claude-ads - Full Meta Ads skill pack that handles competitive intelligence, copy generation, account auditing, and ad scoring. ·
npm install -g @anthropic-ai/claude-code· 9.9k stars · MIT · updated 2026-10 - ai-marketing-skills - Open-source AI marketing skills - growth experiments, sales pipeline, content ops, outbound, SEO, and finance automation. · 3.6k stars · MIT · updated 2026-09
- Claude SEO - Full-site audits, schema validation. 12 sub-skills. · 18k stars · MIT · updated 2026-10
- ComposioHQ/awesome-claude-skills/competitive-ads-extractor - analyzes 3-5 competitors' active ads and outputs a gap analysis showing untapped angles you could own, ranks hooks by frequency, maps offer structures and CTA patterns, and identifies emotional angles nobody in your market is running. ·
npx skills add https://github.com/ComposioHQ/awesome-claude-skills/tree/master/competitive-ads-extractor· 76k stars · updated 2026-09 - Marketing Skills by Corey Haines - 20+ skills: CRO, copywriting, SEO, email sequences, growth. · 54k stars · MIT · updated 2026-10
- Marketing skills by Ryze AI - specific but lower quality, 17 free skills that turn Claude into your marketing assistant. · 4.4k stars · updated 2026-09
- Marketingskills/Ad Creative - Generate on-brand ad creative concepts, copy variations, and visual briefs across channels. · 54k stars · MIT · updated 2026-10
- Marketingskills/AI SEO - Optimize content for AI-powered search engines and answer engines, including structured data, entity coverage, and GEO/AEO best practices. · 54k stars · MIT · updated 2026-10
- Marketingskills/Content Strategy - Build a full content strategy including pillars, formats, cadence, and distribution channels. · 54k stars · MIT · updated 2026-10
- Marketingskills/Email Sequence - Write multi-step email sequences for onboarding, nurture, and re-engagement campaigns. · 54k stars · MIT · updated 2026-10
- Marketingskills/Lead Magnets - The lead-magnets skill from Corey Haines' marketing skills collection (the whole collection is listed under Collections). · 54k stars · MIT · updated 2026-10
- Marketingskills/SEO Audit - Run a comprehensive SEO audit covering technical issues, on-page optimization, content gaps, and actionable recommendations. · 54k stars · MIT · updated 2026-10
- meta-ads-skill - Use when interacting with the Meta Ads CLI to manage accounts, campaigns, ads, and insights. Act as an Expert Media Buyer. · 676 stars · MIT · updated 2026-10
- noise-to-linkedin-carousel - Transforms messy, unstructured source material (transcripts, rough notes, voice memos) into polished, formatted LinkedIn carousel posts ready to publish. · 676 stars · MIT · updated 2026-10
- addyosmani/web-quality-skills skill pack (6 skills) - 6 skills installed from one repo: accessibility, best-practices, core-web-vitals, performance, seo, web-quality-audit. (installed 2026-07-06) · 2.9k stars · MIT · updated 2026-08
- alirezarezvani/claude-skills skill pack (6 skills) - 6 skills installed from one repo: linkedin-analytics, linkedin-content, linkedin-engagement, linkedin-profile, linkedin-skills, linkedin-strategy. (installed 2026-09-24) · 28k stars · MIT · updated 2026-08
- chrome-extensions - Build and publish Chrome Extensions using Manifest V3 best practices. Use this skill whenever the user asks to create, modify, debug, or understand Chrome browser extensions, add-ons, or anything involving the Chrome Extensions API. (installed 2026-07-06) · 2.5k stars · Apache-2.0 · updated 2026-10
- design-critique - Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage fr... (installed 2026-06-14) · 29k stars · Apache-2.0 · updated 2026-10
- emilkowalski/skills skill pack (5 skills) - 5 skills installed from one repo: animation-vocabulary, apple-design, find-animation-opportunities, improve-animations, review-animations. (installed 2026-07-18) · 45k stars · MIT · updated 2026-10
- extract-design-system - Extract design primitives from a public website and generate starter token files for your project. (installed 2026-07-07) · 242 stars · MIT · updated 2026-09
- firecrawl-dashboard-reporting - Pull metrics from analytics dashboards and internal web tools with Firecrawl browser. (installed 2026-07-07) · 192 stars · ISC · updated 2026-08
- firecrawl-website-design-clone - Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. (installed 2026-07-07) · 192 stars · ISC · updated 2026-08
- firecrawl/cli skill pack (8 skills) - 8 skills installed from one repo: firecrawl, firecrawl-agent, firecrawl-crawl, firecrawl-download, firecrawl-interact, firecrawl-map, firecrawl-scrape, firecrawl-search. (installed 2026-04-13) · 649 stars · updated 2026-10
- firecrawl/skills skill pack (4 skills) - 4 skills installed from one repo: firecrawl-build-interact, firecrawl-build-onboarding, firecrawl-build-scrape, firecrawl-build-search. (installed 2026-04-13) · 122 stars · ISC · updated 2026-10
- modern-web-guidance - Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip - web APIs evolve rapidly and training weights contain obsolete patterns. (installed 2026-07-06) · 2.5k stars · Apache-2.0 · updated 2026-10
- no-ai-slop - Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. (installed 2026-09-15) · 12k stars · MIT · updated 2026-09
- playwright-best-practices - Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file upl... (installed 2026-07-06) · 395 stars · MIT · updated 2026-07
- shadcn - Manages shadcn components and projects - adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. (installed 2026-07-07) · 125k stars · MIT · updated 2026-10
- stitch::extract-design-md - Extract a comprehensive design system (DESIGN.md) directly from frontend source code - React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework. (installed 2026-07-07) · 8.5k stars · Apache-2.0 · updated 2026-08
- stitch::generate-design - Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. (installed 2026-06-14) · 8.5k stars · Apache-2.0 · updated 2026-08
- stitch::react-components - Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation. (installed 2026-07-07) · 8.5k stars · Apache-2.0 · updated 2026-08
- supabase - Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, Svelte... (installed 2026-07-06) · 2.8k stars · MIT · updated 2026-10
- supabase-postgres-best-practices - Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations. (installed 2026-07-06) · 2.8k stars · MIT · updated 2026-10
- tailwind-design-system - Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns. (installed 2026-07-07) · 40k stars · MIT · updated 2026-10
- vercel-composition-patterns - React composition patterns that scale. Use when refactoring components with (installed 2026-06-14) · 32k stars · updated 2026-08
- vercel-react-view-transitions - Guide for implementing smooth, native-feeling animations using React's View Transition API ('<ViewTransition>' component, 'addTransitionType', and CSS view transition pseudo-elements). (installed 2026-06-14) · 32k stars · updated 2026-08
- watch - Watch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the v... (installed 2026-07-16) · 18k stars · MIT · updated 2026-09
- web-design-guidelines - Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". (installed 2026-06-14) · 32k stars · updated 2026-08
- writing-beats - Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it. (installed 2026-09-24) · 287k stars · MIT · updated 2026-10
- writing-fragments - Writing, explore: mine raw fragments, no structure yet. (installed 2026-09-24) · 287k stars · MIT · updated 2026-10
- writing-shape - Writing, exploit: shape raw material into an article, paragraph by paragraph. (installed 2026-09-24) · 287k stars · MIT · updated 2026-10
Lists and directories I go back to when I need something I do not have yet.
- awesome claude code - A hand-picked collection of the finest of resources for the most awesome of agents, Claude Code, the undisputed champion of coding companions, from the unstoppable team at Anthropic PBC (no affiliation). · 55k stars · updated 2026-10
- awesome-claude-skills - A curated GitHub list maintained by the community. Great if you prefer a simple, hand-picked list over a full marketplace. · 10k stars · updated 2026-09
- claude code best practice - from vibe coding to agentic engineering - practice makes claude perfect. · 67k stars · MIT · updated 2026-10
- Everything Claude Code (ECC) - the largest Claude Code harness: about 290 skills, 68 agents, 124 rules and 97 commands, plus adapters for Codex, Cursor, OpenCode and more, 260k+ stars. The reference for what a complete setup looks like. Best when you want breadth or run several harnesses; it is heavy on context, so install the components you need rather than everything, and read its token optimization guide first. · 277k stars · MIT · updated 2026-10
- opendirectory - AI Agent Skills built for GTM, Technical Marketing, and growth automation. · 676 stars · MIT · updated 2026-10
- Skills Guide | Claude Skills - Decision trees and skill combinations for choosing the right skill.
- gstack - my notes on it; the entry itself is under Agent teams and subagents:
- The core idea
- gstack is a process, not a toolbox - its skills mirror a sprint: Think → Plan → Build → Review → Test → Ship → Reflect. Each skill writes an artifact the next one reads (/office-hours writes a design doc that /plan-ceo-review reads; /plan-eng-review writes a test plan that /qa picks up). So order matters more than which individual command you run.
- The main loop (in order)
-
- /office-hours - start every new idea here. You describe what you want to build; it interrogates you with forcing questions, pushes back on your framing, and produces a design doc. Why first: it reframes the problem before any code exists, and the design doc feeds everything downstream.
-
- /autoplan - turn the idea into a reviewed plan. One command that automatically runs the CEO review (scope: is this the right thing?), design review, eng review (architecture, edge cases, tests), and DX review - auto-deciding the obvious calls and only surfacing taste decisions to you. Use this instead of running /plan-ceo-review, /plan-eng-review, /plan-design-review individually unless you want one specific lens.
-
- Build - normal Claude Code work, implementing the approved plan.
-
- /review - before any PR. Staff-engineer-style review hunting for bugs that pass CI but break in production. Auto-fixes the obvious, asks you about the risky ones.
-
- /qa <url> - test it for real. Opens an actual headless Chromium browser, clicks through your flows, finds bugs, fixes them with atomic commits, and generates regression tests. /qa-only does the same but report-only (no code changes). /setup-browser-cookies first if the page needs auth.
-
- /ship - open the PR. Syncs main, runs tests, audits coverage, pushes, opens the PR. Then /land-and-deploy merges, waits for CI/deploy, and verifies production. /canary watches production afterwards for console errors and regressions.
-
- /retro - weekly. Reviews what shipped, test health trends, and growth opportunities across the week.
- Picking the right review
- You built... | Before code | After shipping
- UI / web app | /plan-design-review | /design-review
- API / CLI / docs | /plan-devex-review | /devex-review
- Architecture / perf | /plan-eng-review | /review
- Everything | /autoplan | (none)
- Standalone tools worth knowing
- /investigate - systematic root-cause debugging with a hard rule: no fixes without investigation first. Use this instead of "just try a fix" when something breaks.
- /cso - OWASP Top 10 + STRIDE security audit with a high confidence gate (low noise). Good before exposing anything publicly.
- /browse - the headless browser directly (~100ms per command); this is what /qa uses under the hood.
- /design-shotgun → /design-html - generates 4-6 mockup variants in a comparison board, learns your taste from feedback, then converts the winner into production HTML.
- /careful / /freeze / /guard - session guardrails: block destructive commands or restrict edits to one directory.
- /learn - manage what gstack remembers about your codebase across sessions.
- /gstack-upgrade - keep it current.
- Minimal first run (the README's own suggestion)
- /office-hours - describe something you're building (e.g. one of your client web apps)
- /plan-ceo-review on the resulting idea
- /review on any branch with changes
- /qa on a staging URL
- That's enough to know whether the full sprint loop is for you.
Working rules I keep in Notion and refine as Claude Code changes - CLAUDE.md, context, hooks, structure, effort.
- Dave Killeen - Running a whole day out of Claude Code - Field CPO at Pendo uses Claude Code for daily planning, backlog management, and career tracking - a practical model for non-engineers using CC as a full personal operating system.
- What 5 months of nonstop Claude Code taught me - Practitioner breakdown of hard-won lessons from sustained daily use: what actually works, what breaks down at scale, and the habits that compound over time.
- weekly review of all skills and claude code files
- with plan mode significantly better output, more information in plan mode = better input = better output (shift + tab twice to enter plan mode)
- before asking to build a feature, think about the architecture
- before asking to debug, think about what you actually know about the problem
- before asking to refactor something, think about what the end state should look like
- deep back and forth with ChatGPT/Gemini/Claude, defining what I want to build, ask the LLM for the various options you can take in terms of system design, settle on a solution. asking each other questions, not just a one way street.
- Plan mode examples
- Architecture might be wrong (Wait... this should maybe be modularized, Maybe this should be two workflows, What if this scales?)
- Adding a New Feature Mid-Build (Where does retry sit? Is it workflow-level or node-level? Do we centralize error handling?)
- Need Clarification / Edge Case Thinking
- What if the webhook fails?
- What if OpenAI times out?
- What if the transcript is empty?
- What if 5 jobs hit simultaneously?
- Want to refactor cleanly
- Review this workflow as a senior automation engineer and suggest structural improvements before modifying anything.
- Plan mode examples
- Default changed (March 2026): Pro/Max plans now default to medium, not high. Fix: export CLAUDE_CODE_EFFORT_LEVEL=high in your shell profile
- 4 levels - Low (skip thinking, fast/cheap) → Medium (balanced, good default for implementation) → High (always thinks, proactive file reading) → Max (no ceiling, Opus only, expensive)
- The pattern: Plan/architecture = High + Opus → Implementation = Medium + Sonnet → Stuck after 2 attempts = Max
- Adaptive thinking already self-regulates within a level - Claude skips deep thinking on trivial tasks at medium. You're only setting the ceiling, not forcing it on every prompt
- Cost: Max can be 10x more tokens than Low on the same prompt. Opus 4.6 uses ~6-8% of subscription quota per heavy prompt
- Switch mid-session with /effort high or /effort medium - build the habit at the start of planning vs execution blocks
- Most reliable way to set Max: CLAUDE_CODE_EFFORT_LEVEL=max env var - effortLevel: "max" in settings.json gets silently overwritten by the UI (known bug)
- Ultrathink keyword ≠ Max - it actually triggers High. Use /effort max explicitly if you want true max
- opusplan model alias - automatically uses Opus for planning, Sonnet for execution. Best of both worlds for full sessions
- Skill YAML frontmatter supports effort: low - useful for batch/automation skills so they don't burn quota
- use medium for implementation, high for complex reasoning, and max when you're stuck or the stakes are high. The effort parameter controls far more than thinking depth - it governs tool-call appetite, file-reading behavior, and response length simultaneously
- give it full execution loop = faster - “write, run tests, fix failures”
- Break every task into smaller checkpoints - "Create login route, then session handling.", Smaller scope = better output
- plan mode - architect mode, whiteboard mode, system design thinking, claude does not execute and call tools, thinks through structure, risks, dependencies, proposes clear plan before touching any system
- bypass permissions - builder mode, direct system manipulation, Claude does not have to ask anything
- can switch from bypass back to plan mode to rebuild architecture, adding new feature, need clarification/edge case thinking/want to refactor cleanly
- potential flow - 🧠 Plan,⚡ Build, 🧠 Re-evaluate, ⚡ Refine, 🧠 Scale-thinking, ⚡ Optimize implementation
- Run /init on every project - Claude scans your codebase and creates a CLAUDE.md rules file, review it, edit it, make it yours.
- Lazy loading is what makes one big workspace free - subfolder CLAUDE.md files load ONLY when Claude touches files in that subtree. Workspace size does not equal context size - the entire argument against a monorepo dies here.
- Memory files concatenate, they never override - the popular 'deeper CLAUDE.md wins on conflict' claim is wrong per official docs. Contradicting instructions between root and subfolder = coin-flip behavior. Nested files must add, not contradict.
- The launch directory IS the scope - .mcp.json and .claude/settings.json load only from where you start Claude - they are NOT inherited from parents. cd marketing && claude = marketing MCP servers + skills without the n8n stack. This one habit replaces the entire reason people keep separate repos.
- Nested skills are directory-scoped, not session-scoped - a .claude/skills/ inside a subfolder activates whenever Claude works there, even in a session started at root.
- Three-boundary test for a separate repo - only lifecycle (deploys independently), audience (others push to it), or access (NDA/privacy) justify a repo. Notes, plans, client working files, scripts - all in the one workspace.
- Per-role repos fail empirically - the role you do 90% of the time absorbs everything; the other repos die. Real case: 6 role repos dead for 2+ months, backups silently stale, real work stranded in one of them.
- Root CLAUDE.md = map, not manual - folder table + global rules + pointers, under 200 lines (official guidance). Update it when the SYSTEM changes, not when the work changes. Detail goes in domain files and skills.
- Exported configs are the leak vector - n8n workflow JSONs, notebook outputs, API dumps carry live tokens into git - not your source code. A gitleaks pre-commit found 16 live secrets in one workspace. .mcp.json takes ${ENV_VAR} refs, never literals.
- Old repo histories are radioactive - when consolidating, rsync content-only and never merge git history that ever held a secret - then rotate those keys. Archive the old repo on GitHub instead of deleting: free, reversible.
- Worktrees hide real work - before deleting any repo, check .claude/worktrees/ - files can exist ONLY there, one prune away from loss. Real case: 44 production skills lived solely inside an uncommitted worktree.
- Transcripts are plaintext - everything Claude reads can land in ~/.claude/projects/. A root session can read every client folder - NDA or competing clients need their own repo (or devcontainer), not a subfolder.
- Scaffolding rots - elaborate .claude/ rule/command/agent trees built up front decay - one practitioner deleted 60% within 4 months. Add structure only when a pain repeats.
- A version from AI with Remy
- Plan mode as the default. For anything non-trivial (3+ steps or an architectural call), Claude plans before building. If something goes sideways mid-task, it stops and re-plans instead of pushing through. Kills the "Claude runs off and does the wrong thing" risk before it starts.
- Subagent-first orchestration. The main context window is sacred. It's for decisions and talking to me. Anything grunt work (reading 3+ files, broad searches, running tests, producing intermediate analysis) gets delegated to subagents, and their results flow back as summaries, not raw output. This is the single biggest unlock for long-session work, because it stops the main context from getting polluted with tool output.
- Obsidian as the second brain. My vault is the single source of truth for every bit of business context (brand guidelines, strategy docs, meeting notes, client info, decisions). Every workspace loads the relevant bits via @imports at session start, so context flows in automatically.
- Verification before done. Nothing is complete until it's proven to work. Run the tests, check the logs, demonstrate correctness. "Would a staff engineer approve this?" is the internal check before anything gets marked done. Kills the "ship it and see" instinct.
- Boil the Ocean. The standard isn't "good enough," it's "holy shit, that's done." Stole this from Garry Tan
- system prompt for a project, reads before each answer
- Routing file - CLAUDE.md should be a routing file, not a knowledge dump. Keep it under 150 lines. Point to .claude/rules/*.md for detailed specs and docs/ for architecture. Otherwise it gets so long that Claude skims it and misses the important stuff.
- auto-compaction - at ~83.5% of the 200K token window - is identified as the single highest-leverage skill for effective usage
- folder structure and where it finds files, frameworks we are using, what end goal is
- Build a validation loop - Build, test, compile commands inside CLAUDE.md. Claude self-corrects when it can validate its own output. Without this, it hallucinates fixes.
- Never manually edit rules - "Update the rules so we never do this again." One sentence. Claude maintains its own CLAUDE.md
- update constantly - update CLAUDE.md every time the CC makes a mistake
- press the # key while working - will add instructions to your CLAUDE.md automatically
- /init - go through everything we have done and then CC would create CLAUDE.md file
- keep under 200 lines and only important information/context, bloats your context window, only add what's unique to a project.
- project-specific (everything part of the flow, specific/weird stuff) + include reason behind instruction (use x because we had production bugs from x)
- CLAUDE.md based on best practice from Boris Cherny
- → Workflow Orchestration: Mandates "Plan Node Default" for any task over 3 steps. Uses subagents liberally to keep the main context window clean.
- → Self-Improvement Loop: This is the real magic. After ANY correction, it updates a tasks/lessons .md file. You're building a compounding system where the mistake rate drops over time because it actively learns from your feedback.
- → Verification Before Done: Can't mark a task complete without proving it works. Diffs behavior. Runs tests. Checks logs. The bar? "Would a staff engineer approve this?"
- → Autonomous Bug Fixing: Zero hand-holding. Point it at failing CI tests or error logs... it just goes to work. No constant context switching from you.
- → Strict Task Management: Forces a "Plan First" approach written to a todo .md with checkable items before any implementation starts.
- And perhaps the most important part?
- It forces the AI to prioritize simplicity, find root causes instead of temporary fixes, and minimize the blast radius of every change. Senior developer standards. Not shortcuts.
- CLAUDE.md based on best practice from Boris Cherny
- keep secrets in 1Password for portability, and also maintain project-specific .env organization
- claude-supermemory - Enable Claude Code to learn in real-time, update it's knowledge, and grow with you, using supermemory. · 2.8k stars · updated 2026-10
- /clear between features - Old context contaminates new tasks. One feature per session. Start clean or pay the token tax.
- Audit with /context regularly - MCPs destroy your token budget. /context shows the biggest offenders. Disable what you don't need. Most engineers never check this.
- Compact aggressively (~50%) for multi-file coding; for linear work and workflows only when CC starts forgetting and repeating mistakes
- at 20-40% context usage quality of the output starts to chip away, once dropping more context makes it worse, not better
- scope conversations - one conversation per feature or task
- Use external memory - complex = Claude write plans and progress to actual files ( SCRATCHPAD.md or plan.md), persist across sessions, if hierarchy system of files = keep on top
- copy-paste reset - context bloated > copy everything from terminal > run /compact to get summary, /clear the context and start fresh
- Notifications - sound notification once a task is done.
- use hooks (not CLAUDE.md) for enforcement since instructions get "forgotten" in long context
- leverage anti-rationalization Stop hooks to prevent Claude from rationalizing incomplete work
- How I structure Claude Code projects (Reddit post) - Reddit post on splitting memory into .claude/rules files, a Stop hook that captures lessons as you go, and CLAUDE.md as a routing file - my notes on it are below.
- Instead of one big CLAUDE.md, I split into .claude/rules/memory-*.md files - profile (facts about me), preferences (how I like things done), decisions (past choices for consistency), and sessions (rolling summary of recent work). Claude Code auto-loads everything in .claude/rules/ so it's always in context without bloating the main CLAUDE.md.
- Enforcement: CLAUDE.md has a MANDATORY section telling Claude to update memory files as it goes, not at the end. The problem is Claude "forgets" instructions mid-session, so I added a Stop hook that checks if learning-likely files changed and reminds to capture anything new. Belt and suspenders.
### Auto-Update Memory (MANDATORY) **Update memory files AS YOU GO, not at the end.** When you learn something new, update immediately. | Trigger | Action | |---------|--------| | User shares a fact about themselves | → Update `memory-profile.md` | | User states a preference | → Update `memory-preferences.md` | | A decision is made | → Update `memory-decisions.md` with date | | Completing substantive work | → Add to `memory-sessions.md` | **Skip:** Quick factual questions, trivial tasks with no new info. **DO NOT ASK. Just update the files when you learn something.** - The key lines are "AS YOU GO, not at the end" and "DO NOT ASK." Without both of those it tends to either forget or ask permission every time.
-
- Stop hook (settings.json → hooks.Stop):
#!/bin/bash CONTEXT=$(cat) STRONG_PATTERNS="fixed|workaround|gotcha|that's wrong|check again|we already|should have|discovered|realized|turns out" WEAK_PATTERNS="error|bug|issue|problem|fail" if echo "$CONTEXT" | grep -qiE "$STRONG_PATTERNS"; then cat << 'EOF' { "decision": "approve", "systemMessage": "This session involved fixes or discoveries. Consider running /reflect to capture learnings in project docs." } EOF elif echo "$CONTEXT" | grep -qiE "$WEAK_PATTERNS"; then echo '{"decision":"approve","systemMessage":"If you learned something non-obvious this session, run /reflect to update docs."}' else echo '{"decision": "approve"}' fi - This runs when a session ends. It pattern-matches the conversation for signals that learning happened (corrections, discoveries, workarounds) and nudges Claude to write them down. It's a safety net - the CLAUDE.md instruction handles ~90% of it, but the hook catches sessions where it forgot.
- The memory files themselves live in .claude/rules/ so they're auto-loaded as context every session. No RAG, no embeddings - just flat markdown files that Claude reads on startup and edits in-place.
- MCP - connecting tools
- MCP: Biggest unlock for me was connecting tools that Claude can't reach natively. Browser automation for research, Google Workspace for email/calendar, Reddit for monitoring - turns Claude Code from a coding tool into an actual assistant.
- CLAUDE.md as routing file
- The thing most people miss: CLAUDE.md should be a routing file, not a knowledge dump. Keep it under 150 lines. Point to .claude/rules/*.md for detailed specs and docs/ for architecture. Otherwise it gets so long that Claude skims it and misses the important stuff.
Memory plugins, usage meters and small utilities around Claude Code.
- anthropics/claude-code - Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through... · 150k stars · updated 2026-10
- CodexBar - macOS menu bar usage app - Show usage stats for OpenAI Codex and Claude Code, without having to login. · 22k stars · MIT · updated 2026-10
- Ollama + Claude Code = 99% CHEAPER - Running locally with local model or Openrouter.
- rohitg00/agentmemory - #1 Persistent memory for AI coding agents based on real-world benchmarks. · 29k stars · Apache-2.0 · updated 2026-10
- Usage for Claude - macOS menu bar app that shows your Claude usage, from the App Store.
Building n8n workflows from Claude Code - the MCP server and skills that make it work.
- czlonkowski/n8n-mcp - n8n-MCP: A Model Context Protocol (MCP) server that gives Claude Code deep, structured access to n8n's vast library of workflow automation nodes, properties, operations, and documentation. · 23k stars · MIT · updated 2026-10
- czlonkowski/n8n-skills - n8n skillset for Claude Code to build flawless n8n workflows. · 6.4k stars · MIT · updated 2026-10 · also: skills.sh
This list is deliberately short and opinionated. When you want the exhaustive version, these are the ones I actually open:
- hesreallyhim/awesome-claude-code - the reference directory for Claude Code itself: slash commands, hooks, status lines, tooling, plugins. Generated from a curated CSV, so it stays consistent. Go here when you want everything that exists, not just what one person kept.
- ComposioHQ/awesome-claude-skills - skills as a category, with the skill folders committed in the repo so you can read a SKILL.md before installing it. Useful for seeing how other people structure a skill.
- VoltAgent/awesome-claude-code-subagents - a large catalogue of subagent definitions by domain. Worth a skim when you are designing an agent team and want prior art for the role split.
The difference is intent, not quality: those are directories of what exists, this is a record of what I kept after using it. If a link appears in both, theirs will be more complete and mine will tell you whether it survived contact with real work.
The source is a private Notion page where I keep notes while I work. A sync script in my workspace (awesome-sync.py, not in this repo) reads that page through the Notion API and keeps only the sections that are explicitly mapped as public - everything else stays private by default. It canonicalizes every URL (https only, tracking parameters dropped, youtu.be and twitter.com rewritten), drops links to private places (Notion, Google Drive, course platforms), scans every string for secrets and private names, and writes three files: data/links.csv (one row per link), data/notes.json (the field notes) and data/_report.md (what was excluded and why).
From there everything is automated and reproducible from this repo alone:
tools/enrich.pychecks every link and writesdata/enrichment.json: stars, license, last push and archive state from the GitHub API (renamed repositories are followed), titles from YouTube and X oEmbed, and a plain HTTP check with a browser user agent for everything else.tools/build.pyrenders this README fromdata/+config/sections.json+templates/README.template.md. Entries are sorted by name inside each section; the build is deterministic, so running it twice produces the same file.tools/lint.pyfails on dead links, descriptions under 30 characters, duplicate names or URLs, non-https links, tracking parameters, links to private hosts, long dashes, placeholders, thin sections and broken table-of-contents anchors. Whatever it cannot fix on its own is listed under "Open decisions" indata/_report.md.- A weekly GitHub Action (
.github/workflows/links.yml) re-runs the checks and opens a pull request when the README changes.data/_dead.mdlists what needs a human look.
Nothing in this README is edited by hand. Fixes go to data/overrides.json (keyed by the entry id in data/links.csv) and the next build picks them up.
Current build: 161 entries in 8 sections, 139 field notes. Links checked: 161, dead: 0, last check: 2026-10-13. What the sync excluded and why is in data/_report.md.
The content of this list (README and the files in data/) is licensed under CC BY 4.0 - share and adapt it with attribution. The scripts in tools/ are MIT licensed (LICENSE-CODE).