Amb més estrelles
Els skills amb més estrelles de la comunitat. Revisa’n el contingut abans d’utilitzar-los.
stacks-image-to-code
stacksjs
Use when the deliverable is a visually important Stacks page (hero, landing page, marketing site, portfolio, product page, editorial brand page, or redesign where visual quality matters) and you want to generate design reference image(s), deeply analyze them, then implement the UI to match. Runs an image-first pipeline (generate, analyze, implement) and retargets the implement phase to stx + ts-css + composables.
stacks-imagegen-web
stacksjs
Use when designing a landing page, portfolio, hero, or marketing site in a Stacks app and you want premium website design REFERENCE IMAGES first (one horizontal image per section - hero, trust bar, features, pricing, CTA, etc.). Generates IMAGES ONLY, never code. Enforces composition variety, background-image freedom, varied CTAs and hero scales, a narrative concept spine, second-read moments, and one consistent palette across all frames so a coding step can accurately recreate them.
stacks-http
stacksjs
Use when choosing HTTP status constants, bounded fetch, outbound Httx requests, transport fakes, retry/circuit behavior, or the boundary with reactive browser fetching. Covers @stacksjs/http and @stacksjs/httx.
stacks-forms
stacksjs
Use when building persisted form definitions, conditional fields, uploads, payments, submissions, or CSV exports. Covers @stacksjs/forms and config/forms.ts.
stacks-features
stacksjs
Use when installing or disabling optional Stacks bundles, understanding model/migration/view gates, or choosing default route bundles. Covers @stacksjs/features and @stacksjs/config feature controls.
stacks-grill-with-docs
stacksjs
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. Covers Stacks engineering workflows.
stacks-grilling
stacksjs
Use when a plan, design or decision needs stress-testing before any code is written, when the user asks to be grilled or to have their thinking challenged, or when another skill needs the round-and-frontier interview primitive. Produces a shared understanding, never code.
stacks-handoff
stacksjs
Compact the current conversation into a portable handoff document for another agent or session to pick up.
stacks-improve-codebase-architecture
stacksjs
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Covers Stacks engineering workflows.
stacks-implement
stacksjs
Implement a piece of work based on a spec or set of tickets. Covers Stacks engineering workflows.
stacks-implement-spec
stacksjs
Implement the result of /to-spec and /to-tickets in code. Covers Stacks engineering workflows.
stacks-investigate
stacksjs
Use when debugging a Stacks issue - something broken, throwing, failing, flaky or slow. Builds a tight feedback loop that goes red on the bug before any hypothesis is allowed, then minimises, tests hypotheses, fixes and locks it down with a regression test. Enforces no fixes without root cause. Invoke with /stacks-investigate.
stacks-jobs
stacksjs
Use when creating background job classes in app/Jobs/ - job structure, the handle method, job configuration (queue, tries, backoff, timeout, rate), dispatching patterns (dispatch, dispatchIf, dispatchAfter, dispatchNow), or the Every schedule constants. For the queue system internals (workers, batching, events, drivers, testing), see stacks-queue. Covers app/Jobs, the native Job class and typed by-name dispatch.
stacks-health
stacksjs
Use when implementing health checks in a Stacks application - service monitoring, health endpoints, or diagnostic checks. Covers @stacksjs/health (currently WIP - Oh Dear integration planned).
stacks-config
stacksjs
Use when working with Stacks configuration, asynchronous overrides, driver capability evidence, framework feature gates, package resource discovery, or request context. Covers @stacksjs/config and the config/ directory.
stacks-browse
stacksjs
Use for headless browser QA on Stacks applications - navigation, screenshots, responsive testing, console/network monitoring, and accessibility snapshots. Dependency-free, driving a system browser over the Chrome DevTools Protocol using only Bun (no Playwright/Puppeteer). Invoke with /stacks-browse.
stacks-cache
stacksjs
Use when implementing caching in Stacks - memory cache, Redis cache, cache-aside pattern (getOrSet), TTL management, cache stats, or cache configuration. Covers @stacksjs/cache and config/cache.ts.
stacks-auto-imports
stacksjs
Use when checking browser/server binding delivery, model globals, registry generation, or the difference between ambient declarations and runtime imports. Covers Stacks auto-imports, stx client delivery, server boot and generated registries (107 models).
stacks-enums
stacksjs
Use when working with framework constants in a Stacks application - NpmScript commands, Action identifiers, or any enumerated constants used across the build system, CLI, and actions. Covers @stacksjs/enums.
stacks-env
stacksjs
Use when working with environment variables in Stacks - the typed env proxy with auto-coercion, .env file loading, X25519 and AES-256-GCM encryption/decryption of env values, runtime/platform detection, CI provider detection, or the env CLI commands. Covers @stacksjs/env, config/env.ts, and .env files.
stacks-domain-modeling
stacksjs
Use when building or sharpening a Stacks project's domain language - challenging a fuzzy or overloaded term, naming a model or event, writing or editing CONTEXT.md, or recording an architecture decision as an ADR under docs/adr/.
stacks-email
stacksjs
Use when working with email in a Stacks application - sending emails via SES/SendGrid/Mailgun/Mailtrap/SMTP, email templates with STX, email drivers, the Mail singleton, the EmailSDK for inbox management, inbound MIME parsing, or email configuration. Covers @stacksjs/email, config/email.ts, and app/Mail/.
stacks-error-handling
stacksjs
Use when implementing error handling in Stacks - the Result type (Ok/Err), handleError function, error page rendering (development with stack traces, production with friendly messages), ErrorHandler class, ModelNotFoundException, HTTP error mapping, log file writing, or error configuration. Covers @stacksjs/error-handling and config/errors.ts.
stacks-buddy
stacksjs
Use when working with the Stacks CLI (buddy/bud/stacks/stx) - understanding every command with its flags and options, adding custom commands, the make:* scaffolding commands, development server commands, build commands, deployment commands, email/mail commands, environment management, or domain/DNS commands. Covers @stacksjs/buddy and all CLI command files.