stacks-alias

Resolve StacksJS file paths to standardized @stacksjs/ and ~ aliases.

2|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/bughq/bughq --skill stacks-alias-bughq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-alias
Source: https://github.com/bughq/bughq/tree/main/.claude/skills/stacks-alias
Command: npx skills add https://github.com/bughq/bughq --skill stacks-alias-bughq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the complexity of managing deep, relative file paths in a StacksJS monorepo by providing a centralized mapping for over 260 framework modules, configurations, and resource directories.

Core Features & Use Cases

  • Unified Import Resolution: Standardizes imports using @stacksjs/ or stacks/ prefixes, ensuring consistency across the entire codebase.
  • Resource Mapping: Simplifies access to project-specific directories like components, views, and functions using the ~ alias.
  • Use Case: When refactoring a large project, use this Skill to quickly identify the correct alias for a core framework service or a local configuration file, preventing broken import paths.

Quick Start

Use the stacks-alias skill to identify the correct path alias for the database configuration file.

Frequently Asked Questions about stacks-alias

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve complex path aliases in a StacksJS monorepo?

Path aliases in a StacksJS monorepo are resolved by mapping framework modules and resources to standardized prefixes like @stacks/ or stacks/, ensuring consistent module importing across core packages and application resources without deep relative paths.

What is the best way to clean up relative imports in a TypeScript monorepo?

Cleaning up relative imports in a TypeScript monorepo involves using centralized path alias mappings to replace deep directory traversals with standardized prefixes, simplifying access to configuration files, local components, and core framework modules.

Do I need Bun to use StacksJS path aliases for module resolution?

Yes, StacksJS path aliases require the Bun runtime environment to support preloaded path resolution and build-time alias mapping, ensuring that over 260 framework modules and resource directories resolve correctly during development.

Can I use the tilde alias to import local views and components in StacksJS?

Yes, you can use the tilde alias to simplify access to project-specific directories like views and components in StacksJS, preventing broken import paths when refactoring local application resources across the monorepo.

Why does my module resolution break after refactoring StacksJS configuration files?

Module resolution breaks during refactoring when deep relative paths are used instead of standardized aliases, making it difficult to correctly identify and import core framework services or local configuration files across the monorepo.