stacks-registry

$npx mdskill add stacksjs/stacks/stacks-registry

Access and manage Stacks framework extension registry metadata.

  • Retrieve extension metadata like name, URL, and GitHub repo.
  • Depends on @stacksjs/registry package and config/stacks.ts.
  • Uses static array of StackExtensionRegistry entries from registry module.
  • Returns registry data for use in framework extension discovery.

SKILL.md

.github/skills/stacks-registryView on GitHub ↗
---
name: stacks-registry
description: Use when working with the Stacks extension registry — framework extension metadata, package discovery, or the registry system. Covers @stacksjs/registry.
license: MIT
compatibility: Bun >= 1.3.0, TypeScript
allowed-tools: Read Edit Write Bash Grep Glob
---

# Stacks Registry

## Key Paths
- Core package: `storage/framework/core/registry/src/`
- Config: `config/stacks.ts`
- Package: `@stacksjs/registry`

## Source Files
```
registry/src/
└── index.ts              # Registry definition and exports
```

## API

```typescript
import { registry } from '@stacksjs/registry'
import type { Registry } from '@stacksjs/registry'

type Registry = StackExtensionRegistry

const registry: Registry = [
  {
    name: 'stacks',
    url: 'stacksjs.com',
    github: 'stacksjs/stacks',
  },
]

export default registry
```

The registry is a simple array of `StackExtensionRegistry` entries containing framework extension metadata — name, URL, and GitHub repository.

## Usage

```typescript
import { registry } from '@stacksjs/registry'

// Access extension metadata
registry.forEach(ext => {
  console.log(ext.name, ext.url, ext.github)
})
```

## Gotchas
- **Minimal package** — currently just a static array with the core Stacks framework entry
- **Type comes from `@stacksjs/types`** — `StackExtensionRegistry` is defined in the types package
- **Used for framework metadata** — not a package manager or dependency registry
- **Config in `config/stacks.ts`** — the `StackExtensionRegistry` config is defined there

More from stacksjs/stacks

SkillDescription
stacks-actionsUse when working with Stacks server actions — creating actions in app/Actions/, auto-generated API actions from the useApi model trait, the 80+ default framework actions (auth, dashboard, commerce, content, deployment, jobs), action request/response handling, or action registration. Covers @stacksjs/actions and storage/framework/defaults/actions/.
stacks-aiUse when integrating AI capabilities into a Stacks application — using Anthropic/OpenAI/Ollama/AWS Bedrock drivers, image generation (DALL-E), vision analysis, RAG/vector search, embeddings, MCP (Model Context Protocol) clients, text summarization, sentiment analysis, content classification, personalization, or the buddy AI assistant. Covers @stacksjs/ai and config/ai.ts.
stacks-aliasUse when working with path aliases in a Stacks project — import resolution, module aliasing, or debugging import paths. Covers @stacksjs/alias which defines 260+ path mappings for the entire framework.
stacks-analyticsUse when adding analytics to a Stacks application — configuring Fathom or self-hosted analytics, generating tracking scripts, privacy-friendly analytics setup, or the analytics configuration. Covers @stacksjs/analytics and config/analytics.ts.
stacks-apiUse when building, modifying, or debugging API endpoints in a Stacks application — defining routes, handling requests, API middleware, working with the API server, HTTP client (fetcher), API resources, or OpenAPI generation. Covers both @stacksjs/api utilities and the stacks-api server implementation.
stacks-arraysUse when working with array utilities in Stacks — statistical operations (average, median, mode, standard deviation, z-score, percentile, covariance), array manipulation (unique, flatten, partition, shuffle, sample, move), containment checks, or the Arr facade. Covers @stacksjs/arrays.
stacks-authUse when implementing authentication, authorization, passkeys, TOTP/2FA, RBAC, gates, policies, session auth, token management, email verification, password resets, or rate limiting in a Stacks application. Covers the @stacksjs/auth package, config/auth.ts, app/Gates.ts, and app/Middleware/.
stacks-auto-importsUse when working with the Stacks auto-import system — understanding how browser and server auto-imports work, configuring auto-imported functions/models/composables, the auto-import manifests, type generation, or how globals are injected. Covers the auto-import pipeline at storage/framework/auto-imports/.
stacks-brandkitUse when defining or exploring a brand identity for a Stacks project and you want premium brand-kit REFERENCE IMAGES first - logo directions, palettes, typography specimens, identity boards, and application/mockup decks. Generates IMAGES ONLY, never code. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems with intentional logo concepting, sparse type, strong symbolic meaning, and disciplined palettes a coding step can build against.
stacks-browseUse for headless browser QA on Stacks applications — navigation, screenshots, responsive testing, console/network monitoring, and accessibility snapshots. Dependency-free: drives a system browser over the Chrome DevTools Protocol using only Bun (no Playwright/Puppeteer). Invoke with /stacks-browse.