claude-config

Apply standard development permissions to the current project by creating .claude/settings.local.json with pre-approved tools and bash commands. Use when setting up a new project or when the user wants to configure Claude permissions.

Automatically loaded at session start. Maps tasks to the right skill. Do not invoke manually.

Manage Resend email platform via CLI — send emails, manage contacts, broadcasts, templates, segments, domains, webhooks, and more. Use when the user wants to send emails, manage contacts/segments, create broadcasts, manage templates, check domain status, or any Resend-related task. Trigger words: "resend", "send email", "broadcast", "contacts", "email template", "domain verify", "webhook".

Explore and validate product ideas through structured brainstorming. Creates a product brief.

Stage all changes, create a commit with auto-generated or custom message, and push to current branch. Use when the user says "commit", "push", "save changes", or wants to finalize their work.

Complete implementation workflow for a task - understand context, plan, implement, validate, review, and commit. Use when the user wants to implement a feature, fix a bug, or complete a specific development task.

Create a detailed implementation plan with stories. Also creates an empty progress.md for tracking.

How to respond to code review feedback. Use when receiving comments on a PR, review suggestions, or CI feedback. Ensures technical rigor over performative agreement.

Create a new skill for the Claude Code config. Use when the user wants to add a new skill, command, or workflow to their configuration.

Orchestrate multiple subagents in parallel for independent tasks. Use when a feature has multiple unrelated parts that can be worked on simultaneously, or when multiple test failures affect different subsystems.

Structured 4-phase debugging process. Use when a bug is unclear, a fix has failed twice, or you're stuck on a problem instead of guessing randomly.

Enforce TDD (Red-Green-Refactor) for features, bug fixes, and refactoring. Use when writing new functionality, fixing bugs, or when the user explicitly asks for TDD.

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category.

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

SEO audit and optimization review. Use automatically when working on pages, metadata, content, images, or any user-facing features. Also use before commits that add new pages or modify existing content.

Sync local Claude config to GitHub repo. Use to backup or share your Claude configuration (CLAUDE.md, settings, commands, agents, skills).

Identify the next incomplete task from the implementation plan. Use when the user asks "what's next", "next task", "c'est quoi la suite", or wants to know what to work on next.

Re-read project documentation (CLAUDE.md, progress.txt, memory-bank/) to refresh context. Use when starting a new session, after a break, or when the user says "refresh", "reload context", "what's the current state", or "on en est où".

Update progress tracking files (progress.md and implementation plan). Use after completing tasks, implementing features, or when the user wants to record progress.

Run lint, build, and E2E tests in sequence. Use when the user wants to validate their code, run tests, or check if everything works before committing.

Complete workflow to validate build, update documentation, update progress, and push changes. Use when finalizing work, before ending a session, or when the user says "finalize", "wrap up", or "ship it".

Define the technical stack and architecture for a project. Interactive session with the Architect agent.

Create a Product Requirements Document. Interactive session to define features, requirements, and scope.

Check Supabase database health, security advisors, and RLS policies. Use automatically after creating or modifying database migrations, RLS policies, or schema changes. Also use when working with Supabase tables or when security/performance issues are suspected.

Red-team security audit for code changes. Use automatically when working on authentication, authorization, user inputs, API endpoints, database queries, or any security-sensitive code. Also use before commits that touch sensitive areas.

Quick validation check returning pass/fail. Use AUTOMATICALLY before any git commit, before pushing code, when user asks "is it ready?", "can we commit?", "does it build?", "c'est prêt?", "on peut commit?", "ça build?", or wants a quick health check. Runs silently in background.

Enforce a precise, minimal design system inspired by Linear, Notion, and Stripe. Use this skill when building dashboards, admin interfaces, or any UI that needs Jony Ive-level precision - clean, modern, minimalist with taste. Every pixel matters.

Intelligently update project documentation (CLAUDE.md, memory-bank/) based on recent changes. Use after implementing features, establishing new patterns, or when documentation needs to reflect current state.