FabienSalles/claude-marketplace

Astro 5.x — components, routing, collections, i18n, SEO, Tailwind, React islands, transitions

Audit hub — personal overrides for upstream audit skills + stack-specific code patterns (security for TS/NestJS, PHP planned). Loads in parallel with netresearch/security-audit.

Shared hooks, agents, commands, skills across projects

Cross-language software craftsmanship principles — refactoring, DDD, OOP, TDD, testing, code style — that complement language-specific example skills (php-*, ts-*, etc.)

Frontend clean architecture (hexagonal), Container/Presentation patterns

Transverse git & PR discipline — ref freshness (fetch first), branch/commit/PR conventions, force-push and worktree guardrails. Merges the former PR-creation skill.

Chantier→spec→plan→unattended run workflow for Claude Code: cut an initiative into an ordered just-in-time backlog (/goal:tickets), settle the functional contract of any source — Jira US (via MCP), GitHub issue, spec file or inline — with a grilled, observable Definition of Done (/goal:spec), lock the executable plan into gate-blocked iterations (/goal:plan), then let the runner execute it unattended, each slice judged by a program (goal-gate.ts) that runs the declared command and is the only thing allowed to commit — watched to the end by /goal:supervise, with /goal:next as the checkpoint between two iterations. GitHub, commit and PR are all opt-in, never forced.

jQuery code conventions — module structure with exported init function, js-* selector classes, per-block scoping, symmetric toggleClass over imperative show/hide helpers. Framework-agnostic (works with any backend / build system).

Reverse-engineer an unfamiliar or legacy codebase into a versioned knowledge base (shared brain): recon + git archaeology, architecture map, use cases aggregated by actor goal, entity model, risk register. Two depths: onboarding (dev) and audit-prep (security-surface dossier feeding the security-audit skills). Run via the legacy:discovery skill.

macOS / BSD platform discipline — shell/bash 3.2 vs Homebrew bash 5+, BSD vs GNU command portability, common macOS pitfalls

Marketing analytics — tracking setup (GA4/GTM/UTM/tracking plan), Google Analytics Data API reporting, Google Search Console reporting.

Content & copywriting playbooks — LinkedIn posts, SEO blog articles, direct-response copy, editing pass, editorial strategy, content calendar, content repurposing, SEO briefs, technical SEO audit, schema markup.

Distribution channels — multi-platform social posts (Reddit/Twitter/X/LinkedIn/IG/FB/TikTok), Twitter threads and long Reddit posts, email subject lines, newsletter growth.

Strategic marketing — ICP definition, persuasion psychology (70+ mental models), 139 marketing ideas, competitor analysis, positioning/GTM (April Dunford), shared product-marketing context.

NestJS architectural conventions, DDD with NestJS

PHP 8.0–8.3 language conventions — code style, OOP, DDD, refactoring, SQL, Composer. Framework-agnostic. Pair with phpunit for testing and symfony for Symfony-specific FormType/Twig/PRG conventions.

PHPUnit testing discipline for PHP projects — TDD workflow (red-green-refactor with cross-layer iterations), test writing conventions (DAMP, AAA, Prophecy, factories). Layers on craft:tdd-workflow-principles and craft:testing-principles for the cross-language baseline; PHPUnit-specific commands and Prophecy examples live here.

Cherry-picked mattpocock/skills: grill-me (relentless interview before code), grill-with-docs (interview + CONTEXT.md/ADR docs), zoom-out (broader-context request)

Product delivery discipline — slice any functional spec into thin vertical iterations (vertical-slice: 17 splitting techniques + a method to choose and combine them per feature, technical constraint and execution mode), and ship each one without blocking (delivery: feature flags sized to the project, additive no-BC-break change, expand/contract, and the cleanup that closes the loop once it's in prod).

Automatic semver release discipline for this marketplace — every PR that touches a plugin's shipped content bumps its version (major.minor.patch) in plugin.json and marketplace.json, classified from the conventional commits since the plugin's last bump.

Security audit patterns (OWASP, CWE, CVSS) with 80+ checkpoints — by Netresearch

Runtime security hooks: CLAUDE.md injection scanner (SessionStart) + Bash prompt injection detector (PreToolUse)

Deep comparative audit of external Claude skill packs against this marketplace, weighted by my real Claude usage profile, plus a repo structure + documentation health pass. Produces versioned gap-analysis backlogs under audits/. Run via /self-audit:compare <target>.

Claude Code statusline — cwd, git branch, model, context progress bar, 5h rate limit

Cherry-picked obra/superpowers skills: verification-before-completion (evidence before claims), systematic-debugging (root-cause-first)

Personal Symfony conventions — FormType design (data_class as single source of truth, DataTransformer placement), Twig component patterns (trans_default_domain isolation), Post/Redirect/Get for HTML controllers, and testing anything that boots a Symfony kernel (WebTestCase built-in assertions, TypeTestCase, container doubles). Use alongside php (language) and phpunit (framework-agnostic testing). Distinct from atournayre/symfony — these are personal overlays.

Docker, Drizzle ORM, pnpm workspaces, Zod schemas, Claude Code plugin conventions, npx skills conventions

TypeScript conventions, typing, DDD events, functional programming, OOP, refactoring

Vitest TDD workflow, test conventions and patterns