Claude Skills by marcmarti9

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.

Run GitHub Spec Kit's gated spec-driven flow before coding — constitution, specify, clarify, plan, tasks, analyze, implement, converge. Use when starting a feature from a vague prompt, when the project already has .specify/ or specs/, or when the user asks for Spec Kit / speckit / specify. Do not use for one-line fixes.

Select and use temporary domain specialists with bounded JIT context and concrete task-scoped skills.

Model-owned task decision, execution depth and risk gates. Select justified packs, bodies, references, tools and review without keyword classifiers or fixed skill quotas.

Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

Premium Three.js / React Three Fiber product visualization for web storytelling: GLB/glTF scene structure, exploded views, camera direction, lighting, materials, scroll coupling, labels, post-processing, responsive degradation, and GPU validation.

Build premium navigable or guided 3D web environments such as stores, galleries, buildings, rooms, exhibitions, landscapes, and spatial brand journeys. Use when the experience is about moving through space rather than inspecting one product.

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

Mechanical discovery and delivery of explicitly selected Agentit skills and resources. Explains the private CLI, source precedence, receipts and upstream integration boundaries.

Agentit entry contract for material work. Select context just in time, keep installation distinct from delivery, verify observed outcomes, and report host limitations honestly.

Surround agent work with hard, signal-gated verification probes and anti-greenwash rules. Use before done claims, after implementations, or when tests look too easy; not for pure explanation.

Direct the pacing and narrative structure of premium web experiences using scene design, reveals, rhythm, continuity, interaction, and emotional beats before implementation.

Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.